| Excerpt |
|---|
Abiquo 5.3 will now identify all deployed VMs with their provider ID. This will improve performance and management of VMs and save administrator time. |
This means that Abiquo will not use the VM name to identify VMs in providers. If you use a template named “webserver”, then the default VM name will be “webserver” and when you deploy the VM, it will be named “webserver” in the provider. The Abiquo API does not usually validate VM name that the user supplies and it will directly display provider errors. But for example, in the case of duplicate names in ESXi, when Abiquo catches a duplicate name exception, it appends a number to the VM name and retries the operation.
...
With the introduction of provdier ID as VM identifier, the abiquo.virtualmachine.namesperdc property is deprecated. The platform used this property for VM capture and DRaaS configurations.
For an overview of the migration, see Provider ID as VM identifier upgrade.
For full details of the Abiquo upgrade to version 5.3, see Upgrade Abiquo