Linux system administration methodology or best practice

[Stainforth, Matthew (SD/DS)]

I'd be curious to know how this works out for you.  I looked into it
briefly but it wasn't obvious how to get the updates from RHN into
Spacewalk.  If this is possible I'd love to know.

I'll look into mrepo in the meantime.

-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com] On Behalf Of Johan Booysen
Sent: Friday, August 28, 2009 11:02 AM
To: General Red Hat Linux discussion list
Subject: RE: Linux system administration methodology or best practice

Yeah but you pay for the privilege to use RHN Satellite.

I've actually come across Spacewalk, which is apparently a free version
of RHN Satellite.  I've installed it in a test lab but haven't gotten
round to decent testing yet.  In the meantime mrepo does the job for us.

-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com] On Behalf Of Michael Ward
Sent: 28 August 2009 14:42
To: 'General Red Hat Linux discussion list'
Subject: RE: Linux system administration methodology or best practice

Our satellite server downloads all updates from RHN. We can then
allocate
updates to various machines throughout our infrastructure for testing.
Once
testing is complete, if there are discrepancies, we remove the offending
packages from our updates and push the updates to the production
machines at
night.


Michael Ward
Redhat Linux Administrator
Metro State College of Denver
303-352-4225


-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com]
On Behalf Of Johan Booysen
Sent: Friday, August 28, 2009 4:18 AM
To: General Red Hat Linux discussion list
Subject: RE: Linux system administration methodology or best practice

Probably not the cleverest way of doing it, but it works for me:  I've
implemented mrepo, which synchronises updates with RHN.  Then I
configure my servers to point at mrepo for updates.  

You can then make mrepo synch, test the latest updates and update
production servers after testing.  Then synch mrepo to get the next
bunch of updates, test, and deploy to production, etc etc.


-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com] On Behalf Of Shaughnessy, Kevin
Sent: 27 August 2009 22:06
To: redhat-list at redhat.com
Subject: Re: Linux system administration methodology or best practice

I am also looking for hands-on advice for Red Hat administration,
specifically regarding updates:
 -  I'd like a sandbox system to apply them, and test them.  Do I have
to buy the same level of support for this "trash able" system? (I've
already ruled out Fedora and CentOS, as I need to maintain compatibility
with EMC PowerPath and Oracle.)
 -  By the time I've evaluated a set of updates, there are new ones, and
yum always pulls the newest.  How do I migrate my 'approved' set from
sandbox to development to production?
 -  How often do you apply updates to your production servers?  Security
updates?

Thanks,


-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=subscribe
https://www.redhat.com/mailman/listinfo/redhat-list

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list


-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list