Raymond Dans wrote: > I've recently added an XML/RPC method to SipXSupervisor that will > provide the capability to: > > 1. Check for Updates of SipX software (via Yum) > 2. Query the Version of the installed SipX software (based on one of > the SipX RPMs installed on the system) > 3. Update the SipX software and possibly some OS security fixes on the > box (local or remote) via Yum. > > The results of these commands are stored in output files whose name and > path are returned from the XML/RPC call and will be accessible via > Scott's new file Get method (in order to allow SipXConfig to provide > some sort of progress update). > > The Update capability currently updates the RPMs based on the defined > SipX Yum repositories and once completed performs a restart of SipX. > > After discussions with some of you, I think that for the Software Update > capability, we should simply download and install the rpm's and not do > the SipX restart. Instead, I'd like to add 2 additional commands to the > XML/RPC request. The first new command would be to perform a restart of > SipX and the second would be to perform a reboot of the entire system. > The addition of these new commands would give SipXConfig the ability to > perform a restart or reboot at some later time after the new rpm's have > been downloaded and installed.
I think restart and reboot available through XML/RPC would be useful: if not for updates than for other management operations on servers in a cluster. > > If there are no objections, I'll proceed with implementing these 2 new > capabilities. > > Thanks > Raymond > > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
