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

« Previous Version 7 Next »

Abiquo 5.0 introduces support for Availability Sets in Azure.

This feature has two new privileges:

  • Manage availability sets
  • Assign availability set to VM

Users can create Availability sets for use in virtual datacenters. The name of an availability set must be unique in a tenant's location because the availability set is created in Azure at the level of the location (allowed public cloud region).

After a user creates an Availaiblity set, they can select it when they are create a VM, as for private cloud layers.

The VMs within an Availabilty set must be in the same Azure Virtual Network, which means they must be in the same Abiquo virtual datacenter. 

Before they deploy the VM, to change the Availability set, the user can edit the VM.

If the user does not deploy the VM before the VDC is synchronized, the platform will remove the VM from the Availability set during the synchronization process.

During an upgrade, the platform will detect availability sets that contain deployed VMs. To detect other availability sets, the user should synchronize the virtual datacenter or networks.

For more information about Availability sets, see https://docs.microsoft.com/en-us/azure/virtual-machines/windows/tutorial-availability-sets.


  • No labels