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, so you may like to set these up first. You should also create scaling groups for your individual VMs as described below.
An alarm activates when a metric passes a certain threshold. If you imagine a dashboard for your metrics, alarms are like red lights that light up when conditions change, for example, when there is a problem.
Alerts enable you to configure notifications or actions for the VMs in a virtual appliance. Alerts are like a worker monitoring a group of alarms; when all the lights for the group are lit up, the alert is activated. Abiquo alerts can trigger action plans.
A sequence of actions to perform on a virtual appliance. An action plan is run by a trigger.
A trigger is an alert or a schedule that will run the action plan, for example, during times of increased demand.
For horizontal autoscaling, create a scaling group for a VM with rules to define how the platform should scale it out. You can then include scaling operations in an action plan.
Vertical scaling means adding more resources to an existing VM, for example, boosting your CPU and or RAM capacity.
Horizontal scaling means deploying more VMs when you need more resources.
The Abiquo monitoring system displays VM metrics and the user can configure alerts to trigger actions if certain conditions are met within virtual appliances. If your virtual datacenter supports monitoring, but you don't see any metrics for your virtual appliance, you may need to edit your VMs and configure monitoring on the VM monitoring tab. See VM monitoring and metrics
Then you can configure the display of metrics at the virtual appliance level.
To configure the refresh interval, select the Refresh data every checkbox and enter a number of minutes. Then choose the metrics you wish to display and filter by metric statistics.
Screenshot: filtering metric statistics
You can configure alerts, with their associated alarms, and action plans on the control tab. In order to create an alert, you will need to select or create alarms that will activate when VM metric thresholds are surpassed.
In order to create alarms that are not associated with alerts, edit your VMs and configure alarms for VM metrics. See VM Alarms.
To view a list of alerts and their associated alarms, open the Control tab.
The muted alerts have an alert "speaker" symbol without sound waves. The alerts that are not muted have an alert symbol with sound waves.
Before you create an alert for the VMs in a virtual appliance, edit the VMs and do the following steps:
To create an alert for the VMs in a virtual appliance
Assign existing alarms to the alert, or create new alarms and then assign them to the alert.
If all alarms are activated, the alert will be activated. You can use the alert to trigger actions. See Manage action plans and triggers.
Name of the alert. The name can contain up to 128 characters
|Description||Describe the alert|
|Muted||Select this checkbox to disable action when the alert is activated|
|List of emails to notify when the alert is activated|
|Alarms||You must assign an alarm to save the alert|
To modify or delete an alarm associated with an alert:
To edit or delete alarms that are not attached to alerts, open the VM and modify it on the Alarms tab; see VM Alarms.
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.
To use autoscaling do these steps:
Before you begin:
To create a scaling group:
|Name||Name of the scaling group|
|Default cooldown||Period of time to wait from the start of one scaling operation before allowing another scaling operation|
|Minimum running virtual machines|
The minimum running virtual machines that Abiquo must maintain in the scaling group. The value must be greater than or equal to zero, where zero means that the base machine is not deployed
|Maximum running virtual machines||The maximum running virtual machines that Abiquo must maintain in the scaling group|
|Keep virtual machines in the same layer||Select this option to maintain virtual machine anti-affinity layers when autoscaling|
|Disable workflow||Administrators with the privilege to Manage workflow for scaling groups can use this option to disable workflow or enable it as required.|
|Scaling rules||Scaling rules describe how Abiquo will behave when a scaling event is triggered, for example, by an alert or a schedule.|
|Virtual machines||For a scale out rule, the number of times to clone the base machine and deploy each clone for each scaling step. For a scale in rule, the number of machines to remove from the scaling group (Abiquo will delete clone machines and undeploy the base machine)|
|Cooldown||The cooldown time to wait between scaling operations under this rule|
|Start||Date and time to start the time range when scaling triggers will start a scaling operation under this rule. The time range must be unique and cannot overlap with other rules with the same scaling direction. If there is no time range, then this is a default scaling rule.|
|End||Date and time that is the end of the time range when scaling triggers will start a scaling operation. The time range must be unique and cannot overlap with other rules with the same scaling direction. If there is no time range, then this is a default scaling rule|
When you save the scaling group, Abiquo will mark the 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 VMs in the scaling group, including the base machine.
To open the scaling group and check its parameters, click the scaling group symbol in the top right-hand corner of the VM icon.
To trigger autoscaling operations, create an action plan for the VM with the scaling group, and then create triggers to run the action plan. See Manage action plans and triggers. 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 out, the platform does not deploy VMs that are undeployed in the scaling group. To clone the base VM, the platform will do the following:
To scale in, Abiquo currently selects the 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 VMs in the group to within the minimum and maximum size range.
When you delete a scaling group, Abiquo will place all the VMs in the virtual appliance as regular 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.
To enable more control over cloud operations, users can create VM action plans to run tasks for VMs and Docker workloads.
VM action plans are for both private and public cloud and are an important autoscaling functionality on the platform. A VM can have mutliple action plans
In the user interface, in the Virtual appliances view on the Control tab, users can manage Action plans and Triggers that run the action plans.
Before you create an action plan, first create a VM. To create an action plan:
Put the actions in run order using the arrow buttons. Delete actions as required using the trash can button to the left of the action name.
The name of the virtual machine
The name of the action plan
|Description||A description of the action plan|
See Actions list
See Action parameters table
Action parameters table
|Decrease CPU||vCPUs. Not supported by hot-reconfigure. Check OS compatibility|
To run the action plan automatically, go to the Triggers tab and create an alert or schedule trigger.
When you have added some actions and saved the action plan, you can run the action plan immediately to test it. Edit the action plan and click the Execute action plan button, which is beside the + add button to create a new action.
Abiquo recommends that you run an action plan manually to test it before you create a trigger to run it automatically.
Abiquo supports two types of triggers to run action plans: Alerts and Schedules.
To run your action plan based on monitoring metrics, you can select an existing virtual appliance alert to trigger an Action plan. Click the + Add button and select the Alert. For details about creating an alert, see Manage Monitoring Alerts
To run your action plan automatically at selected dates and times, create a schedule trigger.
If you delete an action plan, Abiquo will also delete the schedule associated with that action plan.