[Spacewalk-list] Spacewalk workflow

[Rick van der Linde]

Hi,





However there may (of course) be many ways to resolve your issue. 



I've got best experiences by setting up these software channels as child channels allowing you to control which child channels should be connected to your hosts.  Also allowing you to control when to connect these softteware channels to your hosts at "tiered" steps, with the assurance to apply the same software/packages to the systems involved.



Hope this helps you



Rick





-----Oorspronkelijk bericht-----
Afzender: Soham Chakraborty <dec.soham at gmail.com>
Verstuurd: Vrijdag 21 April 2017 15:20
Aan: spacewalk-list at redhat.com
Onderwerp: [Spacewalk-list] Spacewalk workflow

Hi all,

I am looking to know how others use spacewalk to do 'tier-ed' patching. 

For example, let's say that I have a group of servers in 'dev' tier and another group of servers in 'qa' tier and the rest being in 'prod' tier, how do I ensure that no *unvetted* patch goes into production? In other words, anything that goes into production, should have been through dev and qa.

I have seen folks using spacewalk-clone-by-date before and there is somewhat extensive discussion in this thread: https://access.redhat.com/discussions/450703

I am interested to hear how people are using the tool in scenarios like monthly or quarterly patching.

Thanks, 

_______________________________________________

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/20170422/b682adfb/attachment.htm>