A scaling action can be triggered periodically or based on certain rules to adjust resources. Take an online course selection web application as an example. This application is frequently used before a semester starts and seldom used during the semester. You can expand resources for this application based on predictable traffic.
To suit predictable traffic needs, you can configure a scheduled or periodic policy for expanding resources.
Parameter |
Description |
Example Value |
---|---|---|
Policy Name |
Specifies the name of an AS policy. |
as-policy-p6g5 |
Policy Type |
Select Scheduled or Periodic for expanding resources at a specified time. If you select Periodic, you are required to configure two more parameters:
|
N/A |
Triggered At/On |
Specifies a time at which the AS policy is triggered. |
N/A |
Scaling Action |
Specifies an action and the number of instances.
The following scaling action options are available:
|
For example, there are 10 instances in an AS group, and the scaling action is Add 15% instances. When the AS policy is triggered, AS calculates the number of instances to be added is 1.5 and rounds 1.5 down to 1. After the scaling action ends, there are 11 instances in the AS group. |
Cooldown Period |
Specifies a period of time after each scaling action is complete. During the cooldown period, scaling actions triggered by alarms will be denied. Scheduled and periodic scaling actions are not restricted.
NOTE:
|
300s |
The newly added AS policy is displayed on the AS Policy tab. In addition, the AS policy is in Enabled state by default.