[Spacewalk-list] Spacewalk usage for patch management

[Alexander Dacre]

Hi,

You should look into configuring separate channels for each environment you have.

Once defined, you can then merge content from dev to test, then test to production etc. via the web interface. Alternatively, you can use the API (channel.software.mergePackages) to merge all content or the spacewalk-clone-by-date to only merge errata.

This is what I’m implementing at the moment, with some custom supporting tools written in Go using Kolo’s XMLRPC library.

Thanks,
Alex

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of PenguinWhispererThe .
Sent: 05 August 2014 14:11
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Spacewalk usage for patch management

Hi all,
I want to do patch management on CentOS machines.
But not just push any package that has updates. We should be able to put them in sets. So for example today I check what updates are available.  I want to push these out to staging next week.
If these have been working well, later on the same patches should be installed to the production systems. Even if there are newer updates available only the approved ones should be installed.

All articles/howtos about this subject speak about how to configure spacewalk and it's repositories.
However it's not clear to me if Spacewalk is actually able to do this and what feature I would need for this. Is spacewalk able to accomplish this? What feature do I use? Remarks?

Note that I want this for base/OS packages too. So not only for custom repositories.
Thanks in advance for your response.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20140805/66934521/attachment.htm>