Dan Benson wrote:
Depends on if you like to follow the /centos/5/os/x86_64 tree or the
/centos/5.X/os/x86_64 tree. If you're running hundreds of dumb web
servers then you the former works pretty good -- if you have an Oracle
Rac install you might want to be more careful and use the later.
Sorry, but what depends on what? In general, try to avoid top repling to
list posts, as other folks can't tell what points you are addressing :)
For me, I like to carry around a 40GB Vmware image with CentOS4/5 and
rpmforge.....I used to keep x86_64 and i386...but I've recently decided
to drop i386. So this means keeping a copy of 5.1, 5.2, 4.6, 4.5, etc
isn't entirely feasible....And, I think the work to maintain a head
pointer is sort of tedious considering you could just use the head
pointer
centos.org provides (/centos/5/os/).
If they can always hit the public mirror, you can just use that... and
if CentOS provides that pointer, yes, then just use that and reposync
when you like. That sounds workable.
I will play around with things a bit more.
-Dan
Michael DeHaan wrote:
> Dan Benson wrote:
>
>> Actually would it be possible to create a distro from a repo maintained
>> via cobbler? I will give it a whirl...
>>
>>
> I suppose you could do that, but you would still need the install tree
> to reference. So with cobbler distro add, yes (with caveats), cobbler
> import no.
>
> The problem is that reposync could update a kernel and break your
> configuration, so it's best to copy the kernel/initrd out of the tree first.
>
> It's best to not think of repos and distro trees as the same thing, as
> they are only partially related. I would recommend not doing that and
> only use repos for "update" repos or software not in the main tree.
>
>
>> -Dan
>>
>>
>> Dan Benson wrote:
>>
>>
>>> I think what would be a good feature is to have something like:
>>>
>>> cobbler repo add --mirror=http://mirror.centos.org/centos/5/os/x86_64/
>>> --name=centos5-x86_64 --type=distro
>>>
>>> The distro is also called centos5-x86_64. This would give folks the
>>> option of having all repos managed via cobbler reposync and to follow
>>> the philosophy of .X just be patch updates. Obviously, you can't tune
>>> for all distro paradigms.
>>>
>>> Just some thoughts.
>>>
>>> Thanks again!
>>>
>>> -Dan
>>>
>>>
>>> Michael DeHaan wrote:
>>>
>>>
>>>> Dan Benson wrote:
>>>>
>>>>
>>>>> 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!
>>>>>
>>>>>
>>>>>
>>>>>
>>>> Good deal...
>>>>
>>>>
>>>>
>>>>> That said, centos 4.X/5.X releases are essentially patch updates.
>>>>>
>>>>>
>>>> Yes... I do like to keep the older trees around in case I need them
though.
>>>>
>>>>
>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>>
>>>> Hmm, yes, you can for dot releases ... (sorry I was thinking about
>>>> Fedora major upgrades too much lately)
>>>>
>>>> cobbler repo edit --name=c4updates --mirror=http://newurl
>>>>
>>>> And that will /largely/ work.
>>>>
>>>> If reposync does not like you when you do that, let me know, and we can
>>>> see about putting in some sort of fix for that.
>>>>
>>>> Alternatively you can just do it like this:
>>>>
>>>> cobbler import --name=c43 --mirror=/mnt/dvd
>>>> cobbler repo add --name=c43updates --mirror=http://newurl
>>>> cobbler repo remove --name=c42updates
>>>> rm -rf /var/www/cobbler/repo_mirror/c42updates
>>>> cobbler profile edit --name=webserver --repos=c43updates --distro=c43
>>>> cobbler distro remove --name=c42
>>>> rm -rf /var/www/cobbler/ks_mirror/c42
>>>>
>>>> Note that assigns the webserver profile to the new updates repo and the
>>>> new tree.
>>>>
>>>> Having the commands for delete have optional flags to clean up after
>>>> themselves (eliminating the rm -rf steps) is a RFE in Trac, which should
>>>> be done in a later release (probably not 1.1)
>>>>
>>>>
>>>>
>>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> cobbler mailing list
>>>>> cobbler(a)lists.fedorahosted.org
>>>>>
https://fedorahosted.org/mailman/listinfo/cobbler
>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> cobbler mailing list
>>>> cobbler(a)lists.fedorahosted.org
>>>>
https://fedorahosted.org/mailman/listinfo/cobbler
>>>>
>>>>
>>> _______________________________________________
>>> cobbler mailing list
>>> cobbler(a)lists.fedorahosted.org
>>>
https://fedorahosted.org/mailman/listinfo/cobbler
>>>
>>>
>> _______________________________________________
>> cobbler mailing list
>> cobbler(a)lists.fedorahosted.org
>>
https://fedorahosted.org/mailman/listinfo/cobbler
>>
>>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/cobbler
>
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler