<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html> <head> <meta name="Generator" content="Zarafa WebAccess v7.0.1-28479"> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>RE: [Spacewalk-list] Best way to manage channels</title> <style type="text/css"> body { font-family: Arial, Verdana, Sans-Serif ! important; font-size: 12px; padding: 5px 5px 5px 5px; margin: 0px; border-style: none; background-color: #ffffff; } p, ul, li { margin-top: 0px; margin-bottom: 0px; } </style> </head> <body> Just for your information. I needed to add some proxy rules to /etc/httpd/conf.d/zz-spacewalk-www.conf to make pxe boot installs (via spacewalk) work: # Rewrite rules for kickstart install with subchannels: RewriteRule ^/ks/dist/child/centos-6.0-base/CentOS-60-Test/(.*)$ /ks/dist/CentOS-60-Test/$1 RewriteRule ^/ks/dist/child/centos-6.1-base/CentOS-61-Test/(.*)$ /ks/dist/CentOS-61-Test/$1 RewriteRule ^/ks/dist/child/centos-6.2-base/CentOS-62-Test/(.*)$ /ks/dist/CentOS-62-Test/$1 Probably better rewrite rules are possible to do this, but these work for me. (Be aware that CentOS-6x-Test is the label for the channel in my situation). In common syntax it would be something llike: RewriteRule ^/ks/dist/child/<Parent channel name>/<Child channel name>/(.*)$ /ks/dist/<Child channel name>/$1 Add these rules prior to rewrite rules regarding /ks/dist/<channel name>..... Rick<blockquote style="border-left: #325fba 2px solid; padding-left: 5px; margin-left: 5px">-----Oorspronkelijk bericht----- Aan: spacewalk-list@redhat.com; Van: Edward Perry <edwardperry1@gmail.com> Verzonden: zo 22-01-2012 19:20 Onderwerp: [Spacewalk-list] Best way to manage channels Bijlage: inline.txt <style type="text/css">body { font-family: monospace; }</style><div>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 :)</div><div> </div><div> </div><div> </div><div> </div>Message: 2 Date: Sat, 21 Jan 2012 19:30:50 +0000 From: Mark Watts <<a title="Deze link naar een extern object zal in een nieuw venster worden geopend" target="_blank" onclick="parent.webclient.openWindow(this, 'createmail', 'index.php?load=dialog&task=createmail_standard&to=m.watts@linux-corner.info'); return false;" style="background-color: rgb(255,255,255); font-family: arial, sans-serif; color: rgb(61,84,89); font-size: 13px" href="mailto:m.watts@linux-corner.info">m.watts@linux-corner.info</a>> To: <a title="Deze link naar een extern object zal in een nieuw venster worden geopend" target="_blank" onclick="parent.webclient.openWindow(this, 'createmail', 'index.php?load=dialog&task=createmail_standard&to=spacewalk-list@redhat.com'); return false;" style="background-color: rgb(255,255,255); font-family: arial, sans-serif; color: rgb(61,84,89); font-size: 13px" href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a> Subject: Re: [Spacewalk-list] Best way to manage channels Message-ID: <<a title="Deze link naar een extern object zal in een nieuw venster worden geopend" target="_blank" onclick="parent.webclient.openWindow(this, 'createmail', 'index.php?load=dialog&task=createmail_standard&to=4F1B126A.4040100@linux-corner.info'); return false;" style="background-color: rgb(255,255,255); font-family: arial, sans-serif; color: rgb(61,84,89); font-size: 13px" href="mailto:4F1B126A.4040100@linux-corner.info">4F1B126A.4040100@linux-corner.info</a>> 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. </blockquote> </body> </html>