While in theory that sonds like a great idea I can see a few problems with doing it that way. 1) don't you have to re-enable the monitoring after the reboot 2) you have enter the actions in every time you push an update any way. 3) there is some planing being done to add a reboot requiered field in the future either throught the errata or the rpm itself the holdup is those are larger dicussions because they don't just effect spacewalk.
For this level of complexity I would either write a script that directly used the apis or use a full scheduler like jobscheduler from SOS Berlin. The scheduler rought is the more robust route because it will allow to define more robust workflows which could be triggered by spacewalk or vica versa On Dec 21, 2012 7:54 AM, "Spacewalk User" <[email protected]> wrote: > ** > > When pushing patches, I need to run remote commands both before and after > the updates, but the UI seems to offer me only one or the other as part of > the update. Is there a way that I have not found to have both a pre- and a > post- transaction command integral to the software update? > > Specifics are that I need to send a "cease monitoring" e-mail to the > network operations center and the server team duty manager, run the update, > then reboot the system. I can schedule one of the commands as a separate > scheduled event, but that's not optimal. > > > Thanks for any tips anyone can offer. > > > > --j. > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
