Reboot Compute Resource

To reboot the compute resource, use the following request:

PUT /settings/hypervisors/:hypervisor_id/reboot.xml

PUT /settings/hypervisors/:hypervisor_id/reboot.json

XML Request Example 

curl -X PUT http://onapp.test/settings/hypervisors/13/reboot.xml -d '<skip_powered_off_vms_migration>1</skip_powered_off_vms_migration><schedule_failover>1</schedule_failover><force>1</force><confirm>1</confirm>' -u account_email:API_key -H 'Accept: application/xml' -H 'Content-type: application/xml'

JSON Request Example 

curl -X PUT http://onapp.test/settings/hypervisors/13/reboot.json -d '{"skip_powered_off_vms_migration":"1","schedule_failover":"1","force":"1",confirm:"1"}' -u account_email:API_key -H 'Accept: application/json' -H 'Content-type: application/json'

Where:

 skip_powered_off_vms_migration - set 1 to prevent the migration of powered off virtual servers to another compute resource during the reboot

schedule_failover - set 1 to start running virtual servers after the reboot

force - set 1 to stop all virtual servers that cannot be migrated to another compute resource

confirm - set 1 to confirm the reboot of this compute resource

An HTTP 201 response is returned on a successful reboot. Unsuccessful reboot responses include HTTP 404 (resource not found – e.g. if the compute resource isn't online) and HTTP 422 (request cannot be processed – e.g. if parameters were incorrect).

Page History 

v. 6.0 

• added the skip_powered_off_vms_migration parameter