Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 4.4.0 - 10393 - New Control view

...

To help you detect and address changing demand for resources, the platform's 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 v44, so you may like to set these up first. To use scaling, you should also define scaling groups for the VMs you want to scale, see Define scaling for a VM. The Control view has Alert and Action plans tabs. 

Basic control and scaling concepts

Before you work with control features, please familiarize yourself with these basic concepts.

Alarms

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

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. Alerts can notify users and trigger action plans.

Action plans

A sequence of actions to perform on a virtual appliance. 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

To scale out a VM by cloning it, define a scaling group for the VM with rules to specify how the platform should scale it out. You can then include scaling operations in an action plan to automate scaling.

Vertical scaling

Vertical scaling means adding more resources to an existing VM, for example, boosting your CPU and or RAM capacity.

Horizontal scaling

Horizontal scaling means deploying more VMs when you need more resources. 

Create Alerts and Alarms

To configure alerts, go to Control view → Alerts. 

...

Panel

Privilege: Access alerts section


Create alerts

Before you create an alert for a group of alarms, do the following steps:

...

Include Page
GUI Create an alert v44
GUI Create an alert v44

Remove alarms from alerts

Panel

Privilege: Access alerts section, Manage alarms, Manage alerts

...

To delete alarms, go to Cloud --> Alarms; see Manage cloud alarms v44

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. 

...

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 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. 

...

Abiquo recommends that you run an action plan manually to test it before you create a trigger to run it automatically.

Create a trigger

The platform supports two types of triggers to run action plans: Alerts and Schedules.

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.

Include Page
GUI Create task schedule
GUI Create task schedule

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.

...