Michael, thanks a million for your thorough response. I'm working on
the upgrade right now, ergo my questions :) But, the version of Cobbler
we're using has been working pretty dang good...so good work!
That said, centos 4.X/5.X releases are essentially patch updates. So,
let's say I have all my machines running centos5.1. Well, if I needed
to get that latest bind fix I would have to:
- Download 5.2
- Change my yum.repo.d/CentOS-Base to point to this tree
- Grab 5.2/updates
- Change my updates repo to point to that.
Looking at the Centos5.1 tree there are no bind updates in it's update
tree. So I guess it's a philosophy thing. Right now we look at .X
releases as simple updates. It is, for the most part hands free. I may
end up using mrepo to manage our distros still as this might be the
easiest upgrade route.
Definitely correct me if I am wrong on the above.
Thanks!
-Dan
Michael DeHaan wrote:
Dan Benson wrote:
> Currently we're using an old version of Cobbler (year or so old) to
> maintain our kickstarts. At the same time we maintain yum repos via
> mrepo. I've been taking a look at migrating this all to cobbler, but
> one thing I can across is how we're currently managing centos updates.
> Essentially mrepo is maintaining OS tree via:
>
> os =
http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/
>
> How can I mimic this behavior in cobbler? Or is my understanding
> correct that you have to maintain separate distros for each .X revision
> of centos?
>
First, I'd strongly recommend upgrading your cobbler to 1.0.3 and
keeping up with cobbler updates. There are lots of fixes from a year
ago, and repo management code has had more improvements than most other
things.
So ... It's kind of easy to confuse repos and install trees. Install
trees are unrelated to updates. Yes, you will want to "cobbler import"
each of the CentOS dot releases as seperate distributions if you want to
make each seperately installable. This is a good practice as you might
want to install something on .2 and .3 side by side for debug purposes, etc.
cobbler import --name=CentOS4.2 --mirror=/mnt/dvd --arch=x86_64 ...
If you want to use cobbler manage your yum updates and so forth, you'll
want to read up on "cobbler repo add" in the manpage and that should
provide most of the information you need. Then you edit profiles and
tell them which repos they should have access to.
cobbler repo add --name=CentOS42i386updates --mirror=http://path ...
cobbler reposync --only=CentOS42i386updates ...
cobbler profile edit --name=42webserver --repos="CentOS42i386updates" ...
etc
I hope that helps and if you have other questions let me know!
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler