On 4/19/2011 2:42 PM, Scott Henson wrote:
> I'd import the 5.6 install media. Then I'd look at the automatic repos
> that it creates inside of the ks_mirror directory. I'd add those as
> repos (you might have to sync them down then run hardlink, I'm not
> sure). Then add those repos to the hosts in question and do a yum
> update.
Are you recommending importing the install media as a repo or a distro?
I'm not clear here.
> I'm a little bit surprised that CentOS doesn't have an updates repo that
> you can just subscribe your systems to get these updates automatically?
> Unfortunately, my experience is using RHEL, so I'm just able to yum
> update my systems to the latest U release. I'd be interested to hear how
> others using CentOS are handling this issue. I'm sure it comes up quite
> a bit.
CentOS does. There are two repos: base and updates. When a package is
updated between point releases (synonymous with RHEL U releases, I
think), it's added to the updates repo. However, when a new point
release is made, the base repo is updated. Also, the CD/DVD
installation media for a point release is generated from the base repo.
A new cobbler user using CentOS will set up the base repo (or a DVD of
that repo) as a distro and will set up the updates repo as a repo. The
problem arises when a point release comes out. Since they've added the
base repo as a distro, it won't be updated with cobbler reposync. They
can import the new point release as a new distro but this won't affect
systems that are already deployed.
My solution is to add the base repo both as a distro and as a repo. For
example:
# cobbler import --path=rsync://ftp.linux.ncsu.edu/CentOS/5/os/x86_64/ \
--name=centos5 --arch=x86_64
# cobbler repo add --arch=x86_64 --name=centos5-os-x86_64 \
--mirror=rsync://ftp.linux.ncsu.edu/CentOS/5/os/x86_64/
I then add the repo centos5-os-x86_64 to all of my profiles.
On CentOS mirrors, /CentOS/5/ points to the directory for the current
point release, i.e. rsync://ftp.linux.ncsu.edu/CentOS/5/ points to
rsync://ftp.linux.ncsu.edu/CentOS/5.6/ today but pointed to
rsync://ftp.linux.ncsu.edu/CentOS/5.5/ last month. (5.6 was released
earlier this month.) This means that the centos5-os-x86_64 repo will
always contain the files for the current point release of CentOS 5 and
that they will be available to all of my deployed systems.
(Since I'm miserly for disk space, this also has a side effect of not
requiring more than one CentOS 5 distro. Kickstart will automatically
pull in updated files from the centos5-os-x86_64 repo.)
Do you do something different for RHEL systems?
--CAE
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
