Enabling an AS Group
Scenarios
You can enable an AS group to automatically scale capacity in or out.
After an AS group is enabled, its status changes to Enabled. AS monitors the AS policy and triggers a scaling action for AS groups only in Enabled state. After an AS group is enabled, AS triggers a scaling action to automatically add or remove instances if the number of instances in the AS group is different from the expected number of instances.
-- Only AS groups in the Disabled state can be enabled.
- Only AS groups in the Abnormal state can be forcibly enabled. You can choose More > Forcibly Enable to enable an abnormal AS group. Forcibly enabling an AS group does not have adverse consequences.
- After you create an AS group and add an AS configuration to an AS group, the AS group is automatically enabled.
- Only AS groups in the Disabled state can be enabled.
- Only AS groups in the Abnormal state can be forcibly enabled. You can choose More > Forcibly Enable to enable an abnormal AS group. Forcibly enabling an AS group does not have adverse consequences.
- After you create an AS group and add an AS configuration to an AS group, the AS group is automatically enabled.
Enabling an AS Group
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.
- In the AS group list, locate the row containing the target AS group and click Enable in the Operation column. You can also click the AS group name and then Enable to the right of Status on the Basic Information page to enable the AS group.
- In the Enable AS Group dialog box, click Yes.
Forcibly Enabling an AS Group
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.
- In the AS group list, locate the row containing the target AS group and select Forcibly Enable from the More drop-down list in the Operation column. You can also click the AS group name and then Forcibly Enable to the right of Status on the Basic Information page to enable the AS group.
- In the Forcibly Enable AS Group dialog box, click Yes.
Forcibly Enabling an AS Group
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.
- In the AS group list, locate the row containing the target AS group and select Forcibly Enable from the More drop-down list in the Operation column. You can also click the AS group name and then Forcibly Enable to the right of Status on the Basic Information page to enable the AS group.
- In the Forcibly Enable AS Group dialog box, click Yes.
Modifying an AS Group
-Scenarios
You can modify an AS group if needed. The values of the following parameters can be changed: Name, Max. Instances, Min. Instances, Expected Instances, Cooldown Period, Health Check Method, Health Check Interval, Enterprise project, Instance Removal Policy, EIP, and Notification Mode.
+Scenarios
You can modify an AS group if needed. The values of the following parameters can be changed: Name, Max. Instances, Min. Instances, Expected Instances, Cooldown Period, Health Check Method, Enterprise project, Instance Removal Policy, EIP, Notification Mode, and Health Check Interval.
Changing the value of Expected Instances will trigger a scaling action. AS will automatically increase or decrease the number of instances to the value of Expected Instances.
If the AS group is not enabled, contains no instances, and has no scaling action ongoing, you can modify Subnet and Load Balancing configurations.
diff --git a/docs/as/umn/as_01_0107.html b/docs/as/umn/as_01_0107.html index 55fa3f24..f79b4071 100644 --- a/docs/as/umn/as_01_0107.html +++ b/docs/as/umn/as_01_0107.html @@ -1,7 +1,7 @@Deleting an AS Group
-Scenarios
You can delete an AS group when it is no longer required.
+Scenarios
You can delete an AS group when it is no longer needed.
- If an AS group is not required during a specified period, you are advised to disable it but not delete it.
- An AS group can be deleted only when it has no instances and no scaling action is being performed.
- When an AS group is deleted, its AS policies and the alarm rules generated based on those AS policies will be automatically deleted.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.
- In the AS group list, locate the row containing the target AS group and choose More > Delete in the Operation column.
- In the displayed Delete AS Group dialog box, click Yes.
- Creating an AS Configuration
- - Creating an AS Configuration from an Existing ECS Instance
+ - Creating an AS Configuration from an Existing ECS
- - Creating an AS Configuration from a New Specifications Template
+ - Creating an AS Configuration from Scratch
- Copying an AS Configuration
diff --git a/docs/as/umn/as_02_0101.html b/docs/as/umn/as_02_0101.html
index f40e0acc..afc63342 100644
--- a/docs/as/umn/as_02_0101.html
+++ b/docs/as/umn/as_02_0101.html
@@ -11,7 +11,7 @@
- Use the created VPC, security group, and EIP for the ECS you create. For instructions about how to create an ECS, see Elastic Cloud Server User Guide.
- When the status of the ECS changes to Running, use Xftp or Xshell to log in to the ECS through its EIP, and install and configure a MySQL database.
- Create an ECS but do not bind an EIP to it. For instructions about how to create an ECS, see Elastic Cloud Server User Guide.
- Unbind the EIP from the ECS where the MySQL database is installed and bind the EIP to the ECS where the Discuz! forum is to be deployed.
You can access the MySQL database through a private network, so the EIP bound to the ECS where the MySQL database is installed can be unbound and then bound to the ECS where the Discuz! forum is to be deployed. This improves resource utilization. For detailed operations, see Virtual Private Cloud User Guide. After binding the EIP, you can access the ECS from the Internet and install various environments, such as PHP and Apache.
+Create an ECS and deploy a Discuz! forum on it.@@ -19,11 +19,11 @@- Create an ECS but do not bind an EIP to it. For instructions about how to create an ECS, see Elastic Cloud Server User Guide.
- Unbind the EIP from the ECS where the MySQL database is installed and bind the EIP to the ECS where the Discuz! forum is to be deployed.
You can access the MySQL database through a private network, so the EIP bound to the ECS where the MySQL database is installed can be unbound and then bound to the ECS where the Discuz! forum is to be deployed. This improves resource utilization. For detailed operations, see Virtual Private Cloud User Guide. After binding the EIP, you can access the ECS from the Internet and install various environments, such as PHP and Apache.
- Deploy the forum.
To learn how to deploy the Discuz! forum, see the officially released Discuz! documentation. When configuring parameters, configure the private IP address of the ECS where the MySQL database is installed for the database server, and use the username and password authorized for remotely accessing the ECS where the MySQL database is installed to access the MySQL database. After the configuration is complete, you can unbind the EIP from the ECS where the forum is deployed to reduce resource usage.
Use the ECS where the Discuz! forum is deployed to create a private image. This private image is used to create the ECSs that will be used for capacity expansion.- Only a stopped ECS can be used to create a private image. Stop the ECS where the Discuz! forum is deployed before creating a private image. For detailed operations, see Elastic Cloud Server User Guide.
- Use the ECS to create a private image. For details, see Image Management Service User Guide.
Create an AS group.
-An AS group consists of a collection of ECS instances, AS configurations, and AS policies that have similar attributes and apply to the same application scenario. An AS group is the basis for enabling or disabling AS policies and performing scaling actions. You must create an AS group to automatically add or remove ECS instances to match changes in traffic to the Discuz! forum.
+An AS group is a collection of ECS instances with the same configurations and AS policies that have similar attributes and apply to the same application scenario. An AS group is the basis for enabling or disabling AS policies and performing scaling actions. You must create an AS group to automatically add or remove ECS instances to match changes in traffic to the Discuz! forum.
For instructions about how to create an AS group, see Creating an AS Group. During the configuration, use the created VPC, subnet, load balancer, and listener.
Create an AS configuration.
The AS configuration lists the basic specifications of the ECSs to be automatically added to the AS group in a scaling action.
-For instructions about how to create an AS configuration, see Creating an AS Configuration from a New Specifications Template. During the configuration, select the private image you created in the preceding step. Configure other parameters based on service requirements.
+For instructions about how to create an AS configuration, see Creating an AS Configuration from Scratch. During the configuration, select the private image you created in the preceding step. Configure other parameters based on service requirements.
Manually add the ECS to the AS group.
On the page providing details about the AS group, click the Instances tab and then Add to add the ECS where the Discuz! forum is deployed to the AS group. For details, see Manual Scaling. You can enable instance protection for this ECS so that it will not be automatically removed from the AS group.
Create an AS policy.
diff --git a/docs/as/umn/as_02_0102.html b/docs/as/umn/as_02_0102.html index 98bf324b..f520c432 100644 --- a/docs/as/umn/as_02_0102.html +++ b/docs/as/umn/as_02_0102.html @@ -1,7 +1,7 @@ -Creating an AS Configuration from an Existing ECS Instance
-Scenarios
You can use an existing ECS instance to rapidly create an AS configuration. In such a case, the parameter settings, such as the ECS type, vCPUs, memory, image, and disk settings (including size, type, encryption, and key) in the AS configuration are the same as those of the selected instance by default.
+Creating an AS Configuration from an Existing ECS
+Scenarios
You can use an existing ECS instance to rapidly create an AS configuration. In such a case, the parameter settings, such as the ECS type, vCPUs, memory, image, and disk settings (including size, encryption, key and type) in the AS configuration are the same as those of the selected instance by default.
Procedure
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Click Create AS Configuration.
- Set the parameters for the AS configuration. Table 1 lists the AS configuration parameters.
-
Table 1 AS configuration parameters Parameter
@@ -16,14 +16,14 @@A region is where an AS configuration resides.
N/A
+-
Name
Specifies the name of an AS configuration.
N/A
+-
Configuration Template
@@ -51,7 +51,7 @@NOTE:If you use an existing key, make sure that you have saved the key file locally. Without the key, you will not be able to log in to your instance.
N/A
+-
Advanced Settings
@@ -59,19 +59,19 @@This allows you to configure User Data.
You can select Do not configure or Configure now.
N/A
+-
User Data
Enables an ECS to automatically inject user data when the ECS starts for the first time. This configuration is optional. If this function is enabled, the ECS automatically injects user data during its first startup.
+Enables an ECS to automatically inject user data when the ECS starts for the first time. This configuration is optional. If this function is enabled, the ECS automatically injects user data upon its first startup.
For details, see Elastic Cloud Server User Guide.
The following two methods are available:
-- As text: allows you to enter the user data in the text box below.
- As file: allows you to inject a script or other files when you create an ECS instance. NOTE:
- For Linux, if you use password authentication, this function is not supported.
- If the selected image does not support user data injection, this function is not supported.
- As text: allows you to enter the user data in the text box below.
- As file: allows you to inject a script or other files when you create an ECS. NOTE:
- For Linux, if you use password authentication, this function is not supported.
- If the selected image does not support user data injection, this function is not supported.
N/A
+-
Creating an AS Configuration from a New Specifications Template
+Creating an AS Configuration from Scratch
Scenarios
If you have special requirements on the ECS instances for resource expansion, use a new specifications template to create the AS configuration. In such a case, ECS instances that have the specifications specified in the template will be added to the AS group in scaling actions.
Procedure
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Click Create AS Configuration.
- Set the parameters for the AS configuration. Table 1 lists the AS configuration parameters.
@@ -23,7 +23,7 @@
Specifies the name of the AS configuration to be created.
N/A
+-
Configuration Template
@@ -40,12 +40,12 @@For more information, see Elastic Cloud Server User Guide.
Configure the ECS specifications, including vCPUs, memory, image type, and disk, according to the ECS type.
Memory-optimized ECS
+Memory-optimized
Image
- Public image
A public image is a standard, widely used image. It contains an OS and preinstalled public applications and is available to all users. You can configure the applications or software in the public image as needed.
+- Public image
A public image is a standard, widely used image. It contains an OS and preinstalled public applications and is available to all users. If a public image does not contain the applications or software you need, you can use the public image to create a cloud server and then deploy required software as needed.
- Private image
A private image is an image available only to the user who created it. It contains an OS, preinstalled public applications, and the user's private applications. Using a private image to create ECSs frees you from configuring multiple ECSs repeatedly.
NOTE:If you select an encrypted image, you must grant key management system (KMS) access rights to EVS. Otherwise, encryption cannot be used. If you have rights granting permission, grant the KMS access rights to EVS. If you do not have the permission, contact the user having the security administrator rights to grant the KMS access rights. For details, see Identity and Access Management User Guide.
- Encrypted: indicates that the image has been encrypted.
- KMS Key Name: specifies the name of the key used by the encrypted image. By default, the name is ims/default.
- Xrole Name: EVSAccessKMS: indicates that EVS has obtained the KMS access rights.
- Data Disk
You can create multiple data disks for an ECS instance and encrypt them. In addition, you can specify a data disk image for exporting data.
-When encrypting a data disk, select Encryption for it. KMS access rights must be granted to EVS for using the encryption feature. If you have rights granting permission, grant the KMS access rights to EVS. If you do not have the permission, contact the user having the security administrator rights to grant the KMS access rights. For details, see Identity and Access Management User Guide.
-- Xrole Name: EVSAccessKMS: indicates that EVS has obtained the KMS access rights.
- KMS Key Name: specifies the name of the key used by the encrypted data disk. By default, the name is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
When encrypting a data disk, select Encryption for it. KMS access rights must be granted to EVS for using the encryption feature. If you have rights granting permission, grant the KMS access rights to EVS. If you do not have the permission, contact the user having the security administrator rights to grant the KMS access rights. For details, see Identity and Access Management User Guide.
+- Xrole Name: EVSAccessKMS: indicates that EVS has obtained the KMS access rights.
- KMS Key Name: specifies the name of the key used by the encrypted data disk. By default, the name is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
For more information about EVS disk encryption, see Elastic Volume Service User Guide.
- Public image
Controls ECS access within or between security groups by defining access rules. ECSs added to a security group are protected by the access rules you define.
N/A
+-
EIP
An EIP is a static public IP address bound to an ECS in a VPC. Using the EIP, the ECS provides services externally.
The following options are provided:
-- Do not use: An ECS without an EIP cannot access the Internet. However, it can still be used as a service ECS or deployed in a cluster on a private network.
- Automatically assign: An EIP with a dedicated bandwidth is automatically assigned to each ECS. You can set the bandwidth size. If you select Automatically assign, you need to specify EIP Type, Billed By, and Bandwidth.
- Do not use: An ECS without an EIP cannot access the Internet. However, it can still be used as a service ECS or deployed in a cluster on a private network.
- Automatically assign: An EIP with a dedicated bandwidth is automatically assigned to each ECS. You can set the bandwidth size.
Automatically assign
NOTE:-If you use an existing key, make sure that you have saved the key file locally. Without the key, you will not be able to log in to your instance.
N/A
+-
Advanced Settings
This parameter allows you to configure User Data.
+This allows you to configure User Data.
You can select Do not configure or Configure now.
N/A
+-
User Data
Enables an ECS to automatically inject user data when the ECS starts for the first time. This configuration is optional. After this function is enabled, the ECS automatically injects user data during its first startup.
+Enables an ECS to automatically inject user data when the ECS starts for the first time. This configuration is optional. If this function is enabled, the ECS automatically injects user data upon its first startup.
For details, see Elastic Cloud Server User Guide.
The following methods are available:
- As text: allows you to enter the user data in the text box below.
- As file: allows you to inject script files or other files when you create an ECS. NOTE:
- For Linux, if you use password authentication, this function is not supported.
- If the selected image does not support user data injection, this function is not supported.
N/A
+-
-Scenarios
You can copy an existing AS configuration.
When copying an AS configuration, you can modify parameter settings, such as the configuration name, ECS specifications, and image of the existing AS configuration to rapidly add a new AS configuration.
Procedure
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Click the AS Configurations tab, locate the row containing the target AS configuration, and click Copy in the Operation column.
- On the Copy AS Configuration page, modify parameter settings, such as Name, Specifications, and Image.
- Click OK.
Procedure
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Click the AS Configurations tab, locate the row containing the target AS configuration, and click Copy in the Operation column.
- On the Copy AS Configuration page, modify parameter settings, such as Name, Specifications, and Image, and configure the ECS login mode (key pair) based on service requirements.
- Click OK.
diff --git a/docs/as/umn/as_03_0102.html b/docs/as/umn/as_03_0102.html index 196e7a01..ce139b94 100644 --- a/docs/as/umn/as_03_0102.html +++ b/docs/as/umn/as_03_0102.html @@ -1,7 +1,8 @@Creating an AS Policy
-Scenarios
You can manage instances in an AS group through AS policies. This section describes how to create an AS policy.
+Scenarios
You can create different types of AS policies. In an AS policy, you can define the conditions for triggering a scaling action and what operation to be performed. When the conditions are met, AS automatically triggers a scaling action to adjust the number of instances in the AS group.
+This section describes how to create alarm-based, scheduled, or periodic AS policy for an AS group.
Creating an Alarm Policy
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Locate the row containing the target AS group and click View AS Policy in the Operation column.
- On the AS Policies page, click Add AS Policy.
- Set the parameters listed in Table 1.
-
- Click OK.
The newly added AS policy is displayed on the AS Policy tab. In addition, the AS policy is in Enabled state by default.
+ - Click OK.
The newly added AS policy is displayed on the AS Policies tab. In addition, the AS policy is in Enabled state by default.
Creating a Scheduled or Periodic Policy
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Locate the row containing the target AS group and click View AS Policy in the Operation column.
- On the AS Policies page, click Add AS Policy.
- Configure the parameters listed in Table 2.
@@ -97,7 +98,7 @@
-
N/A
+-
Specifies the time at which the AS policy is triggered.
N/A
+-
Cooldown Period
To prevent an alarm policy from being repeatedly invoked by the same event, you can set a cooldown period.
-Specifies how long any alarm-triggered scaling action will be disallowed after a previous scaling action is complete.
-The cooldown period does not apply to scheduled or periodic scaling actions. However, AS recounts the cooling duration after a scheduled or periodic scaling action is complete.
+To prevent an alarm-based policy from being repeatedly triggered by the same event, you can set a 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.
For example, suppose that the cooldown period is set to 300 seconds (5 minutes), and a scheduled policy is specified to trigger a scaling action at 10:32, and a previous scaling action triggered by an alarm policy ends at 10:30. Any alarm-triggered scaling action will then be denied during the cooldown period from 10:30 to 10:35, but the scaling action scheduled for 10:32 will still take place. If the scheduled scaling action ends at 10:36, a new cooldown period starts at 10:36 and ends at 10:41.
-NOTE:- If a scaling action is triggered by an AS policy, the cooldown period is whatever configured for that AS policy.
- If a scaling action is triggered by manually changing the expected number of instances or by other actions, the cooldown period is whatever configured for the AS group.
NOTE:- If a scaling action is triggered by an AS policy, the cooldown period is whatever configured for that AS policy.
- If a scaling action is triggered by manually changing the expected number of instances or by other actions, the cooldown period is whatever configured for the AS group.
- When an AS group scales out, scale-in requests triggered manually or by scheduled or periodic policies will be executed immediately after the scale-out is complete, without being affected by the cooldown period.
- When an AS group scales in, scale-out requests triggered manually or by scheduled or periodic policies will be executed immediately after the scale-in is complete, without being affected by the cooldown period.
300
@@ -148,7 +149,7 @@
- Public image
- Click OK.
The newly added AS policy is displayed on the AS Policy tab. In addition, the AS policy is in Enabled state by default.
+
- Click OK.
The newly added AS policy is displayed on the AS Policies tab. In addition, the AS policy is in Enabled state by default.
diff --git a/docs/as/umn/as_03_0103.html b/docs/as/umn/as_03_0103.html index 1a5a7542..3e0b333b 100644 --- a/docs/as/umn/as_03_0103.html +++ b/docs/as/umn/as_03_0103.html @@ -13,7 +13,7 @@ If you have created scheduled or periodic AS policies that are invoked at the same time, AS will execute the one created later. This constraint does not apply to alarm-triggered AS policies.
Disabling an AS Policy
If you do not want a particular AS policy to trigger any scaling actions within a specified period of time, you can disable it.
- If all of the AS policies configured for an AS group are disabled, no scaling action will be triggered for this AS group. However, if you manually change the value of Expected Instances, a scaling action will still be triggered.
- You can disable an AS policy only when its status is Enabled.
Locate the row containing the target AS group and click View AS Policy in the Operation column. On the displayed page, locate the row containing the target AS policy and click Disable in the Operation column. To concurrently disable multiple AS policies, select these AS policies and click Disable in the upper part of the AS policy list.
+Locate the row containing the target AS group and click View AS Policy in the Operation column. On the displayed page, locate the row containing the target AS policy and click Disable in the Operation column. To concurrently disable multiple AS policies, select these AS policies and click Disable in the upper part of the AS policy list.
Manually Executing an AS Policy
You can make the number of instances in an AS group reach the expected number of instances immediately by manually executing an AS policy.
- You can manually execute an AS policy if the scaling conditions configured in the AS policy are not met.
- You can manually execute an AS policy only when the AS group and AS policy are both in Enabled state.
Locate the row containing the target AS group and click View AS Policy in the Operation column. On the displayed page, locate the row containing the target AS policy and click Execute Now in the Operation column.
@@ -21,8 +21,8 @@
Deleting an AS Policy
You can delete an AS policy that will not be used for triggering scaling actions.
An AS policy can be deleted even when the scaling action triggered by the policy is in progress. Deleting the AS policy does not affect a scaling action that has already started.
-Locate the row containing the target AS group and click View AS Policy in the Operation column. On the displayed page, locate the row containing the target AS policy and choose More > Delete in the Operation column.
-To concurrently delete multiple AS policies, select these AS policies and click Delete in the upper part of the AS policy list.
+Locate the row containing the target AS group and click View AS Policy in the Operation column. On the displayed page, locate the row containing the target AS policy and choose More > Delete in the Operation column.
+To concurrently delete multiple AS policies, select these AS policies and click Delete in the upper part of the AS policy list.
diff --git a/docs/as/umn/as_04_0100.html b/docs/as/umn/as_04_0100.html index 5c4fec74..169b2126 100644 --- a/docs/as/umn/as_04_0100.html +++ b/docs/as/umn/as_04_0100.html @@ -14,6 +14,8 @@- Viewing a Scaling Action
+
- Managing Lifecycle Hooks
+- Configuring Instance Protection
diff --git a/docs/as/umn/as_04_0103.html b/docs/as/umn/as_04_0103.html index 33557b22..c6658526 100644 --- a/docs/as/umn/as_04_0103.html +++ b/docs/as/umn/as_04_0103.html @@ -1,23 +1,69 @@
Manual Scaling
-Scenarios
You can manually add or remove instances to or from an AS group, or change the expected number of instances.
+-Scenarios
You can change the size of an AS group manually. You can either add or remove instances to or from the AS group, or modify the expected number of instances of the AS group.
Procedure
Adding instances to an AS group
++Procedure
Adding an instance to an AS group
+Before you add an instance to an AS group, ensure that the conditions below are met. +-+
+Table 1 Conditions for manually adding an instance to an AS group Item
+Condition
+AS group
+- The AS group is in the Enabled status.
- The AS group does not have ongoing scaling actions.
- The number of instances to be added plus the expected number of instances cannot exceed the maximum number of instances of the AS group.
Instance
+- The instance to be added is not a member of another AS group.
- The instance is in the same VPC as the AS group.
- A maximum of 10 instances can be added to an AS group at a time.
- If the AS group has an attached load balancer, the instances will be associated with the load balancer.
If an AS group is enabled and has no ongoing scaling action, and the current number of instances is less than the maximum, you can manually add instances to the AS group.
-Before adding instances to an AS group, ensure that the following conditions are met:
-- The instances are not in other AS groups.
- The instances are in the same VPC as the AS group.
- The instances are in the AZs used by the AS group.
- After the instances are added, the total number of instances is less than or equal to the maximum number of instances allowed.
- Up to 10 instances can be added at a time.
To add instances to an AS group, perform the following steps:
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Click the AS Groups tab and then the name of the target AS group.
- On the AS group details page, click the Instances tab and then Add.
- Select the instances to be added and click OK.
Removing instances from an AS group
-You can remove an instance from an AS group, update the instance or fix an instance fault, and add the instance back to the AS group. An instance removed from the AS group no longer carries any application traffic.
-You can modify the AS configuration for an AS group at any time, but the new configuration will not be applied to any instances that are running. To apply the new configuration, stop an instance, and the system will replace it with a new one that has the specifications specified in the new configuration. You can also remove the instance from the AS group, update the instance, and add then instance back to the AS group.
-There are some restrictions on instance removal:
-- The AS group cannot have a scaling action in progress, the instances must be enabled, and the total number of instances after removal cannot be less than the minimum number of instances specified.
- Instances can be removed from an AS group and deleted only if the AS group has no scaling action ongoing, and the instances are automatically created and enabled, and are not used by Storage Disaster Recovery Service (SDRS).
- Instances manually added to an AS group can only be removed. They cannot be removed and deleted.
- A maximum of 10 instances can be removed at a time.
To remove an instance from an AS group, perform the following steps:
-- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Click the AS Groups tab and then the name of the target AS group.
- Click the Instances tab, locate the row containing the target instance, and click Remove or Remove and Delete in the Operation column.
- To delete multiple instances from an AS group, select the check boxes in front of them and click Remove or Remove and Delete.
To delete all instances from an AS group, select the check box on the left of Name and click Remove or Remove and Delete.
+Removing an instance from an AS group
+You can remove an instance from an AS group, update the instance or fix an instance fault, and add the instance back to the AS group. After the instance is removed from the AS group, it no longer processes any application traffic.
+For example, you can change AS configuration for an AS group at any time. New instances will be created using the new configuration, but existing instances in the AS group are not affected. To update the existing instances, you can stop them so that they can be replaced automatically. You can also remove the instances from the AS group, update them, and then add them back to the AS group.
+When you remove instances from an AS group, consider the restrictions below. +++
+Table 2 Constraints on manually removing an instance from an AS group Item
+Constraint
+AS group
+- The AS group is in the Enabled status.
- The AS group does not have ongoing scaling actions.
Instance
+- The instances are in the Enabled lifecycle status.
- The instances are not used by SDRS.
+ - A maximum of 50 instances can be removed from to an AS group at a time.
- If the number of instances you are removing decreases the number of instances in the AS group below the minimum number of instances allowed, AS launches new instances to maintain the expected capacity.
- If you remove instances from an AS group that has an associated load balancer, the instances will be dissociated from the load balancer.
To remove instances from an AS group, perform the following steps:
+- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Click the AS Groups tab and then the name of the target AS group.
- Click the Instances tab, locate the row containing the desired instance, and click Remove or Remove and Delete in the Operation column.
To remove multiple instances from the AS group, select the check boxes in front of them and click Remove or Remove and Delete.
+To remove all instances from the AS group, select the check box on the left of Name and click Remove or Remove and Delete.
++ - If the instances you want to remove were automatically added to the AS group, they are billed on a pay-per-use basis by default. You can:
- Remove the instances from the AS group by choosing Remove.
- Remove the instances from the AS group and delete them by choosing Remove and Delete.
- If the instances were manually added to the AS group, they can only be removed. They cannot be removed and deleted.
- If the instances you want to remove were automatically added to the AS group, they are billed on a pay-per-use basis by default. You can:
Changing the expected number of instances
Manually change the expected number of instances to add or reduce the number of instances in an AS group for expanding resources.
For details, see Modifying an AS Group.
diff --git a/docs/as/umn/as_04_0104.html b/docs/as/umn/as_04_0104.html index 82b7469c..064a2067 100644 --- a/docs/as/umn/as_04_0104.html +++ b/docs/as/umn/as_04_0104.html @@ -1,10 +1,10 @@Configuring an Instance Removal Policy
-When instances are automatically removed from your AS group, the instances that are not in the currently used AZs will be removed first. Besides, AS will check whether instances are evenly distributed in the currently used AZs. If the load among AZs is unbalanced, AS balances load among AZs when removing instances. If the load among AZs is balanced, AS removes instances following the pre-configured instance removal policy.
+When instances are automatically removed from your AS group, the instances that are not in the currently used AZs will be removed first. Then the instance removal policy you select will be applied.
AS supports the following instance removal policies:
- Oldest instance: The oldest instance is removed from the AS group first. Use this policy if you want to upgrade instances in an AS group to a new ECS type. You can gradually replace instances of the old type with instances of the new type.
- Newest instance: The newest instance is removed from the AS group first. Use this policy if you want to test a new AS configuration but do not want to keep it in production.
- Oldest instance created from oldest AS configuration: The oldest instance created from the oldest configuration is removed from the AS group first. Use this policy if you want to update an AS group and phase out the instances created from a previous AS configuration.
- Newest instance created from oldest AS configuration: The newest instance created from the oldest configuration is removed from the AS group first.
diff --git a/docs/as/umn/as_04_0107.html b/docs/as/umn/as_04_0107.html index 63305055..65a117fc 100644 --- a/docs/as/umn/as_04_0107.html +++ b/docs/as/umn/as_04_0107.html @@ -1,7 +1,7 @@ Manually added instances are the last to be removed, and if AS does remove a manually added instance, it only removes the instance. It does not delete the instance. If multiple manually added instances must be removed, AS preferentially removes the earliest-added instance first.
+ Manually added instances are the last to be removed. If AS does remove a manually added instance, it only removes the instance. It does not delete the instance. If multiple manually added instances must be removed, AS preferentially removes the earliest-added instance first.
diff --git a/docs/as/umn/as_04_0105.html b/docs/as/umn/as_04_0105.html index a1f72678..3fd4a7ab 100644 --- a/docs/as/umn/as_04_0105.html +++ b/docs/as/umn/as_04_0105.html @@ -7,7 +7,7 @@- Log in to the management console.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Click the AS Groups tab and then the name of the target AS group.
- Click the Monitoring tab and view scaling actions. On the Monitoring page, you can view changes in the number of instances and metrics such as CPU Usage.
Viewing Historical Scaling Actions
The following steps illustrate how to view the historical records of scaling actions of an AS group.
-- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Click the AS Groups tab and then the name of the target AS group.
- Click the Scaling Actions tab. This page displays historical scaling actions of an AS group, including instance scaling and load balancer migration.
Scaling Action ID, Status, Scaling Action Type, Description, Start Time, and End Time of scaling actions are displayed. Click
+
before the scaling action ID to view the resource name, status, and failure cause. You can also use the filtering function in the upper right corner to view scaling actions in a specified period.- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Click the AS Groups tab and then the name of the target AS group.
- Click the Scaling Actions tab. This page displays historical scaling actions of an AS group, including instance scaling and load balancer migration.
Scaling Action ID, Status, Scaling Action Type, Description, Start Time, and End Time of scaling actions are displayed. Click
before the scaling action ID to view the resource name, status, and failure cause. You can also use the filtering function in the upper right corner to view scaling actions in a specified period.
Configuring Instance Protection
-Scenarios
To control whether a instance can be removed automatically from an AS group, use instance protection. Once configured, when AS automatically scales in the AS group, the instance that is protected will not be removed.
+Scenarios
To control whether an instance can be removed automatically from an AS group, use instance protection. Once configured, when AS automatically scales in the AS group, the instance that is protected will not be removed.
Prerequisites
Instance protection does not protect instances from the following:- Health check replacement if the instance fails health checks
- Manual removaldiff --git a/docs/as/umn/as_05_0103.html b/docs/as/umn/as_05_0103.html index f29fad86..3363f3cd 100644 --- a/docs/as/umn/as_05_0103.html +++ b/docs/as/umn/as_05_0103.html @@ -3,7 +3,7 @@
- Instance protection does not protect unhealthy instances because such instances cannot provide services.
- By default, instance protection does not take effect on the ECSs that are newly created in or added to an AS group.
- If an instance is removed from an AS group, its instance protection setting is lost.
Managing a Bandwidth Scaling Policy
Scenarios
You can adjust the bandwidth through a bandwidth scaling policy.
This section describes how to manage bandwidth scaling policies, including enabling, disabling, modifying, deleting, and immediately executing a bandwidth scaling policy.
- The bandwidth scaling policy configured for a released EIP still occupies the policy quota. Only the account and its IAM users with the global permission can manage the bandwidth scaling policy.
+ The bandwidth scaling policy configured for a released EIP still occupies the policy quota. Only the account and its IAM users with the global permissions can manage the bandwidth scaling policy. IAM users with permissions to some enterprise projects cannot manage the policy.
Enabling a Bandwidth Scaling Policy
A bandwidth scaling policy can be enabled only when its status is Disabled.
diff --git a/docs/as/umn/as_06_0100.html b/docs/as/umn/as_06_0100.html index 090204c9..aa6aa6c2 100644 --- a/docs/as/umn/as_06_0100.html +++ b/docs/as/umn/as_06_0100.html @@ -8,6 +8,8 @@- Recording AS Resource Operations
+
- Querying Real-Time Traces
+- Adding Tags to AS Groups and Instances
- Monitoring Metrics
diff --git a/docs/as/umn/as_06_0101.html b/docs/as/umn/as_06_0101.html index b895c9c9..f8815ed2 100644 --- a/docs/as/umn/as_06_0101.html +++ b/docs/as/umn/as_06_0101.html @@ -1,11 +1,15 @@Health Check
-A health check removes abnormal instances from an AS group. Then, AS adds new instances to the AS group so that the number of instances is the same as the expected number. There are two types of AS group health checks.
-- ECS health check: checks ECS instance running status. If an instance is stopped or deleted, it is considered abnormal. ECS health check is the default health check mode for an AS group. The AS group periodically uses the check result to determine the running status of every instance in the AS group. If the health check results show that an instance is unhealthy, AS removes the instance from the AS group.
- ELB health check: determines ECS instance running status using a load balancing listener. If the AS group uses load balancers, the health check method can also be ELB health check. If you add multiple load balancers to an AS group, an ECS instance is considered to be healthy only when all load balancers detect that the instance status is healthy. If any load balancer detects that an instance is unhealthy, the instance will be removed from the AS group.
In both ECS health check and ELB health check methods, AS removes unhealthy instances from AS groups. However, the removed instances are processed differently in the following two scenarios:
-For instances automatically added to an AS group during scaling actions, AS removes and deletes them. For instances manually added to an AS group, AS only removes them from the AS group.
-When an AS group is disabled, checking instance health status continues. However, AS will not remove instances.
++Health Check Methods
A health check removes unhealthy instances from an AS group. Then, AS adds new instances to the AS group so that the number of instances is the same as the expected number. There are two types of AS group health checks.
+- ECS health check: checks the ECS instance running status. If an instance is stopped or deleted, it is considered abnormal. ECS health check is the default health check mode for an AS group. The AS group periodically uses the check result to determine the running status of every instance in the AS group. If the health check results show that an instance is unhealthy, AS removes the instance from the AS group.
- ELB health check: determines ECS running status using a load balancing listener. If the AS group uses load balancers, the health check method can also be ELB health check.
If you add multiple load balancers to an AS group, an ECS instance is considered to be healthy only when all load balancers detect that the instance is healthy. If any load balancer detects that an instance is unhealthy, the instance will be removed from the AS group.
+ +
In both ECS health check and ELB health check modes, AS removes unhealthy instances from the AS group. Whether a removed instance will be deleted depends on how the instance is added to the AS group.
+If the instance is automatically added to the AS group during a scaling action, AS removes and deletes it. If the instance is manually added to the AS group, AS only removes it from the AS group.
+Constraints
- Even when an AS group is disabled, AS still checks the health of instances in the AS group, but does not remove unhealthy instances.
diff --git a/docs/as/umn/as_06_0103.html b/docs/as/umn/as_06_0103.html index b5f89092..0c38fe0a 100644 --- a/docs/as/umn/as_06_0103.html +++ b/docs/as/umn/as_06_0103.html @@ -1,10 +1,10 @@Recording AS Resource Operations
-Scenarios
AS can use the Cloud Trace Service (CTS) to record resource operations. CTS can record operations performed on the management console, operations performed by calling APIs, and operations triggered within the cloud system.
-If you have enabled CTS, when a call is made to the AS API, the operation will be reported to CTS which will then deliver the operation record to a specified OBS bucket for storage. With CTS, you can record operations associated with AS for later query, audit, and backtrack operations.
+-Scenarios
AS can work together with Cloud Trace Service (CTS) to record resource operations. CTS can record operations performed on the management console, operations performed by calling APIs, and operations triggered within the cloud system.
+If you have enabled CTS, when a call is made to the AS API, the operation will be reported to CTS which will then deliver the operation record to a specified OBS bucket for storage. With CTS, you can record AS operation logs for later query, audit, and backtracking.
Obtaining AS Information in CTS
After you enable CTS in the application system, the system logs the API calling operations performed on AS resources. On the Cloud Trace Service console, you can view operation records for the last 7 days. To obtain more operation records, you can enable the Object Storage Service (OBS) and synchronize operation records to the OBS in real time.
+Obtaining AS Information in CTS
After you enable CTS, whenever an AS API is called, the operation is recorded in a log file. On the Cloud Trace Service console, you can view operation records for the last 7 days. For details, see Querying Real-Time Traces. To store operation records for a longer period, you can transfer them to Object Storage Service (OBS) buckets.
Table 1 lists the AS operations that can be recorded by CTS.Table 1 AS operations that can be recorded by CTS Operation
disableScalingGroup
Performing operations on an AS group
+scaling_group
+operateScalingGroup
+Creating an AS configuration
scaling_configuration
@@ -63,7 +70,7 @@deleteScalingConfiguration
Deleting AS configurations in batches
+Deleting AS configurations in a batch
scaling_configuration
executeScalingPolicy
Performing operations on an AS policy
+scaling_policy
+operateScalingPolicy
+Enabling AS policies in a batch
+scaling_policy
+batchEnableScalingPolicies
+Disabling AS policies in a batch
+scaling_policy
+batchDisableScalingPolicies
+Removing an instance
scaling_instance
@@ -133,6 +161,13 @@batchAddInstances
Performing operations on instances in batches
+scaling_instance
+batchOperateInstance
+Enabling instance protection in a batch
scaling_instance
@@ -147,6 +182,13 @@batchUnprotectInstances
Putting instances into standby in a batch
+scaling_instance
+batchEnterStandbyInstances
+Deleting a tag
scaling_tag
@@ -154,11 +196,18 @@deleteScalingTag
Creating or Updating a tag
+Adding a tag
scaling_tag
updateScalingTag
+createScalingTag
+Updating a tag
+scaling_tag
+updateScalingTag
-Viewing Audit Logs
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - Click Service List. Choose Management & Deployment > Cloud Trace Service.
- Click Trace List in the navigation pane on the left.
- You can use filters to query traces. The following filters are available:
- Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
If you select Resource ID for Search By, specify a resource ID.
-If you select Data for Trace Type, you can only filter traces by tracker.
- - Operator: Select one or more specific operators from the drop-down list.
- Trace Status: Select All trace statuses, Normal, Warning, or Incident.
- Time range: In the upper right corner, choose Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range.
- Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
- Click
to the left of the required trace to expand its details. - Locate the required trace and click View Trace in the Operation column. The trace details are displayed.
CTS Log Entries
Each log entry consists of a trace in JSON format. A log entry indicates an AS API request, including the requested operation, the operation date and time, operation parameters, and information about the user who sends the request. The user information is obtained from the Identity and Access Management (IAM) service.
-The following example shows CTS log entries for the CreateScalingPolicy action:-{ -"time": "2016-12-15 15:27:40 GMT+08:00", -"user": { -"name": "xxxx", -"id": "62ff83d2920e4d3d917e6fa5e31ddebe", -"domain": { -"name": "xxx", -"id": "30274282b09749adbe7d9cabeebcbe8b" -} -}, -"request": { -"scaling_policy_name": "as-policy-oonb", -"scaling_policy_action": { -"operation": "ADD", -"instance_number": 1 -}, -"cool_down_time": "", -"scheduled_policy": { -"launch_time": "2016-12-16T07:27Z" -}, -"scaling_policy_type": "SCHEDULED", -"scaling_group_id": "ec4051a7-6fbd-42d2-840f-2ad8cdabee34" -}, -"response": { -"scaling_policy_id": "6a38d488-664b-437a-ade2-dc45f96f7f4c" -}, -"code": 200, -"service_type": "AS", -"resource_type": "scaling_policy", -"resource_name": "as-policy-oonb", -"resource_id": "6a38d488-664b-437a-ade2-dc45f96f7f4c", -"source_ip": "10.190.205.233", -"trace_name": "createScalingPolicy", -"trace_rating": "normal", -"trace_type": "ConsoleAction", -"api_version": "1.0", -"record_time": "2016-12-15 15:27:40 GMT+08:00", -"trace_id": "f627062b-c297-11e6-a606-eb2c0f48bec5" -}-diff --git a/docs/as/umn/as_06_0104.html b/docs/as/umn/as_06_0104.html index d5c0ad21..79795564 100644 --- a/docs/as/umn/as_06_0104.html +++ b/docs/as/umn/as_06_0104.html @@ -1,7 +1,7 @@Adding Tags to AS Groups and Instances
-Scenarios
If you have many resources of the same type, you can use a tag to manage resources flexibly. You can identify specified resources quickly using the tags allocated to them.
+Scenarios
If you have many resources of the same type, you can use tags to manage resources flexibly. You can identify specified resources quickly using the tags allocated to them.
Using a tag, you can assign custom data to each AS group. You can organize and manage AS groups, for example, classify AS group resources by usage, owner, or environment.
Each tag contains a key and a value. You can specify the key and value for each tag. A key can be a category associated with certain values, such as usage, owner, and environment.
For example, if you want to distinguish between the test environment and production environment, you can allocate a tag with the key environment to each AS group. For the test environment, the key value is test and for the production environment, the key value is production. You are advised to use one or more groups of consistent tags to manage your AS group resources.
@@ -21,14 +21,14 @@Tag Key
- The value cannot be empty.
- An AS group has a unique key.
- A key can contain a maximum of 36 characters, including only digits, letters, hyphens (-), and underscores (_).
- The value cannot be empty.
- The key must be unique to the AS group.
- A key can contain a maximum of 36 characters, including only digits, letters, hyphens (-), and underscores (_).
Organization
Tag Value
- The value can be an empty character string.
- A key can have only one value.
- A tag value can contain a maximum of 43 characters, including only digits, letters, hyphens (-), and underscores (_).
- The value is optional.
- A key can have only one value.
- A tag value can contain a maximum of 43 characters, including only digits, letters, hyphens (-), and underscores (_).
Apache
- Click OK.
diff --git a/docs/as/umn/as_06_0105.html b/docs/as/umn/as_06_0105.html index 6735dfd5..24edea56 100644 --- a/docs/as/umn/as_06_0105.html +++ b/docs/as/umn/as_06_0105.html @@ -69,7 +69,7 @@Modifying or Deleting Tags of an AS Group
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.
- Click the AS group name. On the Overview page, click the Tags tab.
- Locate the row that contains the tag and click Edit or Delete in the Operation column.
After clicking Edit, configure required parameters. For details, see Table 1.
+- Click in the upper left corner to select a region and a project.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.
- Click the AS group name. On the Overview page, click the Tags tab.
- Locate the row that contains the tag and click Edit or Delete in the Operation column.
After clicking Edit, configure required parameters. For details, see Table 1.
After you click Delete, the added tag will be deleted.
- Click
Inband Incoming Rate
Number of incoming bytes per second on an ECS in an AS group
-Formula: Total inband incoming rates of all ECS instances in an AS group/Number of ECS instances in the AS group
+Formula: Total inband incoming rate of all ECS instances in an AS group/Number of ECS instances in the AS group
Unit: Byte/s
≥0 Byte/s
@@ -84,7 +84,7 @@Inband Outgoing Rate
Number of outgoing bytes per second on an ECS in an AS group
-Formula: Total inband outgoing rates of all ECS instances in an AS group/Number of ECS instances in the AS group
+Formula: Total inband outgoing rate of all ECS instances in an AS group/Number of ECS instances in the AS group
Unit: Byte/s
≥0 Byte/s
@@ -99,7 +99,7 @@Disks Read Rate
Number of bytes read from an AS group per second
-Formula: Total disks read rates of all ECS instances in an AS group/Number of ECS instances in the AS group
+Formula: Total disk read rate of all ECS instances in an AS group/Number of ECS instances in the AS group
Unit: Byte/s
≥0 Byte/s
@@ -114,7 +114,7 @@Disks Write Rate
Number of bytes written to an AS group per second
-Formula: Total disks write rates of all ECS instances in an AS group/Number of ECS instances in the AS group
+Formula: Total disk write rate of all ECS instances in an AS group/Number of ECS instances in the AS group
Unit: Byte/s
≥0 Byte/s
@@ -128,8 +128,8 @@Disks Read Requests
Number of read requests per second sent to an ECS disk in an AS group
-Formula: Total disks read rates of all ECS instances in an AS group/Number of ECS instances in the AS group
+Number of disk read requests sent to an AS group per second
+Formula: Total number of disk read requests sent to all ECS instances in an AS group/Number of ECS instances in the AS group
Unit: Request/s
≥0 request/s
@@ -143,8 +143,8 @@Disks Write Requests
Number of write requests per second sent to an ECS disk in an AS group
-Formula: Total disks write rates of all ECS instances in an AS group/Number of ECS instances in the AS group
+Number of disk write requests sent to an AS group per second
+Formula: Total number of disk write requests sent to all ECS instances in an AS group/Number of ECS instances in the AS group
Unit: Request/s
≥0 request/s
diff --git a/docs/as/umn/as_06_0108.html b/docs/as/umn/as_06_0108.html new file mode 100644 index 00000000..20076e91 --- /dev/null +++ b/docs/as/umn/as_06_0108.html @@ -0,0 +1,25 @@ + + +Querying Real-Time Traces
+++Scenarios
After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records generated in the last seven days.
+This section describes how to query and export operation records of the last seven days on the CTS console.
+ ++Viewing Real-Time Traces in the Trace List
- Log in to the management console.
- Click
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed. - Choose Trace List in the navigation pane on the left.
- Set filters to search for your desired traces, as shown in Figure 1. The following filters are available:
++
- Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
- If you select Resource ID for Search By, specify a resource ID.
- If you select Trace name for Search By, specify a trace name.
- If you select Resource name for Search By, specify a resource name.
- Operator: Select a user.
- Trace Status: Select All trace statuses, Normal, Warning, or Incident.
- Time range: You can query traces generated during any time range in the last seven days.
- Click Export to export all traces in the query result as a CSV file. The file can contain up to 5000 records.
- Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
- Click Query.
- On the Trace List page, you can also export and refresh the trace list.
- Click Export to export all traces in the query result as a CSV file. The file can contain up to 5000 records.
- Click
to view the latest information about traces.
- Click
on the left of a trace to expand its details.
+
+ +
- Click View Trace in the Operation column. The trace details are displayed.
+
- For details about key fields in the trace structure, see section "Trace References" > "Trace Structure" and section "Trace References" > "Example Traces" in the CTS User Guide.
++ diff --git a/docs/as/umn/as_06_0206.html b/docs/as/umn/as_06_0206.html index 753826f4..1eb80323 100644 --- a/docs/as/umn/as_06_0206.html +++ b/docs/as/umn/as_06_0206.html @@ -3,7 +3,7 @@++Parent topic: AS Group and Instance Monitoring+Can I Use an ECS Instance ID to Learn What AS Group the Instance Is In?
No.
To obtain details about an AS group and the instances in the group, perform the following operations:
-- Log in to the management console. Choose Compute > Auto Scaling > Instance Scaling.
- On the AS Groups tab page, click the name of the target AS group.
- Click the Instances tab to view the instances in the AS group.
- Log in to the management console. Choose Compute > Auto Scaling > Instance Scaling.
- On the AS Groups page, click the name of the target AS group.
- Click the Instances tab to view the instances in the AS group.
diff --git a/docs/as/umn/as_07_0102.html b/docs/as/umn/as_07_0102.html index a9acbd74..58320293 100644 --- a/docs/as/umn/as_07_0102.html +++ b/docs/as/umn/as_07_0102.html @@ -1,18 +1,18 @@Creating a User and Granting AS Permissions
-Scenarios
IAM can help you implement fine-grained permissions control over your AS resources. With IAM, you can
-- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing AS resources.
- Grant only the permissions required for users to perform a specific task.
- Use IAM to entrust an account or cloud service to perform efficient O&M on your AS resources.
-Scenarios
IAM can help you implement fine-grained permissions control over your AS resources. With IAM, you can:
+- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing AS resources.
- Grant users only the permissions required to perform a given task based on their job responsibilities.
- Use IAM to entrust an account or cloud service to perform efficient O&M on your AS resources.
If your account does not require individual IAM users, skip this section.
-This section describes the procedure for granting permissions (see Figure 1).
+This section describes the procedure for granting permissions. Figure 1 shows the process flow.
diff --git a/docs/as/umn/as_07_0103.html b/docs/as/umn/as_07_0103.html index 277a5b3c..48d2de7c 100644 --- a/docs/as/umn/as_07_0103.html +++ b/docs/as/umn/as_07_0103.html @@ -4,7 +4,7 @@Prerequisites
Learn about the permissions (see Permissions Management) supported by AS and choose policies or roles according to your requirements. For the permissions of other services, see Permission Description.
+Prerequisites
Before granting permissions to user groups, you should learn about the permissions (Permissions Management) supported by AS and choose policies or roles based on service requirements. To grant permissions for other services, learn about all permissions supported by IAM.
Process Flow
-- Create a user group and assign permissions to it.
Create a user group on the IAM console, and attach the AutoScaling ReadOnlyAccess policy to the group.
- - Create an IAM user and add it to the user group.
Create a user on the IAM console and add the user to the group created in 1.
- - Log in and verify permissions.
Log in to the AS console as the created user, and verify the user's permissions for AS.
-- Choose Service List > Auto Scaling. Then, click Create AS Group on the AS console. If a message appears indicating that you have insufficient permissions to perform the operation, the AutoScaling ReadOnlyAccess policy has already taken effect.
- Choose any other service in the Service List. If a message appears indicating that you have insufficient permissions to access the service, the AutoScaling ReadOnlyAccess policy has already taken effect.
- Create a user group and assign permissions to it.
Create a user group on the IAM console, and assign the ASReadOnlyAccess permissions to the group.
+ - Create an IAM user and add it to the user group.
Create a user on the IAM console and add the user to the group created in 1.
+ - Log in and verify permissions.
Log in to the AS console as the created user, and verify the user's permissions for AS.
+- Choose Service List > Auto Scaling. Then, click Create AS Group on the AS console. If a message appears indicating that you have insufficient permissions to perform the operation, the ASReadOnlyAccess policy is in effect.
- Choose another in the Service List. If a message appears indicating that you have insufficient permissions to access the service, the ASReadOnlyAccess policy is in effect.
Scenarios
Custom policies can be created to supplement the system-defined policies of AS. For the actions that can be added to custom policies, see "Permissions Policies and Supported Actions" in Auto Scaling API Reference.
You can create custom policies in either of the following ways:
- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Edit JSON policies from scratch or based on an existing policy.
For operation details, see Creating a Custom Policy. The following section contains examples of common AS custom policies.
+For operation details, see Creating a Custom Policy. The following section contains examples of common AS custom policies.
Example Custom Policies
- Example 1: Allowing users to remove instances from an AS group and create AS configurations
{ "Version": "1.1", @@ -18,8 +18,8 @@ } ] }- - Example 2: Denying AS group deletion
A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
-The following method can be used if you need to assign permissions of the AutoScaling FullAccess policy to a user but you want to prevent the user from deleting AS groups. Create a custom policy for denying AS group deletion, and attach both policies to the group to which the user belongs. Then, the user can perform all operations on AS except deleting AS groups. The following is an example of a deny policy:
+ - Example 2: Denying AS group deletion
A policy with only "Deny" permissions must be used together with other policies. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
+Assume that you need to grant the permissions of the AutoScaling FullAccess policy to a user but want to prevent the user from deleting AS groups. You can create a custom policy for denying AS group deletion, and attach this policy together with the AutoScaling FullAccess policy to the user. As an explicit deny in any policy overrides any allows, the user can perform all operations on AS excepting deleting AS groups. The following is an example of a deny policy:
{ "Version": "1.1", "Statement": [ diff --git a/docs/as/umn/as_faq_0003.html b/docs/as/umn/as_faq_0003.html index 546d9f69..da3e815b 100644 --- a/docs/as/umn/as_faq_0003.html +++ b/docs/as/umn/as_faq_0003.html @@ -5,45 +5,45 @@If the application status or related data must be saved, you can store the information on separate servers.
-Table 1 Quotas Item
+-Table 1 Quotas Item
Description
+Description
Default
AS group
+AS group
Maximum number of AS groups per region per account
+Maximum number of AS groups per region per account
25
AS configuration
+AS configuration
Maximum number of AS configurations per region per account
+Maximum number of AS configurations per region per account
100
AS policy
+AS policy
Maximum number of AS policies per AS group
+Maximum number of AS policies per AS group
50
Instance
+Instance
Maximum number of instances per AS group
+Maximum number of instances per AS group
200
Bandwidth scaling policy
+Bandwidth scaling policy
Maximum number of bandwidth scaling policies per region per account
+Maximum number of bandwidth scaling policies per region per account
50
- AS requires authentication provided by Identity and Access Management (IAM).
The AS administrator account requires permissions of the tenant guest, ECS administrator, Cloud Eye administrator, and ELB administrator.
- If the Cloud Eye administrator is not available, you can only use an existing alarm to create an alarm policy. If the ELB administrator is not available, you can still use existing load balancers.
+- AS requires authentication provided by Identity and Access Management (IAM).
AutoScaling Administrator requires permissions of Tenant Guest, Server Administrator, CES Administrator, and ELB Administrator.
+ If the CES Administrator role is not available, you cannot create alarm rules, but you can use existing alarm rules to create alarm-based scaling policies. If the ELB Administrator role is not available, you can only use existing load balancers.
- AS resources must comply with quota requirements listed in Table 2.
-
Table 2 Quotas Item
+Table 2 Quotas Item
Description
+Description
Default
AS group
+AS group
Maximum number of AS groups per region per account
+Maximum number of AS groups per region per account
25
AS configuration
+AS configuration
Maximum number of AS configurations per region per account
+Maximum number of AS configurations per region per account
100
AS policy
+AS policy
Maximum number of AS policies per AS group
+Maximum number of AS policies per AS group
50
Instance
+Instance
Maximum number of instances per AS group
+Maximum number of instances per AS group
200
Bandwidth scaling policy
+Bandwidth scaling policy
Maximum number of bandwidth scaling policies per region per account
+Maximum number of bandwidth scaling policies per region per account
50
How Can I Automatically Deploy My Application on an Instance?
To enable automatic application deployment on instances automatically added to an AS group, create a private image with the application preinstalled and automatic startup settings preconfigured. Create an AS configuration with the private image, and then change the AS configuration used by the AS group to the one you created. Your application will be automatically deployed on instances that are automatically added to the AS group. The procedure is as follows:
-- Install the application on the instance you will use to create a private image, and configure the application to automatically start at boot.
- Create a private image using the instance. For details, see Image Management Service User Guide.
- Create an AS configuration. For details, Creating an AS Configuration from a New Specifications Template. During the creation, select the private image created in 2.
- Go to the page that shows the details about your AS group.
- Click Change Configuration to the right of Configuration Name. In the displayed dialog box, select the AS configuration created in 3 and click OK.
After new instances are added to the AS group in the next scaling action, you can check whether your application has been installed on the instances. If you encounter any problems, contact technical support.
+- Install the application on the instance you will use to create a private image, and configure the application to automatically start at boot.
- Create a private image using the instance. For details, see Image Management Service User Guide.
- Create an AS configuration. For details, Creating an AS Configuration from Scratch. During the creation, select the private image created in 2.
- Go to the page that shows the details about your AS group.
- Click Change Configuration to the right of Configuration Name. In the displayed dialog box, select the AS configuration created in 3 and click OK.
After new instances are added to the AS group in the next scaling action, you can check whether your application has been installed on the instances. If you encounter any problems, contact technical support.
diff --git a/docs/as/umn/as_faq_0014.html b/docs/as/umn/as_faq_0014.html index 7fd84b7e..e1cfe75b 100644 --- a/docs/as/umn/as_faq_0014.html +++ b/docs/as/umn/as_faq_0014.html @@ -14,17 +14,17 @@diff --git a/docs/as/umn/as_faq_0020.html b/docs/as/umn/as_faq_0020.html index 563a538f..09adb94e 100644 --- a/docs/as/umn/as_faq_0020.html +++ b/docs/as/umn/as_faq_0020.html @@ -1,7 +1,7 @@Handling method: Change the AS configuration for the AS group and then enable the AS group.
- Issue description: The subnet you select does not have enough private IP addresses.
Possible cause: Private IP addresses in the subnet used by the AS group have been used up.
Handling method: Modify the subnet information and enable the AS group.
-- Issue description: The ECS resources of this type in the selected AZ have been sold out.
Possible cause: ECSs of this type have been sold out or are not supported in the AZ selected for the AS group. ECSs of this type are the ECS flavor selected in the AS configuration.
+- Issue description: This type of ECSs has been sold out in the selected AZ.
Possible cause: This type of ECSs has been sold out or is not supported in the AZ selected for the AS group. The ECS flavor selected in the AS configuration is sold out.
Handling method: Change the AS configuration for the AS group and then enable the AS group. If there is no instance in the AS group, you can also change the AZ for the AS group and then enable the AS group.
- Issue description: The selected specifications and the disk do not match.
Possible cause: The ECS type in the AS configuration does not match the disk type, leading to the ECS creation failure.
Handling method: Change the AS configuration for the AS group and then enable the AS group.
- Issue description: The selected specifications and the image do not match.
Possible cause: The ECS type in the AS configuration does not match the image, leading to the ECS creation failure.
Handling method: Change the AS configuration for the AS group and then enable the AS group.
-- Issue description: Storage resources of this type have been sold out in the selected AZ.
Possible cause: Storage resources of this type have been sold out or are not supported in the AZ selected for the AS group. Storage resources of this type refer to the system and data disk types selected for the AS configuration.
+- Issue description: This type of storage resources has been sold out in the selected AZ.
Possible cause: Storage resources of this type have been sold out or are not supported in the AZ selected for the AS group. Storage resources of this type refer to the system and data disk types selected for the AS configuration.
Handling method: Change the AS configuration for the AS group and then enable the AS group. If there is no instance in the AS group, you can also change the AZ for the AS group and then enable the AS group.
- Issue description: A system error has occurred.
Possible cause: An error has occurred in the AS service, peripheral service, or network.
Handling method: Try again later or contact technical support.
-- Issue description: The specification defined in the AS configuration is unavailable.
Handling method: Change specifications by creating an AS configuration as prompted by the error message and use this AS configuration for the AS group. Then enable the AS group.
+- Issue description: The flavor defined in the AS configuration is unavailable.
Handling method: Change specifications by creating an AS configuration as prompted by the error message and use this AS configuration for the AS group. Then enable the AS group.
- Issue description: The selected AS configuration cannot be used by the AS group.
Handling method: Create an AS configuration as prompted by the error message and use this AS configuration for the AS group. Then enable the AS group.
When an Instance Is Removed from an AS Group and Deleted, Is the Application Data Saved?
-No. You must ensure that instances in the AS group do not store application status information or other important data, such as sessions, databases, and logs, or the data will be lost when AS automatically releases them. If you want to store your application status, you can store it on an independent server (such as an ECS) or database (such as an RDS database).
+No. You must ensure that instances in the AS group do not store application status information or other important data, such as sessions, databases, and logs, or the data will be lost when AS automatically releases them. If you want to store your application status, you can store it on an independent server (such as an ECS).
diff --git a/docs/as/umn/as_faq_0028.html b/docs/as/umn/as_faq_0028.html index 2a9d6f70..2c29790c 100644 --- a/docs/as/umn/as_faq_0028.html +++ b/docs/as/umn/as_faq_0028.html @@ -2,7 +2,7 @@How Do I Prevent Instances from Being Automatically Removed from an AS Group?
You can enable instance protection for in-service instances in an AS group. After the configuration, the protected in-service instances will not be removed during scale-in events. You can also modify the minimum number of instances for an AS group and use an instance removal policy to ensure that the AS group always has some in-service instances.
-Unhealthy instances are removed from an AS group and new instances are created automatically. Do not stop or delete instances that have been added to an AS group on the ECS console as they will be marked as unhealthy and automatically removed from the AS group. Even when an AS group is disabled, AS still checks the status of instances in the AS group, but does not remove unhealthy instances.
+Unhealthy instances are removed from an AS group and new instances are created automatically. Do not stop or delete instances that have been added to an AS group on the ECS console as they will be marked as unhealthy and automatically removed from the AS group. Even when an AS group is disabled, AS still checks the health of instances in the AS group, but does not remove unhealthy instances.
diff --git a/docs/as/umn/as_faq_0030.html b/docs/as/umn/as_faq_0030.html index c0fa5f37..3d20f297 100644 --- a/docs/as/umn/as_faq_0030.html +++ b/docs/as/umn/as_faq_0030.html @@ -1,7 +1,7 @@How Do I Handle Unhealthy Instances in an AS Group?
-Normally, you do not need to handle unhealthy instances because AS periodically checks the health status of instances in an AS group. When an AS group is enabled, unhealthy instances are removed and new instances are created to ensure that the expected number of instances are running in the AS group. When an AS group is disabled, AS keeps performing health checks on instances, but does not remove instances.
+Normally, you do not need to handle unhealthy instances because AS periodically checks the health status of instances in an AS group. When an AS group is enabled, unhealthy instances are removed and new instances are created to ensure that the expected number of instances are running in the AS group. When an AS group is disabled, AS still checks the health of instances, but does not remove instances.
It should be noted that if ELB health check is selected, ELB sends heartbeat messages to instances through an intranet. To ensure that the ELB health check can be performed properly, ensure that your instances can be accessed through that intranet. To check this, perform the following steps:
- In the Listener area, locate the row containing the target listener and click View in the Health Check column. A dialog box is displayed.
- Health Check Protocol: Ensure that the protocol has been configured and port has been enabled for the ECS instance to be checked.
- Check Path: If HTTP is used for the health check, ensure that the health check path for the instance is correct.
- Confirm that there is no software such as firewall on the instance blocking the source IP address used for performing the health check.
- Confirm that the rules of instance security groups and network ACL allow access from 100.125.0.0/16, and configure the protocol and port used for health check. Obtain the health check protocol and port from the dialog box displayed in step 1.
- If the default type of health check is used, service ports of the instances must be enabled.
- If the health check port is different from service ports of the instances, communication between the service ports and health check port must be enabled.
What Is a Cooldown Period and Why Is It Required?
-A cooldown period specifies how long any alarm-triggered scaling action will be disallowed after a previous scaling action is complete. This cooldown period does not work for scheduled or periodic scaling actions.
+A cooldown period 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.
Before an instance is put into use after it is added to the AS group, it takes 2 to 3 minutes to execute the configuration script to install and configure applications. The time varies depending on many factors, such as the instance specifications and startup scripts. If an instance is put into use without cooldown, the system will keep adding instances until the load decreases. As the new instances take over services, the system will detect that the load is too low and start removing instances from the AS group. A cooldown prevents the AS group from repeatedly triggering unnecessary scaling actions.
For example:
When a traffic peak occurs, an alarm policy is triggered and AS automatically adds an instance to the AS group to help handle the increased load. However, it takes time for the instance to start. After the instance is started, it takes time to receive requests from ELB. During this period, alarms may continue to be triggered and instances may continue to be added. If you set a cooldown time, after an instance is started, AS stops adding new instances in response to the alarms until the specified period of time (300 seconds by default) passes. That way the newly started instance has time to start processing application traffic. If an alarm is triggered again after the cooldown period elapses, AS starts another instance and the cooldown period starts up again.
diff --git a/docs/as/umn/as_faq_1101.html b/docs/as/umn/as_faq_1101.html index 1edcd30b..97edd74c 100644 --- a/docs/as/umn/as_faq_1101.html +++ b/docs/as/umn/as_faq_1101.html @@ -1,11 +1,7 @@ - -General
- --- +General
+- What Are Restrictions on Using AS?
diff --git a/docs/as/umn/as_faq_1102.html b/docs/as/umn/as_faq_1102.html index 918bc9bc..7b4571ff 100644 --- a/docs/as/umn/as_faq_1102.html +++ b/docs/as/umn/as_faq_1102.html @@ -1,11 +1,7 @@ - -AS Group
- --- +AS Group
+- What Can I Do If the AS Group Fails to Be Enabled?
diff --git a/docs/as/umn/as_faq_1103.html b/docs/as/umn/as_faq_1103.html index 5e1a17ce..f9fdc13e 100644 --- a/docs/as/umn/as_faq_1103.html +++ b/docs/as/umn/as_faq_1103.html @@ -1,11 +1,7 @@ - -AS Policy
- --- +AS Policy
+- How Many AS Policies Can I Enable?
diff --git a/docs/as/umn/as_pro_0002.html b/docs/as/umn/as_pro_0002.html index 5226174b..b9ef1b93 100644 --- a/docs/as/umn/as_pro_0002.html +++ b/docs/as/umn/as_pro_0002.html @@ -6,108 +6,101 @@
When trigger condition 2 or 4 is met, the system autonomously puts instances into the next status.
-Table 1 Instance statuses Status
+-Table 1 Instance statuses Status
Sub-status
+Action
Status Description
+Description
Trigger Condition
+Trigger Condition
Initial
None
+-
The instance has not been added to the AS group.
N/A
+-
Adding to AS group
+Adding
Add the instance.
When trigger condition 1 is met, AS adds the instance to expand the AS group capacity.
The instance status changes to Adding to AS group when any of the following conditions is met:- You manually increase the expected number of instances of the AS group.
- The system automatically expands the AS group capacity.
- You manually add instances to the AS group.
The instance status changes to Adding when any of the following conditions occurs:+- You manually increase the expected number of instances for the AS group.
- The system automatically expands the AS group capacity.
- You manually add the instance to the AS group.
Adding to AS group
+(Optional) Associate the instance with the load balancing listener.
(Optional) Associate the instance with a load balancing listener.
-When trigger condition 1 is met, AS associates the created instance with the load balancing listener.
-The instance status changes to Adding to AS group when any of the following conditions is met:+- You manually change the expected number of instances of the AS group.
- The system automatically expands the AS group capacity.
- You manually add instances to the AS group.
When trigger condition 1 is met, AS associates the instance with the load balancing listener.
Enabled
None
+-
The instance is added to the AS group and starts to process service traffic.
N/A
+-
Removing from AS group
+Removing
+(Optional) Disassociate the instance from the load balancing listener.
When trigger condition 3 is met, the AS group starts to reduce resources and disassociate the instance from the load balancing listener.
+When trigger condition 3 is met, AS disassociates the instance to be removed from the load balancing listener.
The instance status changes from Enabled to Removing from AS group when any of the following conditions is met:- You manually decrease the expected number of instances of the AS group.
- The system automatically reduces the AS group capacity.
- A health check shows that an enabled instance is unhealthy, and the system removes it from the AS group.
- You manually remove instances from the AS group.
The instance status changes from Enabled to Removing when any of the following conditions is met:+- You manually decrease the expected number of instances for the AS group.
- The system automatically reduces the AS group capacity.
- A health check shows that the instance is unhealthy after being enabled, and the system removes it from the AS group.
- You manually remove the instance from the AS group.
Removing from AS group
+Remove the instance.
Remove the instance.
-After the instance is unbound from the load balancing listener, it is removed from the AS group.
-The instance status changes from Enabled to Removing from AS group when any of the following conditions is met:+- You manually decrease the expected number of instances of the AS group.
- The system automatically reduces the AS group capacity.
- A health check shows that an enabled instance is unhealthy, and the system removes it from the AS group.
- You manually remove instances from the AS group.
After the instance is dissociated from the load balancing listener, it is removed from the AS group.
Removed
None
+-
The instance lifecycle in the AS group ends.
None
+-
When an ECS instance is added to an AS group manually or through a scaling action, it goes through the Adding to AS group, Enabled, and Removing from AS group statuses. Then it is finally removed from the AS group.
-If you have added a lifecycle hook to the AS group, the instance statuses change as shown in Figure 2. When a scale-out or scale-in event occurs in the AS group, the required instances are suspended by the lifecycle hook and remain in the wait status until the timeout period ends or you manually call back the instances. You can perform custom operations on the instances when they are in the wait status. For example, you can install or configure software on an instance before it is added to the AS group or download log files from an instance before it is removed. +After an ECS instance is added to an AS group manually or automatically, it goes through different statuses from Adding, Enabled to Removing. Then it is finally removed from the AS group.
+If you have added a lifecycle hook to the AS group, the instance lifecycle changes as shown in Figure 2. When a scale-out or scale-in event occurs in the AS group, the required instances are suspended by the lifecycle hook and remain in the wait status until the timeout period ends or you manually call back the instances. You can perform custom operations on the instances when they are in the wait status. For example, you can install or configure software on an instance before it is added to the AS group or download log files from an instance before it is removed.Under trigger condition 2, 4, 6, or 8, the system automatically changes the instance status.
-Table 2 Instance statuses Status
+-Table 2 Instance statuses Status
Sub-status
+Action
Status Description
+Description
Trigger Description
+Trigger Condition
Initial
None
+-
The instance has not been added to the AS group.
N/A
+-
Adding to AS group
@@ -116,17 +109,17 @@When trigger condition 1 is met, AS adds the instance to expand the AS group capacity.
The instance status will be changed to Adding to AS group when any of the following conditions is met:- You manually change the expected number of instances of the AS group.
- The system automatically reduces the AS group capacity.
- You manually add instances to the AS group.
The instance status changes to Adding when any of the following conditions occurs:- You manually increase the expected number of instances for the AS group.
- The system automatically reduces the AS group capacity.
- You manually add the instance to the AS group.
Wait (Adding to AS group)
None
+-
The lifecycle hook suspends the instance that is being added to the AS group and puts the instance into a wait status.
+The lifecycle hook suspends the instance being added to the AS group and puts the instance into a wait status.
The instance status is changed from Wait (Adding to AS group) to Adding to AS group when either of the following occurs:- The default callback action is performed.
- You manually perform the callback action.
The instance status changes from Wait (Adding to AS group) to Adding to AS group when either of the following conditions occurs:- The default callback action is performed.
- You manually perform the callback action.
When trigger condition 3 is met, AS associates the instance with the load balancing listener.
The instance status is changed from Wait (Adding to AS group) to Adding to AS group when either of the following occurs:- The default callback action is performed.
- You manually perform the callback action.
The instance status changes from Wait (Adding to AS group) to Adding to AS group when either of the following conditions occurs:- The default callback action is performed.
- You manually perform the callback action.
Enabled
None
+-
The instance is added to the AS group and starts to process service traffic.
The instance status changes from Enabled to Removing from AS group when any of the following occurs:- You manually change the expected number of instances of the AS group.
- The system automatically reduces the AS group capacity.
- A health check shows that an enabled instance is unhealthy, and the system removes it from the AS group.
- You manually remove instances from the AS group.
The instance status is changed from Enabled to Removing from AS group when any of the following conditions occurs:- You manually decrease the expected number of instances for the AS group.
- The system automatically reduces the AS group capacity.
- A health check shows that the instance is unhealthy after being enabled, and the system removes it from the AS group.
- You manually remove the instance from the AS group.
When trigger condition 5 is met, the AS group starts to reduce resources and disassociate the instance from the load balancing listener.
The instance status changes from Enabled to Removing from AS group when any of the following occurs:- You manually change the expected number of instances of the AS group.
- The system automatically reduces the AS group capacity.
- A health check shows that an enabled instance is unhealthy, and the system removes it from the AS group.
- You manually remove instances from the AS group.
- You manually decrease the expected number of instances for the AS group.
- The system automatically reduces the AS group capacity.
- A health check shows that the instance is unhealthy after being enabled, and the system removes it from the AS group.
- You manually remove the instance from the AS group.
Wait (Removing from AS group)
+Wait (Removing from AS group)
None
+-
The lifecycle hook suspends the instance that is being removed from the AS group and puts the instance into a wait status.
The instance status is changed from Wait (Removing from AS group) to Removing from AS group when either of the following occurs:- The default callback action is performed.
- You manually perform the callback action.
The instance status is changed from Wait (Removing from AS group) to Removing from AS group when either of the following conditions occurs:- The default callback action is performed.
- You manually perform the callback action.
When trigger condition 7 is met, AS removes the instance from the AS group.
The instance status changes from Wait (Removing from AS group) to Removing from AS group when either of the following occurs:- The default callback action is performed.
- You manually perform the callback action.
The instance status is changed from Wait (Removing from AS group) to Removing from AS group when either of the following conditions occurs:- The default callback action is performed.
- You manually perform the callback action.
Removed
None
+-
The instance lifecycle in the AS group ends.
None
+-
Instances are added to an AS group manually or through a scaling action. Then, they go through the Adding to AS group, Wait (Adding to AS group), Adding to AS group, Enabled, Removing from AS group, Wait (Removing from the AS group), and Removing from AS group and are finally removed from the AS group.
+When the instance is added to the AS group manually or through a scaling action, it goes through statuses from Adding to AS group, Wait (Adding to AS group), Adding to AS group, Enabled, Removing from AS group, Wait (Removing from the AS group), to Removing from AS group and is finally removed from the AS group.
diff --git a/docs/as/umn/as_pro_0003.html b/docs/as/umn/as_pro_0003.html index b8c9b8c0..5a24926f 100644 --- a/docs/as/umn/as_pro_0003.html +++ b/docs/as/umn/as_pro_0003.html @@ -1,8 +1,9 @@Constraints
-AS has the following constraints:
-- Only applications that are stateless and can be horizontally scaled can run on instances in an AS group.
- A stateless process or application can be understood in isolation. There is no stored knowledge of or reference to past transactions. Each transaction is made as if from scratch for the first time.
ECS instances where stateless applications are running do not store data that needs to be persisted locally.
++Function Restrictions
AS has the following restrictions:
+- Only applications that are stateless and horizontally scalable can run on instances in an AS group.
- A stateless process or application can be understood in isolation. There is no stored knowledge of or reference to past transactions. Each transaction is made as if from scratch for the first time.
ECS instances where stateless applications are running do not store data that needs to be persisted locally.
Think of stateless transactions as a vending machine: a single request and a response.
- Stateful applications and processes, however, are those that can be returned to again and again. They are performed in the context of previous transactions and the current transaction may be affected by what happened during previous transactions.
ECS instances where stateful applications are running store data that needs to be persisted locally.
Stateful transactions are performed repeatedly, such as online banking or e-mail, which are performed in the context of previous transactions.
@@ -11,54 +12,56 @@ - AS can release ECS instances in an AS group automatically, so the instances cannot be used to save application status information (such as session statuses) or related data (such as database data and logs). If the application status or related data must be saved, you can store the information on separate servers.
- AS does not support capacity expansion or deduction of instance vCPUs and memory.
- AS requires authentication provided by Identity and Access Management (IAM).
AutoScaling Administrator requires permissions of Tenant Guest, Server Administrator, CES Administrator, and ELB Administrator.
- If the Cloud Eye administrator is not available, you can only use an existing alarm to create an alarm policy. If the ELB administrator is not available, you can still use existing load balancers.
- AS resources must comply with quota requirements listed in Table 1.
-diff --git a/docs/as/umn/as_pro_0007.html b/docs/as/umn/as_pro_0007.html index b7420b4d..458f9bab 100644 --- a/docs/as/umn/as_pro_0007.html +++ b/docs/as/umn/as_pro_0007.html @@ -5,10 +5,10 @@
Table 1 Quotas Item
+ +Quotas
AS resources must comply with quota requirements listed in Table 1. ++- +Table 1 Quotas Item
Description
+Description
Default
+Default
AS group
+AS group
Maximum number of AS groups per region per account
+Maximum number of AS groups per region per account
25
+25
AS configuration
+AS configuration
Maximum number of AS configurations per region per account
+Maximum number of AS configurations per region per account
100
+100
AS policy
+AS policy
Maximum number of AS policies per AS group
+Maximum number of AS policies per AS group
50
+50
Instance
+Instance
Maximum number of instances per AS group
+Maximum number of instances per AS group
200
+200
Bandwidth scaling policy
+Bandwidth scaling policy
Maximum number of bandwidth scaling policies per region per account
+Maximum number of bandwidth scaling policies per region per account
50
+50
diff --git a/docs/as/umn/as_pro_0006.html b/docs/as/umn/as_pro_0006.html index 93c32178..fe71d558 100644 --- a/docs/as/umn/as_pro_0006.html +++ b/docs/as/umn/as_pro_0006.html @@ -27,7 +27,7 @@Cloud Eye
If an alarm-triggered policy is configured, AS triggers scaling actions when an alarm condition specified in Cloud Eye is met.
+If an alarm-triggered policy is configured, AS triggers scaling actions when an alarm triggering condition specified in Cloud Eye is met.
AS scales resources based on ECS instance status monitored by Cloud Eye.
Cloud Trace Service (CTS)
With CTS, you can record AS operation logs for viewing, auditing, and backtracking.
+With CTS, you can record AS operation logs for view, audit, and backtracking.
Log audit
Relational Database Service (RDS)
-The prerequisites for directly accessing an RDS DB instance from a scaled instance are as follows:
-- The scaled instance and the destination RDS DB instance must be in the same VPC.
- The scaled instance must be allowed by the security group to access RDS DB instances.
The scaled instances can access RDS DB instances.
-Connecting to an MySQL DB Instance Through a Private Network
-With IAM, you can create IAM users and assign permissions to the users to control their access to specific resources. For example, you can assign permissions to allow some software developers to use AS resources but disallow them to delete or perform any high-risk operations on the resources.
If your account does not need individual IAM users for permissions management, skip this section.
IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.
-AS Permissions
By default, new IAM users do not have any permissions assigned. You need to add them to one or more groups and attach policies or roles to these groups so that these users can inherit permissions from the groups and perform specified operations on cloud services.
+AS Permissions
By default, new IAM users do not have any permissions assigned. You need to add them to one or more groups and attach policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.
When you grant AS permissions to a user group, set Scope to Region-specific projects and then select projects for the permissions to take effect. If you select All projects, the permissions will take effect for the user group in all region-specific projects. When accessing AS, the users need to switch to a region where they have been authorized to use this service.
You can grant users permissions by using roles and policies.
-- Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
- Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant AS users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs. For the API actions supported by AS, see "Permissions Policies and Supported Actions" in Auto Scaling API Reference.
Table 1 lists all the system policies supported by AS.
+- Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you also also need to attach any existing role dependencies. However, roles are not an ideal choice for fine-grained authorization and secure access control.
- Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant AS users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs. For the API actions supported by AS, see "Permissions Policies and Supported Actions" in Auto Scaling API Reference.
Table 1 lists all the system policies supported by AS.
-Table 1 System-defined permissions supported by AS Policy Name
AutoScaling FullAccess
All operation permissions on all AS resources
+Full permissions for all AS resources
System-defined policy
AutoScaling ReadOnlyAccess
Read-only permissions on all AS resources
+Read-only permissions for all AS resources
System-defined policy
AutoScaling Administrator
All operation permissions on all AS resources
+Full permissions for all AS resources
System role
- If you require high availability, buy servers in different AZs.
- If you require low network latency, buy servers in the same AZ.
To enhance application availability, the system evenly distributes your instances between AZs if multiple AZs have been selected.
-N/A
+-
Name
Specifies the name of the AS group to be created.
-The name can contain up to 64 characters. It can include letters, digits, underscores (_), and hyphens (-).
+The name contains 1 to 64 characters and consists of only letters, digits, underscores (_), and hyphens (-).
N/A
+-
Max. Instances
@@ -65,59 +65,59 @@Provides a network for your ECS instances.
All ECS instances in the AS group are deployed in this VPC.
N/A
+-
Subnet
You can select up to five subnets. The AS group automatically binds all NICs to the created ECSs. The first subnet is used by the primary NIC of an ECS instance by default, and other subnets are used by extension NICs of the instance.
N/A
+-
Load Balancing
This parameter is optional. A load balancer automatically distributes traffic across all instances in an AS group to balance their service load. It improves the fault tolerance of your applications and expands application service capabilities.
-NOTE:- Up to three load balancers can be added to an AS group.
- After multiple load balancers are added to an AS group, multiple services can be concurrently listened to, thereby improving scalability. If ELB health check is selected for Health Check Method, when any one of the listeners detects that an instance becomes unhealthy, AS will replace the faulty instance with a functional one.
NOTE:- Up to three load balancers can be added to an AS group.
- After multiple load balancers are added to an AS group, multiple services can be concurrently listened to, thereby improving service scalability. If ELB health check is selected for Health Check Method, when any one of the listeners detects that an instance becomes unhealthy, AS will replace the faulty instance with a functional one.
If you select Classic load balancer, configure the following parameters:
- Load Balancer
- Listener
If you select Enhanced load balancer, configure the following parameters:- Load Balancer
- Backend ECS Group
If you select Enhanced load balancer, configure the following parameters:- Load Balancer
- Backend ECS Group
- Backend Port: specifies the port on which a backend ECS listens for traffic.
- Weight: determines the portion of requests a backend ECS processes compared to other backend ECSs added to the same listener.
For more information about load balancing, see Elastic Load Balancing User Guide.
N/A
+-
Instance Removal Policy
Specifies the priority for removing instances from an AS group. If specified conditions are met, scaling actions are triggered to remove instances. AS supports the following instance removal policies:
+Controls which instances are first to be removed during scale in. If specified conditions are met, scaling actions are triggered to remove instances by following the removal policy you choose. There are four instance removal policies for you to choose from:
- Oldest instance created from oldest AS configuration: The oldest instance created from the oldest configuration is removed from the AS group first.
- Newest instance created from oldest AS configuration: The newest instance created from the oldest configuration is removed from the AS group first.
- Oldest instance: The oldest instance is removed from the AS group first.
- Newest instance: The newest instance is removed from the AS group first.
NOTE:- Removing instances will preferentially ensure that the remaining instances are load balanced in AZs.
- Manually added ECS instances are the last to be removed. If AS does remove a manually added instance, it only removes the instance from the AS group. It does not delete the instance. If multiple manually added instances must be removed, AS preferentially removes the earliest-added instance first.
N/A
+-
EIP
If EIP has been selected in an AS configuration for an AS group, an EIP is automatically bound to the ECS instance added to the AS group. If you select Release, the EIP bound to an instance is released when the instance is removed from the AS group. Otherwise, the system unbinds the EIP from the instance, but does not release it when the instance is removed from the AS group.
+If EIP has been selected in the AS configuration for an AS group, an EIP is automatically bound to the ECS instance added to the AS group. If you select Release, the EIP bound to an instance is released when the instance is removed from the AS group. Otherwise, the system unbinds the EIP from the instance, but does not release it when the instance is removed from the AS group.
N/A
+-
Health Check Method
When a health check detects a faulty ECS, AS removes the faulty ECS from the AS group and adds a new one. The health check is implemented using any of the following methods:
-- ECS health check: checks ECS instance running status. If an instance is stopped or deleted, it is considered unhealthy. This method is selected by default. Using this method, the AS group periodically determines the running status of each ECS instance based on the health check result. If the health check results show that an instance is unhealthy, AS removes the instance from the AS group.
- ELB health check: determines ECS running status using a load balancing listener. This health check method is available only when the AS group uses a load balancing listener. When a load balancing listener detects that an ECS is faulty, AS removes the ECS from the AS group.
If an ECS instance fails a health check, AS replaces it with a new one. There are two health check methods:
+- ECS health check: checks the ECS instance running status. If an instance is stopped or deleted, it is considered unhealthy. This method is selected by default. Using this method, the AS group periodically checks the running status of each ECS instance. If an instance is unhealthy, AS removes the instance from the AS group.
- ELB health check: determines ECS running status using a load balancing listener. This health check method is only available if a load balancer is configured for the AS group. An instance is considered to be healthy only when all associated listeners detect it as healthy. If a listener detects that the instance is unhealthy, AS removes the instance from the AS group.
N/A
+-
Health Check Interval
Specifies the health check period for an AS group. You can set a proper health check interval, such as 10 seconds, 1 minute, 5 minutes, 15 minutes, 1 hour, and 3 hours based on the site requirements.
+Specifies the length of time between health checks. You can set a health check interval, such as 10 seconds, 1 minute, 5 minutes, 15 minutes, 1 hour, and 3 hours based on service requirements.
5 minutes
NOTE:-- Value default indicates the default enterprise project. Resources that are not allocated to any enterprise projects under your account are displayed in the default enterprise project.
- Enterprise project is an upgraded version of IAM. It allocates and manages resources of different projects.
N/A
+-
Advanced Settings
@@ -136,15 +136,15 @@Configure notifications and tags.
You can select Do not configure or Configure now.
N/A
+-
Notification Mode
This parameter is optional. If this parameter is selected, the system will notify you of scaling action results by email after a scaling action is complete.
-The mailbox is specified when you register yourself on the cloud.
+The notifications will be sent to the email address you specified when you registered yourself on the cloud.
N/A
+-
Tag
@@ -155,14 +155,14 @@- Value
- The value is optional.
- A key can have only one value.
- The value can include up to 43 characters. Only digits, letters, underscores (_), and hyphens (-) are allowed.
N/A
+-
- Click Next.
- On the displayed page, you can use an existing AS configuration or create an AS configuration. For details, see Creating an AS Configuration from an Existing ECS Instance and Creating an AS Configuration from a New Specifications Template.
- Click Next.
- (Optional) Add an AS policy to an AS group. +
- Click Next.
- On the displayed page, you can use an existing AS configuration or create an AS configuration. For details, see Creating an AS Configuration from an Existing ECS and Creating an AS Configuration from Scratch.
- Click Next.
- (Optional) Add an AS policy to an AS group.
On the displayed page, click Add AS Policy.
Configure the required parameters, such as the Policy Type, Scaling Action, and Cooldown Period. For details, see Dynamic Scaling and Scheduled Scaling.diff --git a/docs/as/umn/en-us_image_0000001696678850.png b/docs/as/umn/en-us_image_0000001696678850.png new file mode 100644 index 00000000..6b11888b Binary files /dev/null and b/docs/as/umn/en-us_image_0000001696678850.png differ diff --git a/docs/as/umn/en-us_image_0000001696838310.png b/docs/as/umn/en-us_image_0000001696838310.png new file mode 100644 index 00000000..582b1618 Binary files /dev/null and b/docs/as/umn/en-us_image_0000001696838310.png differ diff --git a/docs/as/umn/en-us_image_0000001696838318.png b/docs/as/umn/en-us_image_0000001696838318.png new file mode 100644 index 00000000..e4fcbfa9 Binary files /dev/null and b/docs/as/umn/en-us_image_0000001696838318.png differ diff --git a/docs/as/umn/en-us_image_0000001744598325.png b/docs/as/umn/en-us_image_0000001744598325.png new file mode 100644 index 00000000..3e15dbf9 Binary files /dev/null and b/docs/as/umn/en-us_image_0000001744598325.png differ diff --git a/docs/as/umn/en-us_image_0108911462.jpg b/docs/as/umn/en-us_image_0000001744678489.jpg similarity index 73% rename from docs/as/umn/en-us_image_0108911462.jpg rename to docs/as/umn/en-us_image_0000001744678489.jpg index f6731989..fac6892b 100644 Binary files a/docs/as/umn/en-us_image_0108911462.jpg and b/docs/as/umn/en-us_image_0000001744678489.jpg differ diff --git a/docs/as/umn/en-us_image_0000001758618249.png b/docs/as/umn/en-us_image_0000001758618249.png new file mode 100644 index 00000000..0d21733f Binary files /dev/null and b/docs/as/umn/en-us_image_0000001758618249.png differ diff --git a/docs/as/umn/en-us_image_0000001763445960.png b/docs/as/umn/en-us_image_0000001763445960.png new file mode 100644 index 00000000..ae028b90 Binary files /dev/null and b/docs/as/umn/en-us_image_0000001763445960.png differ diff --git a/docs/as/umn/en-us_image_0000002040045537.png b/docs/as/umn/en-us_image_0000002040045537.png new file mode 100644 index 00000000..c1439188 Binary files /dev/null and b/docs/as/umn/en-us_image_0000002040045537.png differ diff --git a/docs/as/umn/en-us_image_0000002041487301.png b/docs/as/umn/en-us_image_0000002041487301.png new file mode 100644 index 00000000..c1439188 Binary files /dev/null and b/docs/as/umn/en-us_image_0000002041487301.png differ diff --git a/docs/as/umn/en-us_image_0142360107.png b/docs/as/umn/en-us_image_0142360107.png deleted file mode 100644 index 1909444d..00000000 Binary files a/docs/as/umn/en-us_image_0142360107.png and /dev/null differ diff --git a/docs/as/umn/en-us_image_0200326047.png b/docs/as/umn/en-us_image_0200326047.png index 203ffbdb..11fec6d8 100644 Binary files a/docs/as/umn/en-us_image_0200326047.png and b/docs/as/umn/en-us_image_0200326047.png differ diff --git a/docs/as/umn/en-us_image_0200327117.png b/docs/as/umn/en-us_image_0200327117.png deleted file mode 100644 index 23754194..00000000 Binary files a/docs/as/umn/en-us_image_0200327117.png and /dev/null differ diff --git a/docs/as/umn/en-us_image_0282034671.png b/docs/as/umn/en-us_image_0282034671.png index f057484f..bcc83586 100644 Binary files a/docs/as/umn/en-us_image_0282034671.png and b/docs/as/umn/en-us_image_0282034671.png differ diff --git a/docs/as/umn/en-us_image_0282829283.png b/docs/as/umn/en-us_image_0282829283.png index 2e6cafcc..88bd5442 100644 Binary files a/docs/as/umn/en-us_image_0282829283.png and b/docs/as/umn/en-us_image_0282829283.png differ diff --git a/docs/as/umn/en-us_topic_0042018362.html b/docs/as/umn/en-us_topic_0042018362.html index 7bc77ca0..fe3a3ecb 100644 --- a/docs/as/umn/en-us_topic_0042018362.html +++ b/docs/as/umn/en-us_topic_0042018362.html @@ -4,8 +4,8 @@ - If a scaling action is triggered by an AS policy, the cooldown period is whatever configured for that AS policy.
- If a scaling action is triggered by manually changing the expected number of instances or by other actions, the cooldown period is whatever configured for the AS group.
-An AS configuration defines the specifications of the ECS instances to be added to an AS group. The specifications include the ECS image and system disk size.
-Scenarios
- When you create an AS group, create a new AS configuration or use an existing AS configuration.
- Create the required AS configuration on the Instance Scaling page.
- Change the AS configuration on the AS group details page.
diff --git a/docs/as/umn/en-us_topic_0042018368.html b/docs/as/umn/en-us_topic_0042018368.html index c39a573e..b0427983 100644 --- a/docs/as/umn/en-us_topic_0042018368.html +++ b/docs/as/umn/en-us_topic_0042018368.html @@ -9,7 +9,7 @@Methods
- Create an AS configuration from an existing ECS instance.
If you create an AS configuration from an existing ECS instance, the vCPU, memory, image, disk, and ECS type are the same as those of the selected instance by default. For details, see Creating an AS Configuration from an Existing ECS Instance.
- - Create an AS configuration from a new specifications template.
If you have special requirements on the ECSs for resource expansion, use a new specifications template to create the AS configuration. For details, see Creating an AS Configuration from a New Specifications Template.
+Methods
- Create an AS configuration from an existing ECS instance.
If you create an AS configuration from an existing ECS instance, the vCPU, memory, image, disk, and ECS type are the same as those of the selected instance by default. For details, see Creating an AS Configuration from an Existing ECS.
+ - Create an AS configuration from a new specifications template.
If you have special requirements on the ECSs for resource expansion, use a new specifications template to create the AS configuration. For details, see Creating an AS Configuration from Scratch.
- Create an AS configuration from an existing ECS instance.
- If the ECS type specified in the AS configuration is not available in any of the AZs used by the AS group, the following situations will occur:
- If the AS group is disabled, it cannot be enabled again later.
- If the AS group is enabled, its status will become abnormal when instances are added to it.
- If the ECS type specified in the AS configuration is only available in certain AZs used by the AS group, the ECS instances added by a scaling action are only deployed in the AZs where that ECS type is available. As a result, the instances in the AS group may not be evenly distributed.
Procedure
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Click Create AS Group.
- Set parameters, such as Name, Max. Instances, Min. Instances, and Expected Instances. Table 1 describes the key parameters to be configured.
+
Procedure
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.
- Click Create AS Group.
- Set parameters, such as Name, Max. Instances, Min. Instances, and Expected Instances. Table 1 describes the key parameters to be configured.
-
Table 1 AS group parameters Parameter
Description
@@ -23,7 +23,7 @@A region is where the AS group is deployed.
Resources in different regions cannot communicate with each other over internal networks. For lower network latency and faster access to your resources, select the region nearest to your target users.
N/A
+-
AZ
@@ -32,15 +32,15 @@- If you require high availability, buy servers in different AZs.
- If you require low network latency, buy servers in the same AZ.
To enhance application availability, the system evenly distributes your instances between AZs if multiple AZs have been selected.
N/A
+-
Name
Specifies the name of the AS group to be created.
-The name can contain up to 64 characters. It can include letters, digits, underscores (_), and hyphens (-).
+The name contains 1 to 64 characters and consists of only letters, digits, underscores (_), and hyphens (-).
N/A
+-
Max. Instances
@@ -54,6 +54,7 @@Specifies the expected number of ECS instances in an AS group.
After an AS group is created, you can change this value, which will trigger a scaling action.
+The number of expected instances cannot be smaller than the minimum number of instances or greater than the maximum number of instances.
0
Provides a network for your ECS instances.
All ECS instances in the AS group are deployed in this VPC.
N/A
+-
Subnet
You can select up to five subnets. The AS group automatically binds all NICs to the created ECS instances. The first subnet is used by the primary NIC of an ECS instance by default, and other subnets are used by extension NICs of the instance.
+Automatically-assigned IPv6 address: This parameter is available only if an AZ supporting IPv6 addresses is selected and IPv6 is enabled in the VPC subnet. For details about how to enable IPv6 on a subnet, see IPv4 and IPv6 Dual-Stack Network in the Virtual Private Cloud User Guide. By default, the system assigns IPv4 addresses. If Automatically-assigned IPv6 address is selected, the system assigns IPv6 addresses. In a VPC, an ECS uses an IPv6 address to access the dual-stack Intranet. To access the Internet, you must enable the IPv6 Bandwidth and select a shared bandwidth. Then, the ECS can use the IPv6 address to access the Internet.
N/A
+-
Load Balancing
@@ -85,21 +87,21 @@This parameter is optional. A load balancer automatically distributes traffic across all instances in an AS group to balance their service load. It improves the fault tolerance of your applications and expands application service capabilities.
NOTE:-- Up to three load balancers can be added to an AS group.
- After multiple load balancers are added to an AS group, multiple services can be concurrently listened to, thereby improving service scalability. If ELB health check is selected for Health Check Method, when any one of the listeners detects that an instance becomes unhealthy, AS will replace it with a new one.
If you select Classic load balancer, configure the following parameters:
-- Load Balancer
- Listener
If you select Enhanced load balancer, configure the following parameters:- Load Balancer
- Backend ECS Group
- Backend Port: specifies the port on which a backend ECS listens for traffic.
- Weight: determines the portion of requests a backend ECS processes compared to other backend ECSs added to the same listener.
For more information about load balancing, see Elastic Load Balancing User Guide.
+If you select Classic load balancer, configure the following parameters:
+- Load Balancer
- Listener
If you select Enhanced load balancer, configure the following parameters:- Load Balancer
- Backend ECS Group
- Backend Port: specifies the port on which a backend ECS listens for traffic.
- Weight: determines the portion of requests a backend ECS processes compared to other backend ECSs added to the same listener.
For more information about load balancing, see Elastic Load Balancing User Guide.
N/A
+-
Instance Removal Policy
Controls which instances are first to be removed during scale in. If specified conditions are met, scaling actions are triggered to remove instances. You can choose from any of the following instance removal policies:
-- Oldest instance created from oldest AS configuration: The oldest instance created from the oldest configuration is removed from the AS group first.
- Newest instance created from oldest AS configuration: The newest instance created from the oldest configuration is removed from the AS group first.
- Oldest instance: The oldest instance is removed from the AS group first.
- Newest instance: The latest instance is removed from the AS group first.
NOTE:- AS always balances instances across AZs first, regardless of which removal policy is used.
- Manually added ECS instances are the last to be removed. If AS does remove a manually added instance, it only removes the instance from the AS group. It does not delete instance. If multiple manually added instances must be removed, AS preferentially removes the earliest-added instance first.
Controls which instances are first to be removed during scale in. If specified conditions are met, scaling actions are triggered to remove instances by following the removal policy you choose. There are four instance removal policies for you to choose from:
+- Oldest instance created from oldest AS configuration: The oldest instance created from the oldest configuration is removed from the AS group first.
- Newest instance created from oldest AS configuration: The newest instance created from the oldest configuration is removed from the AS group first.
- Oldest instance: The oldest instance is removed from the AS group first.
- Newest instance: The latest instance is removed from the AS group first.
NOTE:Manually added ECS instances are the last to be removed. If AS does remove a manually added instance, it only removes the instance from the AS group. It does not delete the instance. If multiple manually added instances must be removed, AS preferentially removes the earliest-added instance first.
Oldest instance created from oldest AS configuration
@@ -107,33 +109,33 @@EIP
If EIP has been selected in an AS configuration for an AS group, an EIP is automatically bound to the ECS instance added by a scaling action to the AS group. If you select Release, the EIP bound to an instance is released when the instance is removed from the AS group. Otherwise, the system unbinds the EIP from the instance, but does not release it when the instance is removed from the AS group.
+If EIP has been selected in the AS configuration for the AS group, an EIP is automatically bound to the ECS instance added by a scaling action to the AS group. If you select Release, the EIP bound to an instance is released when the instance is removed from the AS group. Otherwise, the system unbinds the EIP from the instance, but does not release it when the instance is removed from the AS group.
N/A
+-
Health Check Method
When a health check detects an unhealthy ECS instance, AS replaces it with a new one. You can choose from either of the following health check methods:
-- ECS health check: checks ECS instance health status. If an instance is stopped or deleted, it is considered to be unhealthy. This method is selected by default. Using this method, the AS group periodically evaluates the running status of each instance based on the health check results. If the health check results show that an instance is unhealthy, AS removes the instance from the AS group.
- ELB health check: determines ECS running status using a load balancing listener. When a load balancing listener detects that an instance is unhealthy, AS removes the instance from the AS group.
If an ECS instance fails a health check, AS replaces it with a new one. There are two health check methods:
+- ECS health check: checks the ECS instance running status. If an instance is stopped or deleted, it is considered to be unhealthy. This method is selected by default. Using this method, the AS group periodically checks the running status of each instance. If the health check results show that an instance is unhealthy, AS removes the instance from the AS group.
- ELB health check: determines ECS running status using a load balancing listener. This health check method is only available if a load balancer is configured for the AS group. An instance is considered to be healthy only when all associated listeners detect it as healthy. If a listener detects that the instance is unhealthy, AS removes the instance from the AS group.
N/A
+-
Health Check Interval
Specifies the length of time between health checks. You can set a health check interval, such as 10 seconds, 1 minute, 5 minutes, 15 minutes, 1 hour, or 3 hours, based on the service requirements.
+Specifies the length of time between health checks. You can set a health check interval, such as 10 seconds, 1 minute, 5 minutes, 15 minutes, 1 hour, or 3 hours, based on service requirements.
5 minutes
Enterprise Project
Specifies the enterprise project to which the AS group belongs. If an enterprise project is configured for an AS group, ECSs created in this AS group also belong to this enterprise project. If you do not specify an enterprise project, the default enterprise project will be used.
-NOTE:- Value default indicates the default enterprise project. Resources that are not allocated to any enterprise projects under your account are displayed in the default enterprise project.
- Enterprise project is an upgraded version of IAM. It allocates and manages resources of different projects.
Specifies the enterprise project to which the AS group belongs. If an enterprise project is configured for an AS group, ECSs created in this AS group also belong to this enterprise project. If you do not specify an enterprise project, the default enterprise project will be used.
+NOTE:- Value default indicates the default enterprise project. Resources that are not allocated to any enterprise projects under your account are displayed in the default enterprise project.
- Enterprise project is an upgraded version of IAM. It allocates and manages resources of different projects.
N/A
+-
Advanced Settings
@@ -141,7 +143,7 @@Configure notifications and tags.
You can select Do not configure or Configure now.
N/A
+-
Notification Mode
@@ -149,7 +151,7 @@This parameter is optional. If this parameter is selected, the system will notify you of scaling action results by email after a scaling action is complete.
The notifications will be sent to the email address you specified when you registered yourself on the cloud.
N/A
+-
Tag
@@ -160,13 +162,13 @@- Value
- The value is optional.
- A key can have only one value.
- The value can include up to 43 characters. It can include digits, letters, underscores (_), and hyphens (-).
N/A
+-
- Click Next.
- On the displayed page, you can use an existing AS configuration or create an AS configuration. For details, see Creating an AS Configuration from an Existing ECS Instance and Creating an AS Configuration from a New Specifications Template.
- Click Next.
- (Optional) Add an AS policy to an AS group. +
- Click Next.
- On the displayed page, you can use an existing AS configuration or create an AS configuration. For details, see Creating an AS Configuration from an Existing ECS and Creating an AS Configuration from Scratch.
- Click Next.
- (Optional) Add an AS policy to an AS group.
On the displayed page, click Add AS Policy.
Configure the required parameters, such as the Policy Type, Scaling Action, and Cooldown Period. For details, see Dynamic Scaling and Scheduled Scaling.diff --git a/docs/as/umn/en-us_topic_0042018372.html b/docs/as/umn/en-us_topic_0042018372.html index fbd30e97..e3dd2031 100644 --- a/docs/as/umn/en-us_topic_0042018372.html +++ b/docs/as/umn/en-us_topic_0042018372.html @@ -9,17 +9,17 @@ - If a scaling action is triggered by an AS policy, the cooldown period is whatever configured for that AS policy.
- If a scaling action is triggered by manually changing the expected number of instances or by other actions, the cooldown period is whatever configured for the AS group.
-Scaling Action
A scaling action adds instances to or removes instances from an AS group. It ensures that the expected number of instances are running in the AS group by adding or removing instances when the triggering condition is met, which improves system stability.
Cooldown Period
To prevent an alarm-based policy from being triggered repeatedly by the same event, configure a cooldown period. A cooldown period specifies how long any alarm-triggered scaling action will be disallowed after a previous scaling action is complete. This cooldown period does not apply to scheduled or periodic scaling actions.
-For example, if you set the cooldown period to 300 seconds (5 minutes), and there is a scaling action scheduled for 10:32, but a previous scaling action was complete at 10:30, any alarm-triggered scaling actions will be denied during the cooldown period from 10:30 to 10:35, but the scheduled scaling action will still be triggered at 10:32. If the scheduled scaling action ends at 10:36, a new cooldown period starts at 10:36 and ends at 10:41.
+Cooldown Period
To prevent an alarm-based policy from being repeatedly triggered by the same event, you can set a 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.
+For example, suppose that the cooldown period is set to 300 seconds (5 minutes), and a scheduled policy is specified to trigger a scaling action at 10:32, and a previous scaling action triggered by an alarm policy ends at 10:30. Any alarm-triggered scaling action will then be denied during the cooldown period from 10:30 to 10:35, but the scaling action scheduled for 10:32 will still take place. If the scheduled scaling action ends at 10:36, a new cooldown period starts at 10:36 and ends at 10:41.
-Bandwidth Scaling
AS automatically adjusts a bandwidth based on the scaling policies you configured.
After you configure a scaling policy as needed, when the trigger condition is met, AS automatically increases, decreases, or sets the bandwidth to a specified value based on the policy you configured. Three types of bandwidth scaling policies are available, including the alarm, scheduled, and periodic policy.
Region
A region is a geographic area where the resources used by AS are located.
+-Region
A region is a geographic area where resources used by AS are located.
AZs in the same region can communicate with each other over an intranet, but AZs in different regions cannot.
-Cloud data centers are deployed worldwide and AS applies to different regions. Deploying AS in different regions allows you to tailor policies to better suit your requirements. For example, applications can be designed to meet user requirements in specific regions or comply with local laws or regulations.
+Cloud data centers are deployed in locations around the world. You can use AS in different regions. Deploying AS in different regions allows you to tailor policies to better suit your requirements. For example, applications can be designed to meet user requirements in specific regions or comply with local laws or regulations.
Project
A project is used to group and isolate OpenStack resources, including compute, storage, and network resources. A project can be a department or a project team. Multiple projects can be created under one account.
+Project
A project is used to group and isolate resources, including compute, storage, and network resources. A project can be a department or a project team. Multiple projects can be created under one account.
diff --git a/docs/as/umn/en-us_topic_0042018380.html b/docs/as/umn/en-us_topic_0042018380.html new file mode 100644 index 00000000..f9ff105b --- /dev/null +++ b/docs/as/umn/en-us_topic_0042018380.html @@ -0,0 +1,104 @@ + + +Managing Lifecycle Hooks
++Lifecycle hooks enable you to flexibly control addition and removal of ECS instances in AS groups and manage the lifecycle of ECS instances in AS groups. Figure 1 shows the instance lifecycle when no lifecycle hook is added to an AS group.
+ +Figure 2 shows the instance lifecycle when a lifecycle hook is added to an AS group.
+ +When the AS group scales in or out, the added lifecycle hooks are triggered, the scaling action is suspended, and the instance being added or removed is put into a wait state, as shown in 2 and 6 in Figure 2. During this period of time, you can perform some custom operations on the instance. For example, you can install or configure software on an instance being added to the AS group. A suspended scaling action will be resumed if either of the following occurs:
+- The timeout duration ends.
Assume that you have set the timeout period to 3,600s by referring to section Table 1. The suspended scaling action will be automatically resumed if the timeout duration (3,600s) ends.
+ - A callback action is performed to move the instance out of the wait state. For details, see Performing a Callback Action.
+Application Scenarios
- Instances newly added to an AS group need to be initialized before they are bound to a load balancer listener. Initialization means the software is installed and configured and the instance is fully ready to accept traffic.
- To remove an instance from an AS group, it needs to be first unbound from the load balancer listener, stop accepting new requests, and finish processing any accepted requests.
- Before instances are removed from an AS group, you may need to back up data or download logs.
- Other scenarios where custom operations need to be performed.
+How Lifecycle Hooks Work
After you add lifecycle hooks to an AS group, they work as follows:
+- Adding an ECS instance to an AS group
When an instance is initialized and added to an AS group, a lifecycle hook of the Instance adding type is automatically triggered. The instance enters the Wait (Adding to AS group) state, that is, the instance is suspended by the lifecycle hook. If you have configured a notification object, the system sends a message to the object. After receiving the message, you can perform custom operations, for example, installing software on the instance. The instance remains in a wait state until you complete the custom operations and perform a callback action (see Performing a Callback Action) or the timeout duration ends. After the instance moves out of a wait state, the specified default callback action will take place.
+- Continue: The instance will be added to the AS group.
- Abandon: The instance will be deleted and a new instance will be created.
If you have configured multiple Instance adding lifecycle hooks, all of them will be triggered when an instance is added to the AS group. If the default callback action of any lifecycle hook is Abandon, the instance will be deleted and a new instance will be created. If the default callback action of all lifecycle hooks is Continue, the instance is added to the AS group after suspension by the last lifecycle hook is complete.
+
- Removing an instance from an AS group
When an instance is removed from an AS group, the instance enters the Removing state. After a lifecycle hook is triggered, the instance enters the Wait (Removing from AS group) state. The system sends messages to the configured notification object. After receiving the message, you can perform custom operations, such as uninstalling software and backing up data. The instance remains in the wait state until you finish the custom operations and perform the default callback operation or the timeout duration ends. After the instance moves out of a wait state, the specified default callback action will take place.
+- Continue: The instance is removed from the AS group.
- Abandon: The instance is removed from the AS group.
If you have configured multiple lifecycle hooks, and the default callback action of all lifecycle hooks is Continue, the instance will be removed from the AS group until suspension by the remaining lifecycle hooks time out. If the default callback action of any lifecycle hook is Abandon, the instance will be directly removed from the AS group.
+
+Constraints
- You can add, modify, or delete a lifecycle hook when the AS group does not perform a scaling action.
- Up to five lifecycle hooks can be added to one AS group.
+Adding a Lifecycle Hook
- Log in to the management console.
- Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.
- Click the name of the AS group to which the lifecycle hook is to be added. On the AS group details page, click the Lifecycle Hooks tab and then Add Lifecycle Hook.
- In the displayed Add Lifecycle Hook dialog box, set the parameters listed in Table 1.
++
+Table 1 Parameter description Parameter
+Description
+Example Value
+Hook Name
+Specifies the lifecycle hook name. The name can contain letters, digits, underscores (_), and hyphens (-), and cannot exceed 32 characters.
+we12_w
+Hook Type
+Specifies the lifecycle hook type. The value can be Instance adding or Instance removal. Instance adding puts the instance being added to an AS group to the Wait (Adding to AS group) state. Instance removal puts the instance being removed from an AS group to Wait (Removing from AS group) state.
+Instance adding
+Default Callback Action
+Specifies the action that the system takes when an instance moves out of a wait state.
+The default callback action for an Instance adding lifecycle hook can be Continue or Abandon:+- Continue: If multiple lifecycle hooks are configured for the AS group, and the default callback action of all the hooks is Continue, the system will continue to add the instance to the AS group until the all lifecycle hooks time out.
- Abandon: If multiple lifecycle hooks are configured for the AS group, and the default callback action of one lifecycle hook is Abandon, the system will delete the instance and create another one without waiting for the remaining lifecycle hooks to time out.
The default callback action for an Instance removal lifecycle hook can be Continue or Abandon:+- Continue: If only one lifecycle hook is configured for the AS group, the system will remove the instance from the AS group. If multiple lifecycle hooks are configured for the AS group, and the default callback actions of all the hooks are Continue, the system will continue to remove the instance from the AS group until all lifecycle hooks time out.
- Abandon: If multiple lifecycle hooks are configured for the AS group, and the default callback action of one lifecycle hook is Abandon, the system will continue to remove the instance from the AS group without waiting for the remaining lifecycle hooks to time out.
Continue
+Timeout Duration (s)
+Specifies the amount of time for the instances to remain in a wait state. The value ranges from 60s to 86,400s.
+You can extend the timeout duration or perform a Continue or Abandon action before the timeout duration ends. For more information about callback actions, see Performing a Callback Action.
+3600
+Notification Topic
+Specifies a notification object for a lifecycle hook. For details, see "Creating a Topic" in Simple Message Notification User Guide. When an instance is suspended by the lifecycle hook, the system sends a notification to the object. This notification contains the basic instance information, your custom notification content, and the token for controlling lifecycle actions.
+N/A
+Notification Message
+After a notification object is configured, the system sends your custom notification to the object.
+-
+ - Click OK.
The added lifecycle hook is displayed on the Lifecycle Hooks page.
+
+Performing a Callback Action
- On the AS Groups page, click the name of the target AS group.
- On the displayed page, click the Instances tab.
- Locate the instance that has been suspended by the lifecycle hook and click Wait (Adding to AS group) or Wait (Removing from AS group) in the Lifecycle Status column.+
Callback actions can only be performed on instances that have been suspended by a lifecycle hook.
+ - In the displayed Added Hook dialog box, view the suspended instance and all the lifecycle hooks, and perform callback actions on lifecycle hooks.
Callback actions include:
+- Continue
- Abandon
- Extend timeout
If you have performed custom operations before the timeout duration ends, select Continue or Abandon to complete the lifecycle actions. For details about Continue and Abandon, see Table 1. If you need more time for custom operations, select Extend timeout to extend the timeout duration. Then, the timeout duration will be extended by 3600 seconds each time.
+
+Modifying a Lifecycle Hook
On the Lifecycle Hooks page, locate the target lifecycle hook and click Modify in the Operation column, see Table 1 for parameters. You can modify the parameter except Hook Name, such as Hook Type, Default Callback Action, and Timeout Duration.
++Deleting a Lifecycle Hook
On the Lifecycle Hooks page, locate the target lifecycle hook and click Delete in the Operation column.
+++ diff --git a/docs/as/umn/en-us_topic_0044453521.html b/docs/as/umn/en-us_topic_0044453521.html index a286e73c..ba2574c3 100644 --- a/docs/as/umn/en-us_topic_0044453521.html +++ b/docs/as/umn/en-us_topic_0044453521.html @@ -8,7 +8,37 @@++Parent topic: Scaling Action+
- A stateless process or application can be understood in isolation. There is no stored knowledge of or reference to past transactions. Each transaction is made as if from scratch for the first time.
- Only applications that are stateless and horizontally scalable can run on instances in an AS group.
- A stateless process or application can be understood in isolation. There is no stored knowledge of or reference to past transactions. Each transaction is made as if from scratch for the first time.
2023-03-31
+2024-09-19
+Modified the following content:
+Fixed the broken reference issue in Instance Lifecycle.
+2024-08-29
+Modified the following content:
+- Optimized Instance Lifecycle.
- Optimized Managing Lifecycle Hooks.
2024-07-19
+Modified the following content:
+Added Managing Lifecycle Hooks.
+2024-06-18
+Modified the following content:
+- Deleted "RDS" from AS and Other Services.
- Optimized descriptions in Region.
- Optimized operation scenarios in Enabling an AS Group.
- Optimized the ECS login mode in Copying an AS Configuration.
- Optimized descriptions in Table 2.
2024-05-17
+Modified the following content:
+- Added the instructions about how to enable IPv6 for subnets in Creating an AS Group.
2023-03-31
Added the following content:
- Section Permission Management in Service Overview.
- Section Permission Management in User Guide.
2023-02-08
This release incorporates the following change:
+Modified the following content:
Redesigned the table structure in Instance Lifecycle.
2022-09-06
The release incorporates the following changes:
-Optimized keywords.
+Optimized keywords.
2021-10-20
This release incorporates the following changes:
-Modified the following content:
-- Optimized the description of AS group parameters in sections Creating an AS Group Quickly and Creating an AS Group.
- Optimized the description of AS configuration parameters in sections Creating an AS Configuration from an Existing ECS Instance and Creating an AS Configuration from a New Specifications Template.
Modified the following content:
+- Optimized the description of AS group parameters in sections Creating an AS Group Quickly and Creating an AS Group.
- Optimized the description of AS configuration parameters in sections Creating an AS Configuration from an Existing ECS and Creating an AS Configuration from Scratch.
2020-10-19
This release incorporates the following changes:
-Added section "Access Methods".
+Added section "Access Methods."
2019-04-18
@@ -76,13 +103,13 @@2018-08-30
Modified the following content:
-- The cooldown period starts after a scaling action is complete and the default cooldown period is 300 seconds.
- Added FAQ "What Is a Cooldown Period? How Is It Calculated?"
- Added the application scenarios of the scaling bandwidth in Bandwidth Scaling.
- Optimized values of parameter EIP in Creating an AS Configuration from an Existing ECS Instance and Creating an AS Configuration from a New Specifications Template.
- Optimized some UI strings and operation steps.
- Modified the calculation of the cooldown period. The cooldown period starts after a scaling action is complete and the default cooldown period is 300 seconds.
- Added FAQ "What Is a Cooldown Period? How Is It Calculated?"
- Added the application scenarios of the scaling bandwidth in Bandwidth Scaling.
- Optimized values of parameter EIP in Creating an AS Configuration from an Existing ECS and Creating an AS Configuration from Scratch.
- Optimized some UI strings and operation steps.
2018-08-21
Modified the following content:
-Optimized content in Setting Up an Automatically Scalable Discuz! Forum, Creating an AS Group Quickly, Dynamic Scaling, Creating a Bandwidth Scaling Policy, and Health Check.
+Optimized Setting Up an Automatically Scalable Discuz! Forum, Creating an AS Group Quickly, Dynamic Scaling, Creating a Bandwidth Scaling Policy, and Health Check.
2018-07-30
@@ -100,7 +127,7 @@2018-05-30
Modified the following content:
-- Added "View Audit Logs" to Recording AS Resource Operations.
- Added Monitoring Metrics.
- Added Viewing Monitoring Metrics.
- Added Setting Monitoring Alarm Rules.
- Added FAQ "What Can I Do If the AS Group Fails to Be Enabled?"
- Added FAQ "How Should I Handle Unhealthy Instances in an AS Group?"
- Added "View Audit Logs" to Recording AS Resource Operations.
- Added Monitoring Metrics.
- Added Viewing Monitoring Metrics.
- Added Setting Monitoring Alarm Rules.
- Added FAQ "What Can I Do If an AS Group Fails to Be Enabled?"
- Added FAQ "How Should I Handle Unhealthy Instances in an AS Group?"
2018-04-30
@@ -135,7 +162,7 @@2017-07-30
Modified the following content:- Optimized the wizard-based AS group creation process. You must create or use an existing AS configuration after creating an AS group.
- Added Change AS Configuration in the More drop-down list and View AS Policy in the Operation column on the AS Groups page.
- Added the function of marking AS groups and instances.
- Optimized "Creating an AS Group Quickly" and "Creating an AS Group".
- Supported multiple projects.
Modified the following content:- Optimized the wizard-based AS group creation process. You must create or use an existing AS configuration after creating an AS group.
- Added Change AS Configuration in the More drop-down list and View AS Policy in the Operation column on the AS Groups page.
- Added the function of tagging AS groups and instances.
- Optimized "Creating an AS Group Quickly" and "Creating an AS Group".
- Supported multiple projects.
Specifies the region where the AS group resides.
N/A
+-
Policy Name
@@ -26,14 +26,14 @@Specifies the name of the bandwidth scaling policy.
The name consists of only letters, digits, underscores (_), and hyphens (-).
N/A
+-
EIP
Specifies the public network IP address whose bandwidth needs to be scaled.
N/A
+-
Policy Type
@@ -48,12 +48,12 @@You can use an existing alarm rule or create a new one.
To create an alarm rule, configure the following parameters:- Rule Name
Specifies the name of the new alarm rule, for example, as-alarm-7o1u.
- Trigger Condition
Select a monitoring metric and trigger condition based on the metric. Table 2 lists the supported monitoring metrics. An example value is Outbound Bandwidth Avg. > 100 bit/s.
- - Monitoring Interval
Specifies the period for the metric, for example, 5 minutes.
+ - Monitoring Interval
Specifies the monitoring period for the metric, for example, 5 minutes.
- Consecutive Occurrences
Specifies the number of consecutive periods in which the triggering condition is met for triggering a scaling action.
N/A
+-
Scaling Action
@@ -68,12 +68,12 @@N/A
+-
Cooldown Period
Specifies a period of time in the unit of second 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.
+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
- 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 a Scheduled or Periodic Bandwidth Scaling Policy
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- Under Computing, 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, policy type, and trigger condition. For details, see Table 3.
+
Creating a Scheduled or Periodic Bandwidth Scaling Policy
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- Under Computing, 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, policy type, and trigger condition. For details, see Table 3.
-
Table 3 Scheduled or periodic policy parameters Parameter
Description
@@ -127,7 +127,7 @@Specifies the region where the AS group resides.
N/A
+-
Policy Name
@@ -140,28 +140,28 @@EIP
Specifies the public network IP address whose bandwidth needs to be scaled. This parameter is mandatory when Resource Type is set to EIP.
+Specifies the public network IP address whose bandwidth needs to be scaled.
N/A
+-
Policy Type
Specifies the policy type. You can select a scheduled or periodic policy.
If you select Periodic, you are required to configure two more parameters:
-N/A
+-
Triggered At
Specifies a time at which the AS policy is triggered.
+Specifies the time at which the AS policy is triggered.
N/A
+-
Scaling Action
@@ -176,12 +176,12 @@N/A
+-
Cooldown Period
Specifies a period of time in the unit of second 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.
+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
- After setting the parameters, click Create Now.
- After setting the parameters, click Create Now.
diff --git a/docs/as/umn/en-us_topic_2019013003.html b/docs/as/umn/en-us_topic_2019013003.html index eeb9d769..cf3dff89 100644 --- a/docs/as/umn/en-us_topic_2019013003.html +++ b/docs/as/umn/en-us_topic_2019013003.html @@ -1,16 +1,19 @@Overview
-AS policies can trigger scaling actions to adjust bandwidth or the number of instances in an AS group. An AS policy defines the conditions for triggering a scaling action and the operation that will be performed. When the triggering condition is met, a scaling action is triggered automatically.
+diff --git a/docs/as/umn/index.html b/docs/as/umn/index.html index 47ce77dc..28e93685 100644 --- a/docs/as/umn/index.html +++ b/docs/as/umn/index.html @@ -1,8 +1,7 @@AS policies can trigger scaling actions to adjust bandwidth or the number of instances in an AS group. An AS policy defines the conditions for triggering a scaling action and the operation to be performed in a scaling action. When the trigger condition is met, a scaling action is triggered automatically.
+ If multiple AS policies are applied to an AS group, a scaling action is triggered as long as any of the AS policies is invoked, provided that the AS policies do not conflict with each other.
+The number of instances in the AS group will never exceed the specified maximum and minimum numbers of instances.
Constraints
A maximum of 50 AS policies can be created for an AS group.
+AS supports the following policies:
- Alarm policy: AS automatically adjusts the number of instances in an AS group or sets the number of instances to the configured value when an alarm is generated for a configured metric, such as CPU Usage.
- Scheduled policy: AS automatically increases or decreases the number of instances in an AS group or sets the number of instances to the configured value at a specified time.
- Periodic policy: AS automatically increases or decreases the number of instances in an AS group or sets the number of instances to the configured value at a configured interval, such as daily, weekly, and monthly.
Resource Adjustment Modes
- Dynamic
AS adjusts the number of instances or bandwidth when an alarm policy is triggered.
This mode is suitable for scenarios where workloads are unpredictable. Alarm policies are used to trigger scaling actions based on real-time monitoring data (such as CPU usage) to dynamically adjust the number of instances in the AS group.
- Planned
AS adjusts the number of instances or bandwidth when a periodic or scheduled policy is triggered.
This mode is suitable for scenarios where workloads are periodic.
- - Manual
AS allows you to adjust resources by manually adding instances to an AS group, removing instances from an AS group, or changing the expected number of instances.
+ - Manual
You can change the size of an AS group manually. You can either add or remove instances to or from the AS group, or modify the expected number of instances of the AS group.
FAQs
--+ - How Many AS Policies Can I Enable?
- What Can I Do If the AS Group Fails to Be Enabled?
- AS requires authentication provided by Identity and Access Management (IAM).
- AS requires authentication provided by Identity and Access Management (IAM).
Procedure
Create an ECS and install a MySQL database.
You can create a relational database using the Relational Database Service (RDS) service provided by the cloud platform, or create an ECS and install the database there. In this section, we will install a MySQL database on a newly created ECS.
