Description of problem: ================================= So when a vsphere instance has the vm tools (agent) installed, cloud engine can restart the instance. While testing this out, I noticed that the reboot is actually a hard reset... it seems vsphere has a reboot guest os option and curious if that would be a better api call to use than the reset one Version-Release number of selected component (if applicable): ==================================================================== aeolus-conductor-0.13.18-1.el6cf.noarch deltacloud-core-0.5.0-10.el6_2.noarch deltacloud-core-vsphere-0.5.0-10.el6_2.noarch
Deltacloud api invoke vsphere reboot action, if you look at vsphere client after clicking reboot in conductor it does schedule vsphere-vm-reboot action. If you are using console from vsphere-client there you will not see any shutting down service messages when wm is rebooting, so it may be look like reset but its not true we are invoking proper reboot on vsphere.
While ssh'd into a instance, reboot action from conductor causes "The system is going down for reboot NOW!" to be printed out so it appears this is working correctly.