Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Description

Customers can now control who can delete machines in an UNKNOWN state because after deleting these machines, more checks may be required. Virtual machines may be put in the UNKNOWN state if there is an issue with a connection to the hypervisor. A virtual machine that is in the UNKNOWN state has a blue indicator with a question mark.

In Abiquo 2.4, any user can delete their machine in this state and it could remain in the hypervisor. Therefore, the delete should only be performed by an authorized user who can check the hypervisor to ensure that the virtual machine has been fully destroyed. Otherwise the information in Abiquo may not be consistent with the state of the hypervisor and problems could occur. For example, if the user then redeploys their virtual appliance, this would create another virtual machine on the hypervisor. So there would be two different virtual machines with the same name using the same external disk.

Specifications

In Abiquo 2.6 the "Delete unknown virtual machine" privilege has been added to control deleting virtual machines in an UNKNOWN state. This privilege is displayed in the virtual appliance privileges section. In addition, if the user is in a different enterprise, they will require the privilege to administer all enterprises.

Benefits

This feature enables customers to ensure that information in Abiquo is consistent with the state of the hypervisor. It improves platform stability by enabling greater control over situations such as minor communication failures between the hypervisor and Abiquo.

Limitations

No limitations to note for this feature.




  • No labels