| Div | ||
|---|---|---|
| ||
|
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 platform may put VMs into 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
...
| class | privileg |
|---|
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 It marks these VMs with the gray UNKNOWN state label.
...
If the platform later recovers the connection to the hypervisor, it will restore the VMs to their corresponding state.
A user may see a VM in an UNKNOWN state and wish to delete it but this action is protected by a privilege because after you delete the VM, you may also need to check the host machine.
| Panel |
|---|
Privileges: Delete unknown virtual machine |
In addition, if the VM is in another enterprise, you will need the privilege to Allow user to switch enterprise or you will need to log in to the enterprise.
If you do not check the hypervisor after deleting the VM in the platform, the VM may remain in the hypervisor without being registered in the platform. If the information in the platform and in the hypervisor are not consistent, then this may lead to errors or problems.
For example, if the user deletes a persistent VM in an unknown state, then the persistent template will be available to the user. If the user deploys the VM again, then this would create another VM on the hypervisor using the same external disks as the original VM.
This feature 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 featurethe platform.