[Spacewalk-list] Patch Baseline Process

[Michael Ward]

Hi everyone,

My apologies if this has already been answered, but I wasn’t able to find anything when I searched. I’m completely new to spacewalk, I’ve read most of the manuals but they seem a bit light on with regards to proper processes, etc so I’m reaching out here in the hope of additional support.

I’d like to set up spacewalk with a couple of patch ‘baselines’. I.e. I’d like a Test/Pilot baseline with patches that are deployed to a test set of systems. After a month or so, I’d clone that baseline to become a release baseline and deploy that on the remainder of my systems. However, to complicate matters, I need to report against the current RHEL base channel so I’m aware of which systems are missing patches based on the current RHEL repositories so I can look at ‘fast tracking’ critical patches if necessary.

At this stage I’m hoping to set up scripts using the API to do something like the following:


  1.  Clone pilot channel to create a release channel every month. Delete the pilot channel.
  2.  Clone base channel to create a new pilot channel.
  3.  Move the systems from the normal base channel to the release channel and apply errata.
  4.  Move the systems back to the normal base channel so reporting functionality works.

Does anyone have any experience with this and able to advise me if the above will work, or if there is some other recommended way of approaching this ?

Regards,
Michael Ward.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20140414/634c81ae/attachment.htm>