Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. In virtual appliance view, select the virtual machineVM, and from the menu on the virtual machine VM icon, select the Create scaling group option
  2. Enter the scaling parameters and rules
  3. Click Save

...

When you save the scaling group, Abiquo will mark the virtual machine VM icon with the scaling group symbol and display the scaling group 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 VMs in the scaling group, including the base machine.

...

To trigger autoscaling operations, create an action plan for the virtual machine VM with the scaling group, and then create triggers to run the action plan. See Manage action plans and triggersWhen 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 out, the platform does not deploy VMs that are undeployed in the scaling group. To clone the base virtual machineVM, the platform will do the following steps:

  1. Create disks using the following:
    1. Copies of content of disks from the VM template
    2. Empty disks or volumes for each additional disk used in the VM
    3. Disk controllers used in the VM
  2. Apply ALL configuration used in the VM, for example:
    1. CPU and RAM
    2. Network connections of the same type (e.g. private network)
    3. Assignment of firewall policies and attachment to load balancers
    4. Chef recipes, backups, cloud-init, variables, and so on
    5. Metrics. The group of metrics from clone machines and the base machine (if it is deployed) can activate alarms in the base machine, even if it is not deployed
    6. Exception – Alarms: the scaling group has only one set of alarms in the base machine

To scale in,  Abiquo currently selects the virtual machines VMs to delete or undeploy using first in, first out (FIFO). The platform deletes and undeploys VMs without requesting user confirmation when there are disks that are not stored in the Apps library (ISO configuration drive or additional hard disk). 

...

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 without deleting the scaling group. 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 VMs in the group to within the minimum and maximum size range.

...