Re:RHEL Channels
- From: "Alessandro Vercelli" <alever@xxxxxxxxx>
- To: "niall\.litchfield" <niall.litchfield@xxxxxxxxx>
- Date: Wed, 25 Nov 2009 16:09:45 +0100
Hi Niall,
in RHEL 5, the file /var/log/yum.log contains a list of all packages (and
dependencies also) that have been installed on a system with yum.
A simple solution could be:
1. Remote copy of /var/log/yum.log from the dev/test node to all the prod
nodes, into a /tmp/upd_pkgs.txt
2. On prod nodes:
for PACK in `cat /tmp/upd_pkgs.txt| awk -F: '{print $4}'`; do yum -y install
$PACK; done
This will install on the current node all the packages which have been
installed on the dev/test node; if a package is already installed it will be
automatically skipped with a message.
Alessandro
>All,
>
>I'm investigating how one does release management in RHEL. Specifically if
>we have the standard dev/test/prod sort of setup then updating the RHEL
>servers in dev from the RHN at say Oct 01 2009 may install different
>software than running up2date from production at say Dec 01 2009. Is it
>possible (without the use of a satellite server) to specify that the same
>set of RPMs get applied to all servers - so if we test the Oct image we know
>that the exact same rpms will be applied in production. In a yum based
>environment I know that I'm searching for the keyword repository to setup a
>custom repository, in RHN this seems to equate to a channel but I'm having
>difficulty finding an idiots guide to how to configure a channel to do
>release management. Just buy and setup a satellite server may not be an
>option right now.
>
>--
>Niall Litchfield
>Oracle DBA
>http://www.orawin.info
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
