[Spacewalk-list] Best way to manage channels

[Edward Perry]

Than thanks Mark, that makes sense. I was a little gun shy about doing it
that way but it does make sense.  So I'll give it a shot.  I would rather
make a mess at home then at work :)




Message: 2
Date: Sat, 21 Jan 2012 19:30:50 +0000
From: Mark Watts <m.watts at linux-corner.info>
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Best way to manage channels
Message-ID: <4F1B126A.4040100 at linux-corner.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 21/01/2012 18:07, Edward Perry wrote:
> Hey folks, got a question which google is not giving me a good answer.
>
> I have just installed and configured Centos6  based on the howto docs
> and then imported the repo.
>
> Now, How is it best to add the updates  6.1  6.2
>
>
> Would it be best to create new channels and re-associate the channel
> with the systems,
>
> Just add the packages to the current channel
>
> Or Other
>
>
> I am looking for best practices for channel management.

Something like this is what I'd use:

CentOS 6 (x64)
\- CentOS 6.1 (x64)
\- CentOS 6.1 - Updates (x64)
\- CentOS 6.2 (x64)
\- CentOS 6.2 - Updates (x64)
\- EPEL for EL6 (x64)
\- My_Custom_Repo (x64)
\- ...

Don't put packages directly in the parent channel, add them to child
channels. This way its simpler to upgrade; just subscribe the systems
you want to the new child channels. When you're done with a major
version, just delete those child channels.

Bear in mind that you should always use signed packages and import the
keys into Spacewalk so you can deploy them via kickstart. This means you
probably want to sort all your channels before you kickstart new
clients. You'll also want to create your own signing key for custom
packages.

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