Abiquo does not support layers that intersect with 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, or Azure Availability Sets.
To create a layer:
Layers ensure that VMs deploy on separate hypervisors, so the following rules apply:
|Layer with deployed VMs|
Web stack use case for layers
The following diagram shows a possible anti-affinity layers use case of a simple web stack.
In Abiquo, you could deploy this configuration as follows:
VMs not in layers: Apache server(s), firewall, load balancer
If the deploy of a virtual appliances with layers 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. Check with your system administrator.
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:
To delete a layer:
The layer will be deleted and the VM will be moved to the general VM area.
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.
To move deployed VMs between layers, you must move the VM out of one layer before you move it into another. You cannot move a deployed VM directly from one layer to another.
To move a deployed VM to a different layer: