The virtual appliance states are calculated from the VM states as described below. The state name in the table has the color code for the Virtual appliance in each state.
State | Description | ||||||
|---|---|---|---|---|---|---|---|
| There are no VMs in the virtual appliance | ||||||
| All of the VMs are not in the Undeployed state. |
| |||||||
| All the VMs are in the Undeployed state. | ||||||
| This state occurs when a virtual appliance that is in the Deployed state is modified |
. Such as when you add a new VM for example, by adding a new VM. This state indicates that the configuration of the virtual appliance in the cloud node is different to the configuration of the virtual appliance in the Abiquo Server (database). To update the cloud node with the changes, click Deploy all VMs. | |||||||
| One or more of the VMs is in the Locked state and none is in the Unknown state. Note: Virtual appliances awaiting workflow review will be locked with VM state Waiting to be reviewed | ||||||
| Some or all of the VMs are in the Unknown state. The virtual appliance state is unknown when the VM states cannot be recovered from the hypervisor or provider. To continue working with this virtual appliance, the system administrator must take action. |
Some of these states are shown in the virtual appliances lists in following screenshot.
...
| Note |
|---|
Deployed State and Powered Off Virtual Machines The fact that all the VMs in a virtual appliance are powered off does not imply that the virtual appliance is undeployed. |