In private cloud, to create VMs that will always deploy on separate hypervisor hosts, use anti-affinity layers. Each VM in a layer will deploy on a different hypervisor host.
This feature does not enable the high availability of the host, which is a separate feature in platform infrastructure. Abiquo does not support layers that are intersections of other layers. For example, this means that if you have two layers, a VM in the second layer may deploy on the same physical machine as a VM in the first layer.
Ideally you should design and implement your layers before you deploy your VMs.
This feature is not available in public cloud regions. Instead you should use the high availability solution offered by the public cloud, for example, Amazon Availability Zones, which can be accessed by deploying with NICs attached to subnets created in different zones.
Before you begin:
To create a layer:
Layers ensure that VMs deploy on separate hypervisors, so the following rules apply:
|Layer with deployed VMs|
The following diagram shows a possible anti-affinity layers use case of a simple web stack.
In Abiquo, the web stack would look as in the following screenshot.
After you create your layers, deploy the virtual appliance. If the deploy fails, it may be because there are not enough physical machines available in your virtual datacenter. Or some physical machines may be reserved for specific enterprises, for example.
If you have the View datacenter details privilege, you can see the remote access address on the VM details panel. A quick way of checking that the VMs are deployed on separate physical machines is to check the remote access address of the VM, which should be different for each physical machine. If you are an administrator you can also check that the VMs are deployed on separate physical machines in the Infrastructure view.
You cannot make changes to layers that may compromise anti-affinity while your VMs are deployed or running.
Before you begin:
To change the name of a layer:
To remove a VM that is not deployed from an anti-affinity layer, drag the machine outside the layer and into the general VM area
To remove one or more deployed VMs from a layer:
The layer will be deleted and the VM will be moved to the general VM area.
To delete a layer:
Delete a Layer Before it is Empty
You can delete a layer if only one VM remains, even if the VM is deployed and powered on. The VM will remain powered on and it will be moved to the general VM area.
You cannot move a deployed VM directly from one layer to another.
To move a deployed VM to a different layer: