[Spacewalk-list] Complex and depending system updates

[Maxime VEROONE]

As we do here, I suggest an automaton script using API calls to list systems
and their properties, direct commands through SSH, VMware API calls and
remote commands.

Problem with remote commands is that they are asynchronous, so if your osad
is broken or lags, your chain of events become unordered.

The only solution is to make an unique remote command with :
1) stop services through a default script whose name is shared by all
systems
2) yum update
3) reboot

Your problem is that you need to execute a script after boot. The only
solution - for me- is to create an init script/systemd service that will be
triggered after reboot like any service startup script and will disable
himself at the end of its code. (that's a bit hackish but it works)

Other solutions implies automation softwares like puppet for example.

Regards,
Maxime Veroone.

-----Message d'origine-----
De : spacewalk-list-bounces at redhat.com
[mailto:spacewalk-list-bounces at redhat.com] De la part de Chris
Envoyé : samedi 27 février 2016 14:19
À : spacewalk-list at redhat.com
Objet : [Spacewalk-list] Complex and depending system updates

Hello,

I have some questions regarding the action chain. We want to use this
technic for our system upgrade process in an iteration manner. Here the
workflow we thought about:

1) execute script to bring down service
2) If exit code 0 apply patches
3) System reboot
4) after reboot execute script to bring back service
5) if exit code 0 start with next server

The script execution is needed because in some cases a simple service xx
stop/start is not sufficient. Does spacewalk provide this features and if
not do you guys have an idea what 3rd party tool can help out?

Thanks in advance!

Cheers,
Chris



_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list