Abiquo 5.0

Skip to end of metadata
Go to start of metadata



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.

Control and scaling concepts


ConceptDescription
MetricA built-in metric that is provided by a hypervisor or provider (e.g. CPU usage) or a custom metric that the user creates and populates using API calls
AlarmAn 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
AlertAn 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.
Action planA sequence of actions to perform on entities on the platform, such as VMs or scaling groups. An action plan is run by a trigger.
TriggerA trigger is an alert or a schedule that will run the action plan, for example, during times of increased demand. 
Scaling groupFor 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 scalingVertical scaling means scaling up, adding more resources to an existing VM, for example, boosting your CPU and or RAM capacity.
Horizontal scalingHorizontal scaling means scaling out, deploying more VMs when you need more resources. 





Create alerts to notify users and trigger automation

The platform's Alerts feature enables you to track and act upon changes in your cloud environment. To configure Alerts do these steps:

  1. Go to Virtual datacenters → Virtual Appliances → Virtual machines. 
  2. Create and configure your VMs. See Manage Virtual Machines
    1. Remember to go to Monitoring and fetch metrics. See VM monitoring and metrics
  3. Go to Virtual Appliances → Monitoring and check that the platform is retrieving metrics. You may have to wait a few minutes
  4. Create alarms for built-in metrics, scaling group metrics, and custom metrics as required

    1. To create alarms, go to Virtual datacenters → select virtual datacenter → Alarms (see Manage cloud alarms) or Infrastructure → select datacenter → Alarms (see Infrastructure Alarms).

    2. Select an entity, a metric, and a metric statistic and enter a threshold

    3. Save the alarm

  5. Create alerts to notify users

    To create an alert:

    1. Go to ControlAlerts
    2. Click the + add button
    3. Enter the alert details and assign alarms as described below

    4. Click Save


    Field

    Description

    Name

    Name of the alert. The name can contain up to 128 characters

    DescriptionDescribe the alert
    MutedSelect this checkbox to disable action when the alert is activated
    EmailList of email addresses to notify when the alert activates. Click Add email to save an address



    Click the + add button to assign alarms to the alert.

    You must assign at least one alarm to be able to save the alert. Select an existing alarm, or create a new alarm, and assign it to the alert. Repeat for the required alarms

    You can filter the Alarms list by Metric and also if the alarm is Active or not. 


    • You can also use alerts to trigger scaling, see Cloud bursting. 




Configure automation with action plans

You can perform cloud bursting with the platform's Control features. Cloud bursting is automatically deploying new resources in any part of your hybrid cloud environment to meet a peak in demand for resources. Here is a brief outline of how to configure cloud bursting with VM automation.
  1. In your virtual datacenters, create and configure networks 
    1. To optionally use VPNs between VDCs (see Connect virtual networks with VPNaaS), use networks with different addresses, e.g. the default network and a custom network set as the default, see Manage Networks
  2. Create and configure your VMs. See Manage Virtual Machines
    1. Remember to enable metrics. See VM monitoring and metrics.
  3. Define scaling groups for VMs. The base VM can be deployed or undeployed. See Manage Scaling Groups

  4. To use autoscaling in the same provider, while you are creating the scaling group, select the Create autoscaling action option

    1. After you save the scaling group, select the Metric(s) that will drive the scaling

    2. To check and further configure the scaling, click Show more
    3. Optionally add more metrics

The platform will automatically create scaling actions that are driven by alarms and alerts on your metrics. 

To list the alarms, alerts, and action plans created by the platform, display or edit the scaling group.

  1. If the scaling group is not in Maintenance mode, click the magnifying glass information button

If the scaling group is in Maintenance mode, click the pencil edit button

Then go to Autoscaling action and click Show more

You can later display and modify the components of the autoscaling action in the platform. Just go to Virtual datacenters → Alarms, Control → Alerts, and Control → Action plans 

The autoscaling actions configure cloudbursting in the same cloud provider as your original VM with metrics. To configure cloud bursting across providers, you can link an autoscaling group in another provider to your original VM metrics. 

To trigger scaling on a schedule, skip the alarm and alert steps and create an action plan with actions on the scaling group and one or more schedule triggers. You do not need to create alarms and alerts, but you may like to create them anyway, because they can be very useful to help you control your cloud resources.

The following steps describe how to manually enable autoscaling, so that you can configure cloud bursting across providers.

To manually create autoscaling actions:

  1. Deploy VMs
  2. Go to Virtual appliance → Monitoring and check that the platform is retrieving metrics. You may have to wait a few minutes
  3. Create alarms for built-in metrics, scaling group metrics, or custom metrics. See Custom Metrics Resources.  To work with auto-scaling, we recommend that you create alarms for both the high threshold, when you will require more resources, and the low threshold, when these resources can be retired

    1. To create alarms, go to Virtual datacentersAlarms (see Manage cloud alarms) or InfrastructureAlarms (see Infrastructure Alarms).

    2. Select an Entity, a Metric, and a Metric statistic and enter a Threshold, then save the alarm

  4. Create alerts to notify users and to trigger scaling. See Manage Alerts.
  5. Create action plans for cloud bursting and other automation. For example, use scaling actions to add more VMs for your application or to retire VMs that are no longer needed
    General information



    Field

    Description

    Name

    The name of the action plan

    DescriptionA description of the action plan

    Actions


    Action Notes and Parameters table

    ActionNotes and Parameters
    Virtual machine
    Increase CPUvCPUs
    Decrease CPUvCPUs. Not supported by hot-reconfigure. Check OS compatibility
    Increase RAM
    • RAM
    • RAM unit of GB or MB
    Decrease RAM
    • RAM. Not supported by hot-reconfigure. Check OS compatibility
    • RAM unit of GB or MB 
    Resize disk
    • Amount
    • Disk unit of GB or MB
    • Selected disk
    Instance
    • Name for Instance (clone) template. The platform will append the date to the name supplied
    • All disks or selected disks
    Set hardware profileSelect from the available hardware profiles
    General
    Send email
    • Subject
    • Body
    • To (email addresses). Click the add + button to add an email address
    • Cc (copy to these addresses)
    Send webhookSee webhook parameters table
    Scaling group
    Start maintenance


    End maintenance
    Scale in
    Scale out

    Webhook action attributes table


    AttributeDescriptionRequiredDefault value
    EndpointWhere to submit the requesttrue 
    HTTP MethodThe type of request can be GET, POST, or PUTfalseGET
    Expected HTTP status codeIf this status code is returned, continue running the action planfalse204 No Content
    Request headersHeaders such as, secret, authentication, and content-typefalse 
    Request contentRequest bodyfalse 


    When you create actions on VMs also consider the following constraints.

    • User constraintse.g. allocation limits
    • Platform constraints: e.g. to create an instance, the VM must be deployed and powered off 
    • Hypervisor constraints: e.g. when using hot reconfigure on ESXi, you cannot decrement CPU or RAM

    For the API, note that you can request the JSON schema for each action plan entry type from the API.
    See: https://wiki.abiquo.com/api/latest/ActionPlansResource.html#list-action-plan-entry-templates


  6. Add an alert to trigger the action plan or create a schedule to run it
    The platform supports two types of triggers to run action plans: Alerts and Schedules.

    To run your action plan based on metrics, select an existing alert with these steps:

    1. Go to Control → Action plans
    2. Select an action plan
    3. Below the Alerts panel, click the + add button
    4. Select an alert. For details about creating an alert, see Manage Alerts


    To run your action plan automatically at selected dates and times, create a schedule trigger with these steps:

    1. Go to Control → Action plans
    2. Select an action plan
    3. Below the Schedules panel, click the + add button
    4. Enter the details of the schedule

    • To run the action plan at intervals of a fixed number of seconds within a set timeframe:
      1. Select an Interval schedule
      2. Enter the following parameters
        1. Interval seconds: the number of seconds from when the action plan excution starts to when it will start again
        2. Repeat count: the number of times to run the action plan. A value of 0 means repeat forever
        3. Start time: date and time
        4. End time: date and time
    1. After you create an interval schedule, the platform will display the execution count of how many times the action plan has run. If the repeat count is 0, the execution count is null
    • To run an action plan as specified using a Cron-type schedule, select an Advanced schedule and use the calendar selector.



Pages related to control of VMs

  • No labels