[Spacewalk-list] Spacewalk workflow

[Waldirio Manhães Pinheiro]

Hello Soham, good morning

This subject is relevant by the way there isn't one rule like. Normally who
define the often is the IT guys + security team. I got diff situations like
below
 - Companies that didn't apply erratas, just keep the OS running after
installed
 - Companies that apply relevant errata to that server, for example,
application servers, everything related to webserver / apache / ssl will be
checked
 - Companies that apply all erratas by month, week or quarter.

So again, will be according your necessity / company compliance.

It's one best practice you prepare diff environments just to *test* the new
packages, for example, dev and prod, there are servers in prod environment
*locked channels* and you would like to update this one, before you could
update the dev environment *locked channels* adding the new packages and
testing your machines on that locked channel, if all tests pass, you can
assume the promotion to the production environment will be smooth.

To do this *update* on locked channel, when talking about the SW we will do
via spacewalk-clone-by-date, then feel free to use the link below as
reference
 - https://access.redhat.com/articles/3078

On the link below you will find more information about SW workflow
 -
https://www.amazon.com/Spacewalk-Satellite-Project-solution-management-ebook/dp/B071DDQ4W2/ref=sr_1_1?s=books&ie=UTF8&qid=1492602720&sr=1-1&keywords=spacewalk+satellite

Let me know if you have any additional question or concern.



______________
Atenciosamente
Waldirio
msn: waldirio at gmail.com
Skype: waldirio
Site: www.waldirio.com.br
Blog: blog.waldirio.com.br
LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646
PGP: www.waldirio.com.br/public.html

On Fri, Apr 21, 2017 at 10:19 AM, Soham Chakraborty <dec.soham at gmail.com>
wrote:

> 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/20170421/18dcfa10/attachment.htm>