To run a power command on a service:
- Go to the Applications page.
- Select a service.
- From the first menu at the top of the page, choose an available power command for the selected resource:
The following power commands are available for VMs, depending on the VM's power state, the VM's configuration options, the guest OS state and the cloud platform:
- Standby OS: Places the guest operating system in standby mode.
- Reset OS: Resets the guest operating system.
- Shutdown OS: Shuts down the guest operating system.
- Power On: Powers on or resumes the VM.
- Power Off: Places a VM in a non-running state.
If available, use the Shutdown OS command rather than the Power Off command. Use the Power Off command only if the VM isn't responding.
Once the Power Off command is issued for a GCP VM, GCP deletes the persistent disks if this option is configured.
- Suspend: Places a VM in a suspended (or paused) state. Use when you want to free up resources on a short-term basis or put the VM on hold without stopping it (the VM must be running for the command to appear).
- Reset: Places a VM in a non-running state and then restarts it.
If available, use the Reset Guest OS command rather than the Reset command. Use the Reset command only if the VM isn't responding.
If a VM's Power State is Failed, contact your administrator. The Power State is displayed in the State column on the Applications page or on the VM details page.
If you power down a VM that's in an AWS auto scaling group, AWS marks the VM as unhealthy and may terminate and then replace the VM.
Use the Reboot command to reboot a database that has stopped responding. A database must have the status "available" for the Reboot command to be accessible.
Rebooting a database restarts the database engine service and applies any pending modifications to the associated parameter group. Rebooting a database results in a momentary outage of the instance, during which the database status is set to Rebooting.
The following power commands are available for virtual services, depending on the power state and the state of the child VMs' guest operating systems:
- Power On: Place a virtual service and its child VMs in a running state.
- Suspend: Place a virtual service in a suspended state when you want to free up resources on a short-term basis or put the virtual service on hold without stopping it (the virtual service must be running for the command to appear).
- Shutdown OS: Shut down the guest operating systems for the child VMs of the virtual service.
- Power Off: Place a virtual service and its child VMs in a non-running state.
Note that it's best practice to shut down the guest OS of the child VMs of a virtual service rather than just powering off the virtual service.
Configuring the start order of a virtual service (vApp) allows you to handle startup and shutdown dependencies among its children.
The reverse order is used for shutdown.
- You can't specify delays or actions to be performed at startup and shutdown.
- To configure the start order for the children of a nested virtual service, you need to edit the start order of that virtual service directly.
To edit the start order for a virtual service:
- Select the virtual service, then select Actions >Virtual Service > Edit Start Order.
- In the Edit Start Order dialog, use the arrows to move VMs from one group to another.
- All children in a group are started before proceeding to the next group.
- There is no order of precedence within a group, so to control the order, you must move VMs into separate groups.
If you don't have permission to edit the start order, you can instead select View Start Order.