...
To help you detect and address changing demand for resources, the virtual appliance has Monitoring and Control features, which include alerts with notifications, action plans for automation, and vertical and horizontal autoscaling. To configure monitoring and control, go to Virtual datacenters, select a virtual appliance and then select the Monitoring or Control tabs. Much of these features depend on the configuration of VM monitoring and metrics and VM Alarms Manage cloud alarms, so you may like to set these up first. You should also create scaling groups for your individual VMs as described below.
...
In order to create alarms that are not associated with alerts, edit your VMs and configure alarms for VM metrics. See VM AlarmsManage cloud alarms.
Display VM alarms and alerts
...
- Enable VM monitoring (see VM monitoring and metrics)
- Optionally create VM alarms (see VM AlarmsManage cloud alarms)
To create an alert for the VMs in a virtual appliance
...
To edit or delete alarms that are not attached to alerts, open the VM and modify it on the Alarms tab; see VM AlarmsManage cloud alarms.
Manage scaling groups
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 machine. Scaling operations are subject to all standard Abiquo constraints, such as privileges and allocation limits.
...
- Open the Control tab of the virtual appliance and click the + button
- Enter the action plan details
- Add actions, by clicking the + Add button, selecting the action type from the pulldown list and entering the parameters as required. Consider the following constraints on actions
- Maintenance block: You can create one complete maintenance block (start maintenance, action(s), and stop maintenance) and the maintenance block cannot contain any scaling actions
- Scale in and/or scale out actions: You can only scale in and/or scale out at the end of the action plan but you can create the scaling action(s) in any order (e.g. scale in first, only scale in)
- Email actions: You can perform an email action at any time, including after scaling actions
- Platform contstraintsconstraints: For example, to create an instance, the VM must be deployed and powered off
- Hypervisor constraints: For example, when using hot reconfigure on ESXi, you cannot decrement CPU or RAM
...