...
Excerpt | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Web Stack Use Case DiagramThe following diagram shows a possible anti-affinity layers use case of a simple web stack. Web Stack Use Case ScreenshotIn Abiquo, the web stack would look as in the following screenshot. This section gives an example of how to implement this use case. Create an Anti-affinity LayerBefore you create a layer:
To add a new layer, click the add layer button. Enter the layer name.
Create all the layers you require for your virtual appliance. Add virtual machine templates or virtual machines to the layer using drag and drop. Remember that the virtual datacenter must have a separate hypervisor (of the same type) for each machine in a layer. Layers ensure that virtual machines deploy on separate hypervisors, so the following rules apply:
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. Checking Separate DeploymentsIf you have the View datacenter details privilege, you can see the remote access address on the virtual machine details panel. A quick way of checking that the virtual machines are deployed on separate physical machines is to check the remote access address of the virtual machine, which should be different for each physical machine.
Checking Separate Deployments in Infrastructure ViewThe following screenshots of Infrastructure view show the virtual machines in layers deployed on physical machines in Abiquo. Screenshot 1: Physical machine 1 contains Tomcat App server, Database, and Apache servers. Screenshot 2: Physical machine 2 contains: Tomcat App Server, Database, m0n0wall firewall. As the above screenshots show, the virtual machines in layers (Database and App Server) are deployed on separate hypervisors. Modifying an Anti-affinity layerYou cannot make changes to layers that may compromise anti-affinity while your virtual machines are deployed or running. Renaming an Anti-affinity layerTo change the name of the layer, first check that no machines in the layer are deployed. This means that all the virtual machines in the layer should be not deployed. This means that they are in the not allocated state. For example, virtual machines that are newly created in a virtual appliance that is deployed or part of a virtual appliance that has been undeployed. The virtual machines that are not deployed will be shown with the state NOT_ALLOCATED. Move the mouse over the layer and click the edit button. Enter the new layer name If you wish to deploy any new machines, you can deploy them individually or synchronize the virtual appliance to deploy them all together. Remove Machines that are Not Deployed from an Anti-affinity LayerTo remove a virtual machine that is not deployed from an anti-affinity layer:
Remove Deployed Machines from an Anti-affinity LayerTo remove a deployed virtual machine from a layer:
To remove multiple deployed virtual machines from a layer:
Delete an Anti-affinity LayerThe layer will be deleted and the virtual machine will be moved to the general virtual machine area. To delete a layer:
Move Machines Between LayersYou cannot move a deployed machine directly from one layer to another. To move a deployed machine to a different layer:
|
...