Configuring a Time AS Policy

Updated on 2024-05-25 GMT+08:00

View PDF

This section describes how to configure a time AS policy. You can configure a time policy to periodically scale instances. This frees you from repeatedly adjusting resources to keep up with service changes and peak pressures, helping you reduce resources and labor costs.

NOTE:

CAE instance scaling is calculated by current and expected metrics.

Expected instances = ceil [Current instances * (Current metrics/Expected metrics)] (ceil is rounded up.)

There is an error tolerance of 10% to prevent frequent fluctuation of instance quantity, so there is no scaling when Current metrics/Expected metric ranges from 0.9 to 1.1.

Application Scenario

This policy is useful for periodic resource usage, mainly in industries such as securities, healthcare, and education.

Procedure

Log in to CAE.
Choose Component Configurations.
Select the target component from the drop-down list in the upper part of the page.

Figure 1 Selecting a component
Click Edit in the AS Policies module.

Select Time and configure the policy by referring to Table 1.

**Table 1** Configuring a time policy
Parameter	Description
Max. Instances	Max. number of instances that can be reached during scale-out. Value range: 1 to 99. NOTE: Max. Instances must be greater than Min Instances.
Min Instances	Min number of instances that can be reached during scale-in. Value range: 1 to 99.
Trigger Cycle	The policy is expected to be executed at a specified interval. Value: Every day, Every day, or Monthly.
Trigger Time in a Day	This parameter is mandatory when Trigger Cycle is set to Every day. Configure the policy triggered every day. For example, the number of instances remains 3 after 18:00 every day. Click Add Trigger Time to add more time policies.
Trigger Time in a Week	This parameter is mandatory when Trigger Cycle is set to Every week. Configure the policy triggered every week. For example, the number of instances remains 4 after 08:00 on every Monday. Click Add Trigger Time to add more time policies.
Trigger Time in a Month	This parameter is mandatory when Trigger Cycle is set to Monthly. Configure the policy triggered every month. For example, the number of instances remains 4 after 06:00 on the fifth day of each month. Click Add Trigger Time to add more time policies.

You can configure time segments to control instance scaling.

For example, set Trigger Cycle to Every day, and set From 18:00 and Instances 3, and From 00:00 and Instances 1. The system keeps 1 instance from 00:00 to 18:00, and 3 instances from 18:00 to 00:00 every day.

Figure 2 Configuring a time policy
Click to enlarge

Click OK.
Click Activate Settings in the upper part of the page. In the dialog box displayed on the right, confirm the configurations and click OK for the configurations to take effect.

Parent topic: Configuring an AS Policy

Previous topic: Configuring a Metric AS Policy

Next topic: Configuring a Hybrid AS Policy

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot