Can AS Increase Bandwidths as Required?
Yes. Auto Scaling can increase bandwidths based on specific scenarios.
Scenarios
You can automatically adjust your purchased EIP bandwidth and shared bandwidth using a bandwidth scaling policy. This section describes how to create a bandwidth scaling policy.
When creating a bandwidth scaling policy, you need to configure basic information. The system supports three types of bandwidth scaling policies: alarm-based, scheduled, and periodic.
The basic information for creating a bandwidth scaling policy includes the policy name, resource type, policy type, and trigger condition.
Creating an Alarm-based Bandwidth Scaling Policy
- Log in to the management console.
- Under Compute, click Auto Scaling. In the navigation pane on the left, choose Bandwidth Scaling.
- Click Create Bandwidth Scaling Policy.
- Set parameters, such as the policy name, resource type, policy type, and trigger condition. For details, see Table 1.
Table 1 Alarm policy parameters Parameter
Description
Example Value
Region
Select the region where the bandwidth scaling policy is applied.
-
Policy Name
Enter a name for the bandwidth scaling policy.
The name consists of only letters, digits, underscores (_), and hyphens (-).
-
Resource Type
Select the type of the bandwidth to be adjusted. You can select EIP or Shared bandwidth.
Shared bandwidth
EIP
This parameter is available only when Resource Type is set to EIP.
Select the EIP whose bandwidth needs to be scaled.
NOTE:Only bandwidths of pay-per-use EIPs can be scaled.
-
Policy Type
Select Alarm.
Alarm
Alarm Rule
Choose whether to create a new alarm rule or use an existing one.
If you select Use existing, you can select an alarm rule drop-down list. Alternatively, click Create Alarm Rule on the right to create an alarm rule on the Cloud Eye console. For details, see Creating an Alarm Rule.
If you select Create, configure the following parameters:- Rule Name
Enter a name for the new alarm rule, for example, as-alarm-7o1u.
- Trigger Condition
Select a monitoring metric and trigger condition. Table 2 lists the supported monitoring metrics. An example value is Outbound Traffic Avg. > 100 bit/s.
- Monitoring Interval
Specifies the monitoring period for the metric, for example, 5 minutes.
- Consecutive Occurrences
Specifies the number of consecutive times, for example, one time, for triggering a scaling action during a monitoring period.
-
Alarm Policy Type
This parameter is available only when Policy Type is set to Alarm. The value can be Simplified scaling or Refined scaling.
- If you select Simplified scaling, you can set an action to be performed when a monitored metric hits the configured threshold, for example, Monitored metric >, ≥, <, or ≤ xx.
- If you select Refined scaling, you can set the action to be performed when the monitored metric falls within a range with both an upper and a lower limit, for example, xx ≤ Monitored metric < xx.
Simplified scaling
Scaling Action
Define the scaling action to be performed.
The actions include:- Add
When a scaling action is triggered, the bandwidth is increased.
- Reduce
When a scaling action is triggered, the bandwidth is decreased.
- Set to
The bandwidth is set to a fixed value.
NOTE:The step (minimum unit for bandwidth adjustment) varies depending on the bandwidth value range. The bandwidth will be automatically adjusted to the nearest value according to the actual step.
- If the bandwidth is less than or equal to 300 Mbit/s, the default step is 1 Mbit/s.
- If the bandwidth ranges from 300 Mbit/s to 1,000 Mbit/s, the default step is 50 Mbit/s.
- If the bandwidth is greater than 1,000 Mbit/s, the default step is 500 Mbit/s.
-
Cooldown Period
A cooldown period (in seconds) is the period of time between two scaling actions. AS recounts the cooldown period after a scaling action is complete. During the cooldown period, AS denies all scaling requests triggered by alarm-based policies. Scaling requests triggered manually or by scheduled or periodic policies are not affected.
300s
Table 2 Monitoring metrics supported by the alarm policy Metric
Description
Inbound Bandwidth
Indicates the network rate of inbound traffic.
Inbound Traffic
Indicates the network traffic going into the cloud platform.
Outbound Bandwidth
Indicates the network rate of outbound traffic.
Outbound Traffic
Indicates the network traffic going out of the cloud platform.
Outbound Bandwidth Usage
Indicates the usage of network rate of outbound traffic in the unit of percentage.
- Rule Name
- After setting the parameters, click Create Now.
The newly created bandwidth scaling policy is displayed on the Bandwidth Scaling page and is in Enabled state by default.
Creating an Alarm Rule
When creating an alarm-based bandwidth scaling policy, you can click Create Alarm Rule to the right of Rule Name to create an alarm rule. To do so, perform the following operations:
- Click Create Alarm Rule to the right of Rule Name to switch to the Alarm Rules page of Cloud Eye.
- On the Alarm Rules page, click Create Alarm Rule in the upper right corner.
- Set parameters based on Figure 1 and Table 3. For more information about how to set alarm rules, see Cloud Eye User Guide.
Table 3 Key parameters for creating an alarm rule Parameter
Description
Example Value
Name
Specifies the name of the alarm rule.
alarm-bandwidth
Description
(Optional) Provides supplementary information about the alarm rule.
-
Alarm Type
Select the alarm type to which the alarm rule will apply. The type can be Metric, Event, Website, WAN, or Availability.
Metric
Cloud Product
Select the cloud product you want to monitor. This parameter is only available if you select Metric for Alarm Type.
Virtual Private Cloud - Bandwidths
Resource Level
This parameter is only available if you select Metric for Alarm Type. You can select Cloud product (recommended) or Specific dimension.
Cloud product
Monitoring Scope
Select the resources to which the alarm rule applies. Set this parameter to Specific resources.
Specific resources
Instance
This parameter is available only if Monitoring Scope is set to Specific resources.
Search for the bandwidth using its name or ID. The name and ID can be obtained from the EIP details.
Select the created shared bandwidth.
Method
Select Associate template or Configure manually.
NOTE:If you select Associate template, after the associated template is modified, the policies contained in this alarm rule to be created will be modified accordingly.
Configure manually
Alarm Policy
Configure the alarm policy for triggering the alarm rule as required. For details about the monitoring metrics, see Table 2.
-
- After setting the parameters, click Create.
- On the Create Bandwidth Scaling Policy page, click
to the right of Rule Name, and select the created alarm rule.
Alternatively, you can create an alarm rule on the Cloud Eye console page before creating a bandwidth scaling policy. Ensure that the EIP bandwidth you want to adjust is configured for the alarm rule. After the alarm rule is created, you can select the rule when creating a bandwidth scaling policy.
Creating a Scheduled or Periodic Bandwidth Scaling Policy
- Log in to the management console.
- Under Compute, click Auto Scaling. In the navigation pane on the left, choose Bandwidth Scaling.
- Click Create Bandwidth Scaling Policy.
- Set parameters, such as the policy name, resource type, policy type, and trigger condition. For details, see Table 4.
- After setting the parameters, click Create Now.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
