Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Abiquo 2.6


Skip to end of metadata
Go to start of metadata

It is important that users clearly understand the different states that virtual appliances and virtual machines can have in the Abiquo platform and the differences between them. In order to change the state of virtual machines, users will require the Perform virtual machine actions privilege.

API Feature

In the API the valid virtual machine states are: NOT_ALLOCATED, ALLOCATED, CONFIGURED, ON, PAUSED, OFF, LOCKED and UNKNOWN. See VirtualMachineResource

Virtual Machine States

    • Not Allocated: The virtual machine does not exist on the cloud node; it is just a template of the virtual machine to be deployed. It only exists in Abiquo and the physical machine and other resources are not allocated in the cloud node and it is not consuming resources. For example, if you add a virtual machine template to a virtual machine that is deployed, the virtual machine you just created is not deployed and its state is not allocated. If you undeploy a virtual appliance, then all the virtual machines in the virtual appliance will be undeployed, and these virtual machines will be in the not allocated state.

Screenshot 1: a virtual machine that is not deployed is in the not allocated state.

 

  • Allocated : The virtual machine does not exist on the cloud node but a physical machine has been assigned to it. When you deploy a virtual machine, the first step in the deploy process is the resource scheduling or allocation. After resource allocation, the machine is in the allocated state.
  • Configured: The virtual machine exists on the cloud node. Resources such as network and volumes are allocated to it on the physical machine. After the machine is configured in the hypervisor, the machine is in the configured state.

Both of the above two states are usually short steps in the deploy process. The final step in the deploy process is to power on the virtual machine.

  • On: The virtual machine exists in the cloud node and is running. 

  • Paused: The virtual machine exists on the cloud node and it is suspended.

  • Off: The virtual machine exists in the cloud node but it is not running. Resources are still allocated in the cloud node.

  • Locked: An operation is being performed on the virtual machine.

  • Unknown: Abiquo does not know the current state of the virtual machine but the machine exists on the cloud node. 

    • To delete a virtual machine in the unknown state, you need the "Delete unknown virtual machine" privilege and also access to the enterprise or the Administer all enterprises privilege

Problems Deploying or Configuring a Virtual Machine

If there is a problem with deploying or configuring a virtual machine, you will see a small yellow warning icon on the virtual machine icon within the virtual appliance.

A configuration problem should be accompanied by warnings and error messages in the Events view, including one showing that the reconfigure task has failed.

SOURCE: Abiquo System / SYSTEM /
TIMESTAMP: Fri Jul 27 04:09:53 EDT 2012
ACTION PERFORMED: VM_RECONFIGURE
PERFORMED BY: SYSTEM
STACK TRACE: Reconfigure (task ID 'a65c6c74-0583-4c59-a56b-96c8f51b048c') on virtual machine ID '2' failed: Updating the virtual machine to state 'UNKNOWN'
SEVERITY: CRITICAL

Virtual Machine Tasks

The virtual machine warning symbol is based on the virtual machine task state. Virtual machine tasks are a collection of jobs. For example, a deploy task is made up of jobs to allocate, configure and power on the virtual machine. If a job fails, then the task will also fail and the warning symbol will be displayed on the virtual machine. Virtual machine tasks are automatically cleaned up regularly based on the task trimmer property in the Abiquo Configuration Properties. However, virtual machine task states are not automatically cleaned up.

Delete a Warning Symbol

A warning symbol refers to a previous event but the current status of the platform may be different. Therefore, once the user has seen a warning symbol, it can be acknowledged and deleted.

To acknowledge and delete a warning symbol:

  1. Move the mouse button over the warning symbol. An X will appear over the symbol
  2. Click the X to remove the warning
Delete Warnings for Users of Your Enterprise

A user with the Manage users privilege can acknowledge the warnings for the users of the enterprises they can manage.

 

Virtual Appliance States

  • Deployed: Some or all of the virtual machines are not in the Undeployed state. All the virtual machines exist in the hypervisor and none is in the Unknown or Locked state. Resources are allocated in the cloud node.

  • Not deployed: All the virtual machines are in the Undeployed state. No virtual machines; or none of the virtual machines exist in the hypervisor and none is in the Unknown or Locked state. The virtual appliance can be seen as a template. Resources are not allocated in the cloud node.

  • Needs Sync: This state occurs when a virtual appliance which is in the Deployed state is modified. 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 the  button.

  • Locked: Any of the virtual machines is in the Locked state and none is in the Unknown state.

  • Unknown: Some or all of the virtual machines are in the Unknown state. The virtual appliance state is unknown when the virtual machine states cannot be recovered from the hypervisor. To continue working with this virtual appliance, the system administrator must take action.

Deployed State and Powered Off Virtual Machines

The fact that all the virtual machines in a virtual appliance are powered off does not imply that the virtual appliance is undeployed. In the first case, the virtual appliance is consuming resources because the virtual machines exist in the cloud nodes. In the second case, the virtual appliance is not consuming resources.

  • No labels