[Spacewalk-list] Architecture question

[Jeremy Davis]

Hello all,

I would like to provide how I have setup channels for Spacewalk.

Currently, we have a Development, Test, and Production 32bit and 64bit with
version 4, 5, and 6 base channels. These base channels contain the OS level
packages obtained form the OS CentOS yum repository. We then have
subchannels as follows. Extras, addons, centosplus, and updates. These
sub-channels of each of the base channels reflect each of the different
CentOS yum repositories with the same name. We then have a custom channel
created under the base channels for custom packages or custom builds of
packages that are assigned to different systems. This has worked out well as
we can assign certain custom channels to different systems and also upgrade
systems to the latest sub release like cent 5.4 to say 5.6 within the base
channels. It also allows for complete testing in each of the different
environments (Dev,Test,Prod). In order to move between 4 5 and 6 we retire
old servers and rebuild the server as the new release and assign it to the
correct channels based on keys. Below is a short example of what I am
talking about above.

<orgname>-centos-{development,test,production}-base-{v4,v5,v6}-{32bit,64bit}


<orgname>-centos-{development,test,production}-addons-{v4,v5,v6}-{32bit,64bit}


<orgname>-centos-{development,test,production}-centosplus-{v4,v5,v6}-{32bit,64bit}


<orgname>-centos-{development,test,production}-contrib-{v4,v5,v6}-{32bit,64bit}


<orgname>-centos-{development,test,production}-extras-{v4,v5,v6}-{32bit,64bit}


<orgname>-centos-{development,test,production}-updates-{v4,v5,v6}-{32bit,64bit}

<orgname>-custom-{development,test,production}-{v4,v5,v6}-{32bit,64bit}-<product/environment
name>

If you have any further questions please feel free to ask. Thank you for
your time and have a great day!

Thanks,
Jeremy

On Tue, Aug 9, 2011 at 9:46 AM, Pierre Casenove <pcasenove at gmail.com> wrote:

> Hello,
> Thanks you for your answer. I think I will set up something like you have
> done for centos.
>
> Pierre
>
>
> 2011/8/9 John Hodrien <J.H.Hodrien at leeds.ac.uk>
>
>> On Mon, 8 Aug 2011, Martin Eggen wrote:
>>
>>  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).
>>>
>>
>> I could never quite decide the right/best way to lay out the channels.
>>
>> This time I've gone with:
>>
>> CentOS 6 (contains no packages)
>>  ------CentOS 6.0
>>  ------CentOS 6.0 updates
>>  ------CentOS 6.0 approved updates
>>  ------CentOS 6 internal packages
>>
>> Then when 6.1 comes out, I can add a 6.1 child channel, test a new
>> kickstart
>> against it (without disturbing the existing 6.0 kickstart).  I can test
>> updates to 6.1 without disturbing the existing 6.0 machines.  Moving from
>> 6.0
>> to 6.1 doesn't affect the base channel subscription.  6.0 updates would be
>> a
>> regularly repo-synced version of 6.0 updates, and 6.0 approved updates
>> would
>> contain a subset of the updates channel.
>>
>> jh
>>
>>
>> ______________________________**_________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/**mailman/listinfo/spacewalk-**list<https://www.redhat.com/mailman/listinfo/spacewalk-list>
>>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20110809/7eb621af/attachment.htm>