Introduction
Div | ||
---|---|---|
| ||
|
Abiquo 4.0 introduces horizontal autoscaling of virtual machines , where users define a scaling group entity for a base virtual machine. They then create an action plan for the virtual machine with scaling actions, and then create scaling triggers, which are either monitoring alerts for virtual appliances or schedules for planned scaling. through scaling groups created for virtual machines. When a scaling event is triggered, Abiquo will follow the scaling rules of the scaling group. To scale out, it will clone the base virtual machine (with the template disk content) and deploy, and to scale in, it will delete clones or undeploy the base virtual machine.
Info | ||
---|---|---|
| ||
In version 4.0, Abiquo does not clone captured virtual machines, so you will need to create an instance and recreate the virtual machine from the resulting template to use autoscaling |
To use autoscaling do these steps:
- Create a base virtual machine
- Define a scaling group for a base virtual machine, including scaling rules
- Create an action plan for the virtual machine with scaling actions
- Create scaling triggers, which are either monitoring alerts for virtual appliances or schedules for planned scaling
Screenshot: Create scaling group
How does Abiquo clone the base virtual machine
...
- To clone the base virtual machine, Abiquo will do the following steps
- Create disks using the following:
- Copies of content of disks
- from the VM template
- Empty disks or volumes for each additional disk used in the VM
- Disk controllers used in the VM
- Apply ALL configuration used in the VM, for example:
- CPU and RAM
- Network connections of the type (e.g. private network)
- Assign firewall policies and attach to load balancers
- Chef recipes, backups, cloud-init, variables
- , and so on
Does the state of the base virtual machine make a difference?
If the base virtual machine is not deployed, Abiquo will not deploy it. In order to add another virtual machine, Abiquo will clone the base machine and deploy the clone. If the base machine is deployed, Abiquo will count it as one of the active machines in the scaling group. As part of a scale in operation, Abiquo will delete clone machines but it will only undeploy the base machine. Note that if the base machine were deleted directly on the hypervisor, this would destroy the scaling group, whereas if the base machine is undeployed, the scaling group is not vulnerable to interference at the hypervisor level.
Create a scaling group
Abiquo supports horizontal autoscaling with virtual machine scaling groups.
...
- Create and configure a base virtual machine. When a scaling event is triggered, Abiquo will clone this virtual machine according to your scaling rules. The base virtual machine can be deployed or undeployed, as appropriate.
- Abiquo may undeploy the base machine but it will not delete it
...
Include Page | ||||
---|---|---|---|---|
|
When Abiquo creates a you save the scaling group, Abiquo will mark the virtual machine icon changes to display with the scaling group name, symbol and display the scaling group button, the maintenance button, and the name. If necessary, Abiquo will create clones of the base machine and deploy them in order to reach the minimum size. The number in the bottom right-hand corner of the icon is the number of running virtual machines in the scaling group, including the base machine.
Create triggers for autoscaling
...
See Manage action plans and triggers v4.0
...
What are the constraints on VMs in a scaling group
When a virtual machine is part of a scaling group, Abiquo does not allow you to perform deploy or configuration operations on the virtual machine, unless you put the scaling group into maintenance mode.
You cannot create alarms for cloned virtual machines that are part of a scaling group.
What is maintenance mode
Maintenance mode temporarily disables autoscaling and enables you to make changes to your virtual machines, for example, to manually deploy or undeploy machines, or to edit the scaling group itself. Remember that if you manually undeploy virtual machines, Abiquo will not reuse them. Abiquo will always clone the base virtual machine to expand the scaling group.
Note that in maintenance mode you can undeploy the base virtual machine but you cannot delete it; to delete the base virtual machine, you will need to delete the scaling group.
...