[Spacewalk-list] Architecture question

[Martin Eggen]

Hi,

the Updates channel receive all updates packages. I used this layout mostly because it was suggested for the CentOS channels, and it also matches my yum repositories as created by mrepo. For some systems I want to be able to subscribe them just to a specific Base channel (RHEL 5.x) and then adding updates later as needed.

I created one main configuration channel pr. OS (we have both RHEL and Solaris systems), and then some role/application specific channels. Make sure to rank the more specific configuration channels higher than the general channel (so any common configuration files will read the more specific version).

Martin

Fra: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] På vegne av Pierre Casenove
Sendt: 6. august 2011 09:06
Til: spacewalk-list at redhat.com
Emne: Re: [Spacewalk-list] Architecture question

Thanks for these useful links!
There is one thing I don't understand: In the base channel you have 5.6 packages. In the update channel, with your solution, do you only have the latest version released by redhat of each package or do you have all the version released since rhel 5.6?
In the first case, I can see clearly the advantage, in the second one, why don't you just put everything in the base channel?

Another question, on the configuration channels: did you create many channels? just one? by arch?

Your experience is more than useful for me!

Thanks,

Pierre

2011/8/5 Martin Eggen <mare at steria.no<mailto:mare at steria.no>>
Hi,
correct, my base channel is still 5.6 and the updates channel receives patches (now at 5.7). Mrepo runs daily (nightly), but I do not rebuild ISOs.
Documentation for setting up mrepo with RHN is here: https://github.com/dagwieers/mrepo/blob/master/docs/redhat-network.txt

Also check https://fedorahosted.org/spacewalk/browser/scripts/clone-errata/<https://fedorahosted.org/spacewalk/browser/scripts/clone-errata/rhn-clone-errata.py>  for cloning RHN errata into your (Base) channel with rhn-clone-errata.py.

You need to edit chanMap (ca line 455) to match your SPW channel name, but apart from that it was not too much work setting up. I did one errata clone with -begin-date=<RHEL 5.6 release date> and then I run it nightly with --begin-date=<yesterday> to clone new erratas. I only use rhn-clone-errata (not spw-clone-errata between local channels, yet).

Martin

Fra: spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com> [mailto:spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com>] På vegne av Pierre Casenove
Sendt: 5. august 2011 07:45
Til: spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>
Emne: Re: [Spacewalk-list] Architecture question

Hello,
Thanks for the feedback.
So all your system are in version 5.6 minimum and some subscribe to the updates channel, which now contains rhel 5.7 for example. Am I correct?
Could you please point me to some tutorial to setup mrepo and rhn? Do you run mrepo and rebuild an iso every night or just once a week?

Thanks,

Pierre

2011/8/4 Martin Eggen <mare at steria.no<mailto:mare at steria.no>>

Hi,
I follow the advice on http://wiki.centos.org/HowTos/PackageManagement/Spacewalk also for our RHEL systems, that is, I rhnpushed 5.6 to a Base RHEL5 channel and sync updates from a yum repo (which uses mrepo to fetch updates from RHN) into a child Updates channel. This is probably redundant but I can see some uses for having separate channels (allowing some systems to only subscribe to Base for a certain minor release). I created similar channels (Base + Updates) for CentOS 5, and one child channel under each Base for EPEL.

I experienced some trouble after adding CentOS though, for some reason CentOS packages were appearing in my RHEL channels, making clients system complain (invalid PGP keys) and not fetching updates.  For the time being I have removed the CentOS channels/repos, but will have to make another try later.



________________________________
This email originates from Steria AS, Biskop Gunnerus' gate 14a, N-0051 OSLO, http://www.steria.no. This email and any attachments may contain confidential/intellectual property/copyright information and is only for the use of the addressee(s). You are prohibited from copying, forwarding, disclosing, saving or otherwise using it in any way if you are not the addressee(s) or responsible for delivery. If you receive this email by mistake, please advise the sender and cancel it immediately. Steria may monitor the content of emails within its network to ensure compliance with its policies and procedures. Any email is susceptible to alteration and its integrity cannot be assured. Steria shall not be liable if the message is altered, modified, falsified, or even edited.

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com<mailto:Spacewalk-list at redhat.com>
https://www.redhat.com/mailman/listinfo/spacewalk-list


This email originates from Steria AS, Biskop Gunnerus' gate 14a, N-0051 OSLO, http://www.steria.no. This email and any attachments may contain confidential/intellectual property/copyright information and is only for the use of the addressee(s). You are prohibited from copying, forwarding, disclosing, saving or otherwise using it in any way if you are not the addressee(s) or responsible for delivery. If you receive this email by mistake, please advise the sender and cancel it immediately. Steria may monitor the content of emails within its network to ensure compliance with its policies and procedures. Any email is susceptible to alteration and its integrity cannot be assured. Steria shall not be liable if the message is altered, modified, falsified, or even edited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20110808/a9e05139/attachment.htm>