Documentation can be found on http://onap.readthedocs.io/en/latest
- APPC User Documentation (includes API descriptions, Logging information, Architecture information, etc...)
- APPC Deployment Documentation
Reboot API Definition
The Reboot API definition is temporarily inlcuded here until the APPC LCM Guide in Readthedocs is updated for Casablanca:
The Reboot is used to reboot a VM.
There are two types supported: HARD and SOFT. A SOFT reboot attempts a graceful shutdown and restart of the server. A HARD reboot attempts a forced shutdown and restart of the server. The HARD reboot corresponds to the power cycles of the server.
A “hard Reboot” should succeed when the VM is any of the non-error initial states (active, stopped, paused, suspended). However, “soft Reboot” succeeds only if the VM was already active. If the VM was previously stopped, paused, or suspended, the soft Reboot command may fail.
NOTE: The command implementation is based on OpenStack functionality. For further details, see http://developer.openstack.org/api-ref/compute/.
/restconf /operations/ appc-provider-lcm:reboot
New in 1806.
The type of reboot. Values are HARD and SOFT. If not specified, SOFT reboot is performed.
The self-link URL of the VM.
This is the identity-url associated with the cloud-region. (If not provided, APP-C may automatically use an incorrect identity-url.)
- A successful Reboot of the VM returns a success status code 400 when completed.
- A failed request to reboot the VM returns a failure code 401 and the failure message. Failure messages can include:
- vm-id not available in A&AI
- identity-url not available in A&AI