...
How does Abiquo clone the base virtual machine?
Abiquo copies the virtual machine’s template from the Apps library to create a new virtual machine and then applies the same virtual machine configuration. First Abiquo will add the same amount of CPU and RAM as in the base machine, and create empty disks and external storage volumes to match the disk configuration, as well as network connections of the same category. Then Abiquo will assign the same firewall policies and connect to the same load balancers. And Abiquo will copy all other configuration, including Chef recipes, backups, cloud-init, variables, and so on.
Does the state of the base 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.
What does the user need to do to prepare for autoscaling?
Users will need to ensure that they have enough resources in their virtual datacenter to deploy up to the maximum number of cloned virtual machines. In particular, users will need to obtain enough available IP addresses of the same category to assign to the clones, for example, by reserving public IP addresses, or by obtaining IP addresses in external networks, or creating private networks.
What restrictions apply to cloned virtual machines?
You cannot create alarms for cloned virtual machines that are part of a scaling group.
How do I create and configure a scaling group?
A user with the privilege to Manage scaling groups can easily create a scaling group from the options menu of the base virtual machine icon.
...
To define how Abiquo will scale the virtual machine group out or in during a scaling event, the user sets scaling rules. Remember that scaling rules do not schedule scaling events. Scaling rules only specify how many clones to create or remove in a scaling event. When scaling in, Abiquo deletes clone machines and/or undeploys the base machine. Scale in rules can be different from scale out rules. If users add a time frame for scaling, Abiquo will only use the rule during this interval. A default rule has no time frame and users can create one default rule for each scaling direction.
What happens when I save the scaling group?
...
How do I set up an autoscaling operation?
To set up an autoscaling operation, you will need to create an action plan for the virtual machine with the scaling group and add an autoscaling action. Action plans can now include the following horizontal autoscaling actions:
Scaling group: Start maintenance
Scaling group: End maintenance
Scaling group: Scale out
Scaling group: Scale in
IMG5
How do I trigger the action plan for the scaling operation?
For Abiquo v4.0 action plans, the Triggers tab replaces the previous Task schedules tab, and you can now configure action plans to be triggered by alerts as well as by schedules.
...
How can I open a scaling group again after I save it?
Click on the scaling group symbol in the top right-hand corner of the virtual machine icon.
...
How can I make changes to the scaling group?
To edit the scaling group and rules, put it into maintenance mode by clicking the “cog” button on the scaling group icon, or in the top right hand corner of an open scaling group.
...
What happens when a scaling event is triggered?
When an autoscaling event is triggered, Abiquo will search for a scaling rule that is valid for the specific time range, or for a default rule. Abiquo will create or delete/undeploy the number of virtual machines for the scaling operation, then wait for the cooldown period before accepting another scaling request. Scaling operations are managed by action plans and subject to all standard Abiquo constraints, such as privileges and allocation limits. In this initial release, Abiquo 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. When scaling out, Abiquo will always create new clones instead of deploying virtual machines that are undeployed, for example, machines that were manually undeployed during maintenance.
Deleting a scaling group
If 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.
...