...
Abiquo 4.0 introduces horizontal autoscaling of virtual machines through scaling groups created for virtual machines. When 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.
| Div | ||
|---|---|---|
| ||
|
To use autoscaling do these steps:
...
Scaling operations are managed by action plans and subject to all standard Abiquo constraints, such as privileges and allocation limits.
To scale in, Abiquo deletes and undeploys virtual machines without waiting for user confirmation to force the undeploy of virtual machines with disks that are not stored in the Apps library (ISO configuration drive or additional hard disk). Abiquo currently selects the virtual machines to delete or undeploy using first in, first out (FIFO), but in future releases the administrator will be able to select the scale in policy, from last in, first out (LIFO) or FIFO.
To scale out, Abiquo will always create new clones instead of deploying virtual machines that are undeployed, for example, machines that were manually undeployed during maintenance.
...
You cannot create alarms for cloned virtual machines that are part of a scaling group. This is because Abiquo will automatically apply the metrics from the base machine, that will be considered in the activation of the alarms from the base machine.
How do metrics and alarms work with scaling groups?
Abiquo will automatically apply the same metrics configuration from the base machine to the clone machines. And Abiquo will automatically consider the metrics from all of the virtual machines as a group, and use these metrics to determine if the alarms in the base machine should activate. This means that even if the base machine is undeployed, an alarm in the base machine can still activate, based on the performance of the clone 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.
When you leave maintenance mode, Abiquo will apply your modifications to the scaling group, e.g. adding new rules. Then Abiquo will adjust the number of virtual machines in the group to within the minimum and maximum size range.
...
When you delete a scaling group, Abiquo will not destroy the virtual machines. It will place all the virtual machines in the virtual appliance as regular virtual machines and the scaling group constraints will no longer exist.
To delete a scaling group, first put it into maintenance mode, then click the delete button.