Versions Compared

Key

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

...

Horizontal scaling of VMs enables users to configure an automatic response to changing demands for resources. To scale out, the platform clones the base VM and deploys the clones. To scale in, Abiquo will delete clone machines but it will just undeploy the base machineScaling operations are subject to all standard Abiquo constraints, such as privileges and allocation limits.

 To clone the base virtual machine, the platform will do the following steps:

...

Info
titleScaling notes
  • Limitation: Abiquo does not clone captured VMs, so you will need to create an instance and recreate the VM from the resulting template to use scaling groups
  • Deploying VMs: The platform does not deploy VMs that are undeployed in the scaling group
  • Undeploying VMs: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). 
  • State of base VM: A scaling group with a deployed base VM would be destroyed if the base VM were deleted directly on the hypervisor. In contrast, a scaling group with an undeployed base VM is not vulnerable to interference at the hypervisor level. 

...

To trigger autoscaling operations, you will need to create an action plan for the virtual machine with the autoscaling scaling group, and then create triggers to run the action plan. Scaling operations are subject to all standard Abiquo constraints, such as privileges and allocation limits. See Manage action plans and triggers

...

When you delete a scaling group, Abiquo will not destroy the virtual machines. It will place all the virtual machines VMs in the virtual appliance as regular virtual machines VMs 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.