...
To help you detect and address changing demand for resources, the platform's Control control features include monitoring alerts with notifications, action plans for automation, and autoscaling. These features may depend on the configuration of VM monitoring and metrics and Manage cloud alarms, so you may like to set these up first (see VM monitoring and metrics and Manage cloud alarms). To use scaling, you should also define scaling groups for the VMs you want to scale, (see Monitoring and scaling VMs). The Control view has Alert manages Alerts and Action plans tabs.
Basic control and scaling concepts
| Concept | Description |
|---|---|
| Alarm | 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. See Manage cloud alarms and Infrastructure Alarms |
| Alert | An alert enables you to configure notifications or actions from alarms. Alerts are like a worker monitoring a group of alarms; when all the lights for the group are lit up, the alert is activated. Alerts can trigger action plans. See Control View |
| Action plans | A sequence of actions to perform on entities on the platform, such as VMs or scaling groups. An action plan is run by a trigger. |
| Trigger | A trigger is an alert or a schedule that will run the action plan, for example, during times of increased demand. |
| Scaling group | 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 | Vertical scaling means scaling up, adding more resources to an existing VM, for example, boosting your CPU and or RAM capacity. |
| Horizontal scaling | Horizontal scaling means scaling out, deploying more VMs when you need more resources. |
Create Alerts and Alarms
To configure alerts, go to Control → Alerts.
...
| . |
...
...
...
Manage
...
| Panel |
|---|
Privilege: Access alerts section |
Create alerts
Before you create an alert for a group of alarms, do the following steps:
- Retrieve VM built-in metrics, by editing VMs and enabling monitoring (see VM monitoring and metrics) or create custom metrics
- Optionally create metric alarms (see Manage cloud alarms)
To create an alert:
- Go to Control view → Alerts
- Click the + add button
- Enter the alert details
Select an existing alarm, or create a new alarm, and assign it to the alert. Repeat for the required alarms
Click Save
...
action plans
...
Remove alarms from alerts
| Panel |
|---|
Privilege: Access alerts section, Manage alarms, Manage alerts |
To remove an alarm from an alert:
Click the delete button, and confirm
The platform will remove it from this alert, but it will remain in all other alerts that it is associated with
To delete alarms, go to Cloud --> Alarms; see Manage cloud alarms
Manage action plans and triggers
To enable more control over cloud operations, users can create action plans to run tasks on VMs and scaling groups, and to run general tasks.
| Panel |
|---|
Privilege: Access action plans and triggers, Manage action plans and triggers |
Action plans are an important automation functionality on the platform. They can combine tasks for VMs in different providers and have multiple triggers including alerts from custom metrics or built-in metrics. Each VM or scaling group can have multiple action plans.
Create an action plan
Before you create an action plan, you will probably want to create at least one VM.
To create an action plan:
...
- click the + Add button
- select a general action or select a VM or scaling group and a specific action type from the pulldown list
- enter parameters as required
...
and
...
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.
...
To run the action plan automatically, go to the Triggers tab and create an alert or schedule trigger.
Run an action plan now
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.
| Expand | ||
|---|---|---|
| ||
Abiquo recommends that you run an action plan manually to test it before you create a trigger to run it automatically.
Create a trigger
...
triggers
...
To run your action plan based on metrics, you can select an existing alert to trigger an Action plan. Click the + Add button and select the Alert. For details about creating an alert, see #Create Alerts and Alarms
To run your action plan automatically at selected dates and times, create a schedule trigger.
...
Delete an action plan
If you delete an action plan, Abiquo will also delete the schedule associated with that action plan.
Scale out VMs
As an automatic response to changing demands for resources, the platform can scale out by cloning a master VM. And it can scale in, by deleting clone machines and undeploying the master VM.
To use scaling, first define a scaling group, see Monitoring and Scaling VMs
...
...
Pages related to control of VMs
...