...
When scaling, the platform will search for a rule that is valid for the specific time range, or for a default rule. It will create or delete/undeploy the number of VMs in the rule, then wait for the cooldown period before accepting another scaling request. To scale in, Abiquo currently selects the virtual machines to delete or undeploy using first in, first out (FIFO).
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. 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.
Perform maintenance on the scaling group
Maintenance mode temporarily disables autoscaling and enables you to make changes to your VMs (deploy, undeploy, delete etc.) and edit the scaling group. Note that you cannot delete the base VM. Also you cannot create alarms for cloned VMs that are part of a scaling group, because the scaling group alarms are in the base VM. 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.
- To put the scaling group in maintenance mode, click the "cog" maintenance button or trigger an action plan with the action "Scaling group: start maintenance mode"
- To leave maintenance mode, click the "cog" maintenance button again or trigger an action plan with the action "Scaling group: end maintenance mode".
...