[Spacewalk-list] Spacewalk and RHN Channels Best Practices

[Musayev, Ilya]

The second proposed setup:

1 base channel, 2 child channels
rhel-x86_64-server-5

-          rhel-x86_64-server-5-stable

-          rhel-x86_64-server-5-testing

The base channel gets all packages and erratas nightly, the stable child channel has only prod hosts with approved packages (synced at point in time). The testing channel is used by non-prod hosts, which is cloned from the base channel throughout specified interval. Obviously I can have multiple testing channels if needed.

Any feedback on how your enterprise setup is designed is appreciated.

Thank you
-ilya


From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Musayev, Ilya
Sent: Tuesday, May 15, 2012 1:45 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Spacewalk and RHN Channels Best Practices

Here is the current proposed setup, please tell me where I have flows.

1 base channel, 3 child channels
rhel-x86_64-server-5

-          rhel-x86_64-server-5-stable

-          rhel-x86_64-server-5-testing

-          rhel-x86_64-server-5-latest
The original design was to import base iso image into  "rhel-x86_64-server-5", then create 3 child channels and with content of base. Create a sync mechanism that would continusly update "rhel-x86_64-server-5-latest". From then on, clone "rhel-x86_64-server-5-latest" to "rhel-x86_64-server-5-testing" and once confirmed to "rhel-x86_64-server-5-stable".

The prod servers will use activation key that will bind to "rhel-x86_64-server-5-stable" where nonprod to "rhel-x86_64-server-5-testing" and some subset of nonprod to "rhel-x86_64-server-5-latest".

What do you see as an issue in this design, how would I make my prod servers see all applicable errata - because if I just keep it in stable child channel it only sees what it is entitled to see.


From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Musayev, Ilya
Sent: Tuesday, May 15, 2012 12:58 PM
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Spacewalk and RHN Channels Best Practices

Looking for a general layout of channels for updates only (no management or provisioning as it handled by other systems).

Example:

Would you recommend getting all packages/erratas continuously from rhn for base channel rhel-x86_64-server-5 and then span off clones and/or child channels to test out patches?

I just need enterprise working layout that I can setup in house.

My environment consists of prod and non prod servers. I would like to be able to test latest patches on specific non-prod servers, mark them as stable/verified and promote the same operation to production servers and obviously preserve the states. I also would to for all prod servers to have erratas displayed so I know how far they are lagging behind.

How would I go about this setup in terms of system groups and channels?

Any help is appreciated.

Thanks
ilya

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20120515/c69af23a/attachment.htm>