Enabling an AS Group
-Scenarios
You can enable an AS group to automatically scale in or out capacity.
+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.
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.
Deleting an AS Group
Scenarios
You can delete an AS group when it is no longer required.
-- If an AS group is not required during a specified period of time, 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 those AS policies will be automatically deleted.
- 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.
Setting Up an Automatically Scalable Discuz! Forum
-Overview
AS automatically adds instances to an AS group for applications and removes unneeded ones on demand. You do not need to prepare a large number of extra ECS instances for an expected marketing activity or unexpected peak hours. By eliminating the need to deploy those extra instances, AS ensures system reliability and reduces your operating costs.
+Overview
AS automatically adds instances to an AS group for applications and removes unneeded ones on demand. You do not need to prepare a large number of extra ECS instances for expected marketing activities or unexpected peak hours. By eliminating the need to deploy those extra instances, AS ensures system reliability and reduces your operating costs.
This section describes how to use services, such as AS, ECS, ELB, and VPC to deploy a web service that can be automatically scaled in and out, for example, a Discuz! forum.
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.
-- 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.
- - Deploy the forum.
For instructions about how to deploy the Discuz! forum, see 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 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 and deploy a Discuz! forum on it.- 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.
Create a private image.
-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, so 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.
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.
@@ -25,7 +25,7 @@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.
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 on this ECS so that it will not be automatically removed from 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.
An AS policy specifies the conditions for triggering a scaling action. After you create an AS policy for the AS group, AS automatically increases or decreases the number of instances based on the policy.
You can configure an alarm-based AS policy. When Cloud Eye generates an alarm for a monitoring metric, such as vCPU usage, AS automatically increases or decreases the number of instances in the AS group. If traffic fluctuations are predictable, you can also configure a scheduled or periodic AS policy.
diff --git a/docs/as/umn/as_02_0102.html b/docs/as/umn/as_02_0102.html index 403ea3cc..98bf324b 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 vCPUs, memory, image, disk, and ECS type in the AS configuration are the same as those of the selected instance by default.
+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.
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
@@ -28,8 +28,8 @@Configuration Template
Select Use specifications of an existing ECS > Select ECS.
-The ECS type, vCPUs, memory, image, and disk information in the AS configuration are the same as those of the selected ECS by default.
+Choose Use specifications of an existing ECS > Select ECS.
+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.
Use specifications of an existing ECS
-
+N/A
Specifications
The public cloud provides various ECS types for different application scenarios.
-For more information, see Elastic Cloud Server User Guide.
+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
@@ -70,15 +70,15 @@Disk
Includes system disks and data disks.- System Disk
Common I/O: uses Serial Advanced Technology Attachment (SATA) drives to store data.
+- System Disk
Common I/O: uses Serial Advanced Technology Attachment (SATA) drives to store data.
High I/O: uses serial attached SCSI (SAS) drives to store data.
Ultra-high I/O: uses solid state disk (SSD) drives to store data.
If the image based on which an ECS is created is encrypted, the system disk of the ECS is automatically encrypted. In addition, the name of the encrypted key is displayed on the page.
- Data Disk
You can create multiple data disks for an ECS instance. 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.
- 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.
For more information about EVS disk encryption, see Elastic Volume Service User Guide.
- System Disk
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.
-
- 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.
Automatically assign
Advanced Settings
This parameter allows you to configure and User Data.
+This parameter allows you to configure User Data.
You can select Do not configure or Configure now.
N/A
@@ -129,7 +127,7 @@-
+N/A
Deleting an AS Configuration
-Scenarios
When you no longer need an AS configuration, you can delete it as long as the AS configuration is not used by an AS group. You can delete a single AS configuration or delete them batches.
+Scenarios
When you no longer need an AS configuration, you can delete it as long as the AS configuration is not used by an AS group. You can delete a single AS configuration or delete them in batches.
diff --git a/docs/as/umn/as_03_0102.html b/docs/as/umn/as_03_0102.html index 4c869eb1..196e7a01 100644 --- a/docs/as/umn/as_03_0102.html +++ b/docs/as/umn/as_03_0102.html @@ -3,8 +3,7 @@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.
- Click the AS Configurations tab page, locate the row containing the target AS configuration, and click Delete in the Operation column to delete this AS configuration. You can also select multiple AS configurations to be deleted and click Delete in the upper part of the AS configuration list to delete them all at once.
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.
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.
+
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.
Table 1 AS policy parameters Parameter
Description
@@ -73,75 +72,77 @@- 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.
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.
-
Table 2 Parameter description Parameter
+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.
+
Table 2 Parameter description Parameter
Description
+Description
Example Value
+Example Value
Policy Name
+Policy Name
Specifies the name of the AS policy to be created.
+Specifies the name of the AS policy to be created.
as-policy-p6g5
+as-policy-p6g5
Policy Type
+Policy Type
Select Scheduled or Periodic for expanding resources at a specified time.
-If you select Periodic, you are required to configure two more parameters:
-- Interval
- One day
- One week
- One month
Select Scheduled or Periodic for expanding resources at a specified time.
+If you select Periodic, you are required to configure two more parameters:
+- Period
- Day
- Week
- Month
N/A
+N/A
+
Time Zone
+Time Zone
The default value is GMT+08:00.
-GMT+08:00 is 8:00 hours ahead of Greenwich Mean Time.
+The default value is GMT+08:00.
+GMT+08:00 is 8:00 hours ahead of Greenwich Mean Time.
GMT+08:00
+GMT+08:00
Triggered At
+Triggered At
Specifies a time at which the AS policy is triggered.
+Specifies the time at which the AS policy is triggered.
N/A
+N/A
+ +Scaling Action
+Scaling Action
Specifies an action and the number of instances.
-The following scaling action options are available:- Add
Adds instances to an AS group when the scaling action is performed.
- - Reduce
Removes instances from an AS group when the scaling action is performed.
- - Set to
Sets the expected number of instances in an AS group to a specified value.
+Specifies an action and the number of instances.
+- Add 1 instance
- Add 10% instances
The number of instances to be added is 10% of the current number of instances in the AS group. If the product of the current number of instances and the percentage is not an integer, AS automatically rounds the value up or down:
-- If the value is greater than 1, it is rounded down.
- If the value is greater than 0 but less than 1, it is rounded up to 1.
- Add 1 instance
- Add 10% instances
The number of instances to be added is 10% of the current number of instances in the AS group. If the product of the current number of instances and the percentage is not an integer, AS automatically rounds the value up or down:
+- If the value is greater than 1, it is rounded down.
- If the value is greater than 0 but less than 1, it is rounded up to 1.
Cooldown Period
+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.
-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.
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.
+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.
300
+300
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_0103.html b/docs/as/umn/as_04_0103.html index 224a1314..33557b22 100644 --- a/docs/as/umn/as_04_0103.html +++ b/docs/as/umn/as_04_0103.html @@ -1,7 +1,7 @@Manual Scaling
-Scenarios
You can manually add or remove instances to or from an AS group, or changing the expected number of instances.
+Scenarios
You can manually add or remove instances to or from an AS group, or change the expected number of instances.
@@ -16,7 +16,7 @@Procedure
Adding instances to an 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.
- 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.
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.
diff --git a/docs/as/umn/as_04_0105.html b/docs/as/umn/as_04_0105.html index 68e3da9d..a1f72678 100644 --- a/docs/as/umn/as_04_0105.html +++ b/docs/as/umn/as_04_0105.html @@ -3,11 +3,11 @@Viewing a Scaling Action
-Scenarios
This section describes how to check whether a scaling action has been performed and how to view scaling action details.
diff --git a/docs/as/umn/as_04_0107.html b/docs/as/umn/as_04_0107.html index 9afc3175..63305055 100644 --- a/docs/as/umn/as_04_0107.html +++ b/docs/as/umn/as_04_0107.html @@ -1,7 +1,7 @@Viewing Scaling Actions
The following steps illustrate how to view scaling actions of an AS group.
+Viewing Monitoring Data
The following steps illustrate how to view scaling actions of an AS group.
- 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 particular 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 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.
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_0102.html b/docs/as/umn/as_05_0102.html index 54e6b2f8..ddabb14f 100644 --- a/docs/as/umn/as_05_0102.html +++ b/docs/as/umn/as_05_0102.html @@ -1,7 +1,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.
Viewing Details About a Bandwidth Scaling Policy
-Scenarios
You can view details about a bandwidth scaling policy, including its basic information and execution logs. Policy execution logs record details about policy execution. This section describes how to create a bandwidth scaling policy.
+Scenarios
You can view details about a bandwidth scaling policy, including its basic information and execution logs. Policy execution logs record details about policy execution.
diff --git a/docs/as/umn/as_05_0103.html b/docs/as/umn/as_05_0103.html index 2252c6f7..f29fad86 100644 --- a/docs/as/umn/as_05_0103.html +++ b/docs/as/umn/as_05_0103.html @@ -3,7 +3,7 @@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 Bandwidth Scaling.
- On the Bandwidth Scaling page, click the name of a bandwidth scaling policy to go to the page showing its basic information and view its details. You can view basic information about the scaling policy, including Policy Type, Trigger Condition, and Scaling Action.
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 corresponding to a released EIP still occupies the policy quota. Only the account and its IAM users with the global permission can manage the AS bandwidth 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.
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_0101.html b/docs/as/umn/as_06_0101.html index 86d942b6..b895c9c9 100644 --- a/docs/as/umn/as_06_0101.html +++ b/docs/as/umn/as_06_0101.html @@ -1,8 +1,8 @@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 check.
-- ECS health check: checks ECS instance running status. If an instance is stopped or deleted, it is considered as 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.
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.
diff --git a/docs/as/umn/as_06_0103.html b/docs/as/umn/as_06_0103.html index bfa68fd3..b5f89092 100644 --- a/docs/as/umn/as_06_0103.html +++ b/docs/as/umn/as_06_0103.html @@ -5,7 +5,7 @@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.
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.
-Table 1 list the AS operations that can be recorded by CTS. +Table 1 lists the AS operations that can be recorded by CTS.Table 1 AS operations that can be recorded by CTS Operation
Resource Type
@@ -166,12 +166,10 @@ -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 Source, Resource Type, and Search By
Select a filter criterion from the drop-down list.
-When you select Trace name for Search By, you need to select a specific trace name.
-When you select Resource ID for Search By, you need to select or enter a specific resource ID.
-When you select Resource name for Search By, you need to select or enter a specific resource name.
- - Operator: Select a specific operator (at user level rather than tenant level).
- Trace Status: Available options include All trace statuses, normal, warning, and incident. You can only select one of them.
- Time range: In the upper right corner of the page, you can query traces in the last one hour, last one day, last one week, or within a customized period of time.
- Trace Source, Resource Type, and Search By
- Click
to the left of the required trace to expand its details. - Locate the required trace and click View Trace in the Operation column. A dialog box is displayed, showing the trace content.
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:{ diff --git a/docs/as/umn/as_06_0104.html b/docs/as/umn/as_06_0104.html index 9fc82a41..d5c0ad21 100644 --- a/docs/as/umn/as_06_0104.html +++ b/docs/as/umn/as_06_0104.html @@ -4,7 +4,7 @@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.
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 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.
+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.
After you allocate a tag to an AS group, the system will automatically add the tag to the instances automatically created in the AS group. If you add a tag to an AS group or modify the tag, the new tag will be added to the ECSs automatically created in the AS group. Creating, deleting, or modifying the tag of an AS group will have no impact on the ECSs in the AS group.
Restrictions of Using Tags
You must observe the following rules when using tags:- Each AS group can have a maximum of 10 tags added to it.
- Each tag contains a key and a value.
- You can set the tag value to an empty character string.
- If you delete an AS group, all tags of it will also be deleted.
Tag Key
- The value cannot be empty.
- An AS group has a unique 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 (_).
Organization
Tag Value
- The value can be an empty character string.
- A key can have only one 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 (_).
Apache
- Click OK.
diff --git a/docs/as/umn/as_07_0100.html b/docs/as/umn/as_07_0100.html new file mode 100644 index 00000000..48a3c176 --- /dev/null +++ b/docs/as/umn/as_07_0100.html @@ -0,0 +1,17 @@ + + +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
Permissions Management
+ ++ + ++ diff --git a/docs/as/umn/as_07_0102.html b/docs/as/umn/as_07_0102.html new file mode 100644 index 00000000..a9acbd74 --- /dev/null +++ b/docs/as/umn/as_07_0102.html @@ -0,0 +1,24 @@ + + +++Parent topic: AS Management+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.
If your account does not require individual IAM users, skip this section.
+This section describes the procedure for granting permissions (see Figure 1).
++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.
++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.
++ diff --git a/docs/as/umn/as_07_0103.html b/docs/as/umn/as_07_0103.html new file mode 100644 index 00000000..277a5b3c --- /dev/null +++ b/docs/as/umn/as_07_0103.html @@ -0,0 +1,42 @@ + + +++Parent topic: Permissions Management+AS Custom Policies
+++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.
++Example Custom Policies
- Example 1: Allowing users to remove instances from an AS group and create AS configurations
{ + "Version": "1.1", + "Statement": [ + { + "Effect": "Allow", + "Action": [ + "as:instances:delete", + "as:configs:create" + ] + } + ] +}+ - 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:
+{ + "Version": "1.1", + "Statement": [ + { + "Action": [ + "as:groups:delete" + ], + "Effect": "Deny" + } + ] +}+
++ diff --git a/docs/as/umn/as_faq_0008.html b/docs/as/umn/as_faq_0008.html index de435a4d..916379f8 100644 --- a/docs/as/umn/as_faq_0008.html +++ b/docs/as/umn/as_faq_0008.html @@ -31,7 +31,7 @@ fi result=`fdisk -l $disk | grep $disk` if [ $result = 1 ] then - echo "disk path is not exist in linux,exit" + echo "disk path does not exist in linux,exit" exit fi diff --git a/docs/as/umn/as_faq_0011.html b/docs/as/umn/as_faq_0011.html index 2bf770ff..4375586d 100644 --- a/docs/as/umn/as_faq_0011.html +++ b/docs/as/umn/as_faq_0011.html @@ -1,8 +1,8 @@++Parent topic: Permissions Management+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 the 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 using the private image. For details, see Creating an AS Configuration from a New Specifications Template. Ensure that the image in the AS configuration is 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.
+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.
diff --git a/docs/as/umn/as_faq_0012.html b/docs/as/umn/as_faq_0012.html index efd9fd4a..ef0f499b 100644 --- a/docs/as/umn/as_faq_0012.html +++ b/docs/as/umn/as_faq_0012.html @@ -8,7 +8,7 @@Handling Method
- Check whether the ECS needs to be logged in to.
- If yes, use the original image password or key pair to log in to this ECS.
The original image password or key pair is the OS password or key pair configured when the private image was created.
- If no, go to step 2.
- If yes, use the original image password or key pair to log in to this ECS.
- Change the AS configuration for the AS group. For details, see Changing the AS Configuration for an AS Group.
- Change the AS configuration of the AS group. For details, see Changing the AS Configuration for an AS Group.
Make sure that Cloud-Init or Cloudbase-Init has been installed on the image specified in the new AS configuration. For how to install Cloud-Init or Cloudbase-Init, see Image Management Service User Guide.
After the AS configuration is changed, you can use the key file to log in to the new ECSs that are added to the AS group during scaling actions. You do not need to use the original image password or key pair to log in to these new ECSs anymore.
diff --git a/docs/as/umn/as_faq_0033.html b/docs/as/umn/as_faq_0033.html index 9403ff42..f5f488f6 100644 --- a/docs/as/umn/as_faq_0033.html +++ b/docs/as/umn/as_faq_0033.html @@ -1,7 +1,7 @@How Do I Fix the Error "The key pair does not exist" When I Connect to an Instance?
-A key pair is specific to each user. If the key pair of a user who is under the same account as you is configured for an AS configuration, you cannot connect the instances scaled out using that AS configuration.
+A key pair is specific to each user. If the key pair of a user who belongs to the same account as you is configured for an AS configuration, you cannot connect the instances scaled out using that AS configuration.
If you want to connect to these instances without being restricted by the key pair permission, password authentication needs to be configured as the login mode.
diff --git a/docs/as/umn/as_faq_1904.html b/docs/as/umn/as_faq_1904.html index 48444a56..23fc9e12 100644 --- a/docs/as/umn/as_faq_1904.html +++ b/docs/as/umn/as_faq_1904.html @@ -7,7 +7,7 @@-Based on the scaling rules, the manually added instances are not created based on the AS configuration used by the AS group. The instances automatically added using the AS configuration are removed at first. The manually added instances would not be removed until all of the automatically added instances have been removed first. Finally, since you have set the minimum number of instances to N or a larger value, those instances cannot be removed.
Note: If the instances manually added are stopped or if they malfunction, they are marked as unhealthy and removed from the AS group. This is because health checks ensure that all instances in the AS group are healthy.
diff --git a/docs/as/umn/as_pro_0001.html b/docs/as/umn/as_pro_0001.html index e0b5991e..8adf9d83 100644 --- a/docs/as/umn/as_pro_0001.html +++ b/docs/as/umn/as_pro_0001.html @@ -1,15 +1,15 @@Method 2
Enable instance protection for the N instances. For more information, see Configuring Instance Protection.
+Method 2
Enable instance protection for these instances. For details, see Configuring Instance Protection.
You can enable instance protection for these instances at the same time. When the AS group scales in, protected instances will not be removed from the AS group as long as they do not fail health checks. Instances that fail health check will be removed even if they are protected.
AS Advantages
-AS automatically scales resources to keep up with service demands based on pre-configured AS policies. With automatic resource scaling, you can enjoy reduced costs, improved availability, and high fault tolerance. AS is used for following scenarios:
-- Heavy-traffic forums: The traffic on a popular forum is difficult to predict. AS dynamically adjusts the number of ECS instances based on monitored ECS metrics, such as vCPU and memory usage.
- E-commerce: During big promotions, E-commerce websites need more resources. AS automatically increases ECS instances and bandwidths within minutes to ensure that promotions go smoothly.
- Live streaming: A live streaming website may broadcast popular programs from 14:00 to 16:00 every day. AS automatically scales out ECS and bandwidth resources during this period to ensure a smooth viewer experience.
AS automatically scales resources to keep up with service demands based on pre-configured AS policies. With automatic resource scaling, you can enjoy reduced costs, improved availability, and high fault tolerance. AS is used for the following scenarios:
+- Heavy-traffic forums: The traffic on a popular forum is difficult to predict. AS dynamically adjusts the number of ECS instances based on monitored ECS metrics, such as vCPU and memory usage.
- E-commerce: During big promotions, e-commerce websites need more resources. AS automatically increases ECS instances and bandwidths within minutes to ensure that promotions go smoothly.
- Live streaming: A livestreaming website may broadcast popular programs from 14:00 to 16:00 every day. AS automatically scales out ECS and bandwidth resources during this period to ensure a smooth viewer experience.
Automatic Resource Scaling
AS adds ECS instances and increases bandwidths for your applications when the access volume increases and removes unneeded resources when the access volume drops, ensuring system stability and availability.
- Scaling ECS Instances on Demand
AS scales ECS instances for applications based on demand, improving cost management. ECS instances can be scaled dynamically, on a schedule, or manually:
- Dynamic scaling
Dynamic scaling allows scale resources in response to changing demand using alarm-based policies. For details, see Dynamic Scaling.
- - Scheduled scaling
Scheduled scaling helps you to set up your own scaling schedule according to predictable load changes by creating periodic or scheduled policies. For details, see Scheduled Scaling.
+ - Scheduled scaling
Scheduled scaling helps you set up your scaling schedule according to predictable load changes by creating periodic or scheduled policies. For details, see Scheduled Scaling.
- Manual scaling
You can either manually change the expected number of instances of your AS group, or add or remove instances to or from the AS group. For details, see Manual Scaling.
Consider a train ticket booking application running on the public cloud. The load of the application may be relatively low during Q2 and Q3 because there are not many travelers, but relatively high during Q1 and Q4. Traditionally, there are two ways to plan for these changes in load. The first option is to provision enough servers so that the application always has enough capacity to meet demand, as shown in Figure 1. The second option is to provision servers according to the average load of the application, as shown in Figure 2. However, these two options may waste resources or be unable to meet demand during peak seasons. By enabling AS for this application, you have a third option available. AS helps you scale servers to keep up with changes in demand. This allows the application to maintain steady, predictable performance without wasting money on any unnecessary resources, as shown in Figure 3.
+Consider a train ticket booking application running on the public cloud. The load of the application may be relatively low during Q2 and Q3 because there are not many travelers, but relatively high during Q1 and Q4. Traditionally, there are two ways to plan for these changes in load. The first option is to provide enough servers so that the application always has enough capacity to meet demand, as shown in Figure 1. The second option is to provision servers according to the average load of the application, as shown in Figure 2. However, these two options may waste resources or be unable to meet demand during peak seasons. By enabling AS for this application, you have a third option available. AS helps you scale servers to keep up with changes in demand. This allows the application to maintain steady, predictable performance without wasting money on any unnecessary resources, as shown in Figure 3.
@@ -19,18 +19,18 @@ - Dynamic scaling
- Scheduled policies
The system automatically increases, decreases, or adjusts the bandwidth to a fixed value on a fixed schedule.
- Periodic policies
The system periodically adjusts the bandwidth based on a configured periodic cycle.
For example, you can use an alarm-based policy to regulate the bandwidth for a live streaming website.
-For a live streaming website, service load is difficult to predict. In this example, the bandwidth needs to be dynamically adjusted between 10 Mbit/s and 30 Mbit/s based on metrics such as outbound traffic and inbound traffic. AS can automatically adjust the bandwidth to meet requirements. You just need to select the relevant EIP and create two alarm policies. One policy is to increase the bandwidth by 2 Mbit/s when the outbound traffic is greater than X bytes, with the limit set to 30 Mbit/s. The other policy is to decrease the bandwidth by 2 Mbit/s when the outbound traffic is less than X bytes, with the limit set to 10 Mbit/s.
+For example, you can use an alarm-based policy to regulate the bandwidth for a livestreaming website.
+For a livestreaming website, service load is difficult to predict. In this example, the bandwidth needs to be dynamically adjusted between 10 Mbit/s and 30 Mbit/s based on metrics such as outbound traffic and inbound traffic. AS can automatically adjust the bandwidth to meet requirements. You just need to select the relevant EIP and create two alarm policies. One policy is to increase the bandwidth by 2 Mbit/s when the outbound traffic is greater than X bytes, with the limit set to 30 Mbit/s. The other policy is to decrease the bandwidth by 2 Mbit/s when the outbound traffic is less than X bytes, with the limit set to 10 Mbit/s.
- Evenly Distributing Instances by AZ
diff --git a/docs/as/umn/as_pro_0002.html b/docs/as/umn/as_pro_0002.html index b63d1f04..5226174b 100644 --- a/docs/as/umn/as_pro_0002.html +++ b/docs/as/umn/as_pro_0002.html @@ -1,173 +1,198 @@To reduce the impact of power or network outage on system stability, AS attempts to distribute ECS instances evenly across the AZs that are used by an AS group.
-A region is a geographic area where resources used by ECS instances are located. Each region contains multiple Availability Zones (AZs) where resources use independent power supplies and networks. AZs are physically isolated from one another but interconnected through an intranet. AZs are engineered to be isolated from failures in other AZs. They provide cost-effective, low-latency network connections to other AZs in the same region.
-An AS group can contain ECS instances in one or more AZs within a region. During scale the capacity of an AS group, AS attempts to evenly distribute ECS instances across AZs used by the AS group based on the following rules:
+A region is a geographic area where resources used by ECS instances are located. Each region contains multiple AZs where resources use independent power supplies and networks. AZs are physically isolated from one another but interconnected through an intranet. AZs are engineered to be isolated from failures in other AZs. They provide cost-effective, low-latency network connections to other AZs in the same region.
+An AS group can contain ECS instances in one or more AZs within a region. When scaling the capacity of an AS group, AS attempts to evenly distribute ECS instances across AZs used by the AS group based on the following rules:
Evenly distributing new instances to balanced AZs
AS attempts to evenly distribute ECS instances across the AZs used by an AS group. To do it, AS adds new instances to the AZ with the fewest instances.
Consider an AS group containing four instances that are evenly distributed in the two AZs used by the AS group. If a scaling action is triggered to add four more instances to the AS group, AS adds two to each AZ.
Figure 4 Evenly distributing instances
Re-balancing instances across AZs
-After you have manually added or removed instances to or from an AS group, the AS group can become unbalanced between AZs. AS compensates by re-balancing the AZs during the next scaling action.
+After you have manually added or removed instances to or from an AS group, the AS group can become unbalanced between AZs. AS compensates by re-balancing the AZs during the next scaling action.
Consider an AS group containing three instances that are distributed in AZ 1 and AZ 2, with two in AZ 1 and one in AZ 2. If a scaling action is triggered to add five more instances to the AS group, AS adds two to AZ 1 and three to AZ 2.
Figure 5 Re-balancing instances
Instance Lifecycle
-The ECS instances in an AS group transitions through different statues from the moment it is created to its removal.
+An ECS instance in an AS group goes through different statuses from its creation to its removal.
The instance status changes as shown in Figure 1 if you have not added a lifecycle hook to the AS group.-When trigger condition 2 or 4 is met, the system autonomously puts instances into the next status. -Table 1 Instance statuses Status
+When trigger condition 2 or 4 is met, the system autonomously puts instances into the next status.
+ ++Table 1 Instance statuses Status
Sub-status
+Sub-status
Status Description
+Status Description
Trigger Condition
+Trigger Condition
Initial
+Initial
None
+None
The instance has not been added to the AS group.
+The instance has not been added to the AS group.
The instance status will be changed to Adding to AS group when either of the following occurs:- 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.
N/A
+Adding to AS group
+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.
Adding to AS group
+Adding to AS group
Add the instance.
+(Optional) Associate the instance with a load balancing listener.
When trigger condition 1 is met, AS adds the instance to expand the AS group capacity.
+When trigger condition 1 is met, AS associates the created 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.
-Enabled
-None
-The instance is added to the AS group and starts to process service traffic.
-The instance status is changed from Enabled to Removing from AS group when any of the following occurs:- You manually decrease the expected number of instances of the AS group.
- The system automatically removes instances in a scaling action.
- 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 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.
Removing from AS group
+Enabled
(Optional) Disassociate the instance from the load balancing listener.
+None
When trigger condition 3 is met, the AS group starts to reduce resources and disassociate the instance from the load balancing listener.
+The instance is added to the AS group and starts to process service traffic.
+N/A
Remove the instance.
+Removing from AS group
After the instances are unbound from the load balancing listener, they are removed from the AS group.
+(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.
+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.
Removed
+Removing from AS group
None
+Remove the instance.
The instance lifecycle in the AS group ends.
+After the instance is unbound from the load balancing listener, it is removed from the AS group.
None
+- 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.
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.-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, Removing from AS group statuses, and is finally removed from the AS group.
-If you have added a lifecycle hook to the AS group, the instance statues 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. --Under trigger conditions 2, 4, 6, or 8, the system automatically changes the instance status. -Table 2 Instance statuses Status
+Under trigger condition 2, 4, 6, or 8, the system automatically changes the instance status.
+ +-Table 2 Instance statuses Status
Sub-status
+Sub-status
Status Description
+Status Description
Trigger Description
+Trigger Description
Initial
+Initial
None
+None
The instance has not been added to the AS group.
+The instance has not been added to the AS group.
The instance status is changed to Adding to AS group when either of the following occurs:- You manually increase the expected number of instances of an AS group.
- The system automatically adds instances to the AS group in a scaling action.
- You manually add instances to the AS group.
N/A
+Adding to AS group
+Add the instance.
+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.
Adding to AS group
+Wait (Adding to AS group)
Add an instance.
+None
When trigger condition 1 is met, AS adds the instance to expand the AS group capacity.
+The lifecycle hook suspends the instance that is being added to the AS group and puts the instance into a wait status.
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 waiting state.
-The instance status is changed from Wait (Adding to AS group) to Adding to AS group when either of the following operations is performed:- The default callback action is performed.
- You manually perform the callback action.
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.
Adding to AS group
- +Adding to AS group
+(Optional) Associate the instance with a load balancing listener.
+(Optional) Associate the instance with a load balancing listener.
When trigger condition 3 is met, AS associates the instance with the load balancing listener.
+When trigger condition 3 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.
-The instance status is changed from Enabled to Removing from AS group when any of the following occurs:- You manually decrease the expected number of instances of an AS group.
- The system automatically removes instances in a scaling action.
- A health check shows that the instance is unhealthy after being enabled, and the system removes it from the AS group.
- You manually remove an instance from an AS group.
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.
Removing from AS group
+Enabled
(Optional) Disassociate the instance from the load balancing listener.
+None
When trigger condition 5 is met, the AS group starts to reduce resources and disassociate the instance from the load balancing listener.
+The instance is added to the AS group and starts to process service traffic.
Wait (Removing from AS group)
-None
-The lifecycle hook suspends the instance that is being removed from the AS group and sets the instance to be in waiting state.
-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 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.
Removing from AS group
+Removing from AS group
Remove the instance.
+(Optional) Disassociate the instance from the load balancing listener.
When trigger condition 7 is met, AS removes 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.
Removed
+Wait (Removing from AS group)
None
+None
The instance lifecycle in the AS group ends.
+The lifecycle hook suspends the instance that is being removed from the AS group and puts the instance into a wait status.
None
+- The default callback action is performed.
- You manually perform the callback action.
Removing from AS group
+Remove the instance.
+When trigger condition 7 is met, AS removes the instance from the AS group.
+- 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.
diff --git a/docs/as/umn/as_pro_0003.html b/docs/as/umn/as_pro_0003.html index 5b065a3e..b8c9b8c0 100644 --- a/docs/as/umn/as_pro_0003.html +++ b/docs/as/umn/as_pro_0003.html @@ -4,8 +4,8 @@-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.
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 with 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 with the context of previous transactions.
+ - 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.
- 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.
- 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.
diff --git a/docs/as/umn/as_pro_0006.html b/docs/as/umn/as_pro_0006.html index 15eac0ec..93c32178 100644 --- a/docs/as/umn/as_pro_0006.html +++ b/docs/as/umn/as_pro_0006.html @@ -7,77 +7,77 @@-Table 1 Related services Service
Description
+Description
Interaction
+Interaction
Reference
+Reference
Elastic Load Balancing (ELB)
After ELB is configured, AS automatically associates ECS instances to a load balancer listener when adding ECSs, and unbinds them when removing the instances.
+After ELB is configured, AS automatically associates ECS instances to a load balancer listener when adding ECSs, and unbinds them when removing the instances.
For AS to work with ELB, the AS group and load balancer must be in the same VPC.
AS distributes traffic to all ECSs in an AS group.
+ELB distributes traffic to all ECSs in an AS group.
+ 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 condition specified in Cloud Eye is met.
AS scales resources based on ECS instance status monitored by Cloud Eye.
+AS scales resources based on ECS instance status monitored by Cloud Eye.
+ ECS
ECS instances added in a scaling action can be managed and maintained on the ECS console.
+ECS instances added in a scaling action can be managed and maintained on the ECS console.
AS automatically adjusts the number of ECS instances.
+AS automatically adjusts the number of ECS instances.
+ Virtual Private Cloud (VPC)
AS automatically adjusts the bandwidths of EIPs assigned in VPCs and also shared bandwidths.
+AS automatically adjusts the bandwidths of EIPs assigned in VPCs and also shared bandwidths.
AS automatically adjusts the bandwidth.
+AS automatically adjusts the bandwidth.
+ Cloud Trace Service (CTS)
With CTS, you can record AS operation logs for view, audit, and backtracking.
+With CTS, you can record AS operation logs for viewing, auditing, and backtracking.
Log audit
+Log audit
+ Tag Management Service (TMS)
If you have multiple resources of the same type, TMS enables you to manage these resources more easily.
+If you have multiple resources of the same type, TMS enables you to manage these resources more easily.
Tags
+Tags
+ Relational Database Service (RDS)
The prerequisites for directly accessing an RDS DB instance from a scaled instance are as follows:
+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.
+The scaled instances can access RDS DB instances.
Connecting to a DB Instance Through a Private Network
+Connecting to an MySQL DB Instance Through a Private Network
Permissions Management
++If you need to assign different permissions to employees in your enterprise to access your AS resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you securely access to your resources.
+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.
+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.
+ ++
+Table 1 System-defined permissions supported by AS Policy Name
+Description
+Category
+Dependency
+AutoScaling FullAccess
+All operation permissions on all AS resources
+System-defined policy
+None
+AutoScaling ReadOnlyAccess
+Read-only permissions on all AS resources
+System-defined policy
+None
+AutoScaling Administrator
+All operation permissions on all AS resources
+System role
+The ELB Administrator, CES Administrator, Server Administrator, and Tenant Administrator roles need to be assigned in the same project.
+Table 2 lists the common operations supported by each system-defined policy of AS. Select the policies as required.
+ ++
+Table 2 Common operations supported by each system-defined policy of AS Operation
+AutoScaling FullAccess
+AutoScaling ReadOnlyAccess
+AutoScaling Administrator
+Creating an AS group
+√
+x
+√
+Modifying an AS group
+√
+x
+√
+Querying details about an AS group
+√
+√
+√
+Deleting an AS group
+√
+x
+√
+Creating an AS configuration
+√
+x
+√
+Creating an AS policy
+√
+x
+√
+Creating a bandwidth scaling policy
+√
+x
+√
+
++ diff --git a/docs/as/umn/as_qs_0005.html b/docs/as/umn/as_qs_0005.html index 42ab5008..7e9de5a1 100644 --- a/docs/as/umn/as_qs_0005.html +++ b/docs/as/umn/as_qs_0005.html @@ -24,7 +24,7 @@++Parent topic: Service Overview+AZ
An AZ is a physical location where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network.
-- If you require high availability, buy servers in difference AZs.
- If you require low network latency, buy servers in the same AZ.
- 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
@@ -42,7 +42,7 @@Specifies the maximum number of ECS instances in an AS group.
0
+1
Expected Instances
@@ -57,7 +57,7 @@Specifies the minimum number of ECS instances in an AS group.
1
+0
VPC
@@ -77,13 +77,13 @@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 fault tolerance of your applications and expands application service capabilities.
+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.
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 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.
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 as 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.
- 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.
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 Instance and Creating an AS Configuration from a New Specifications Template.
- 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_0171188722.jpg b/docs/as/umn/en-us_image_0171188722.jpg new file mode 100644 index 00000000..083e80a1 Binary files /dev/null and b/docs/as/umn/en-us_image_0171188722.jpg differ diff --git a/docs/as/umn/en-us_topic_0042018361.html b/docs/as/umn/en-us_topic_0042018361.html index 009dac85..7e76ee63 100644 --- a/docs/as/umn/en-us_topic_0042018361.html +++ b/docs/as/umn/en-us_topic_0042018361.html @@ -14,6 +14,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.
- AS and Other Services
+ - Permissions Management
+ - User Permissions
- Basic Concepts
diff --git a/docs/as/umn/en-us_topic_0042018368.html b/docs/as/umn/en-us_topic_0042018368.html index 266df476..c39a573e 100644 --- a/docs/as/umn/en-us_topic_0042018368.html +++ b/docs/as/umn/en-us_topic_0042018368.html @@ -9,7 +9,7 @@- 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.
- 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:
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
@@ -29,7 +29,7 @@AZ
An AZ is a physical location where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network.
-- If you require high availability, buy servers in difference AZs.
- If you require low network latency, buy servers in the same AZ.
- 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
@@ -82,13 +82,13 @@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 fault tolerance of your applications and expands application service capabilities.
+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.
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.
- 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.
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 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.
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.
- 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.
N/A
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
@@ -154,7 +154,7 @@Tag
If you have many resources of the same type, you can use tags to more easily manage your resources. You can identify specified resources quickly using the tags allocated to them.
+If you have many resources of the same type, you can use tags to manage your resources. You can identify specified resources quickly using the tags allocated to them.
Each tag contains a key and a value. You can specify the key and value for each tag.
- Key
- The key must be specified.
- The key must be unique to the AS group.
- The key can include up to 36 characters. It can include digits, letters, underscores (_), and hyphens (-).
- 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 (-).
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.
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 set 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.
+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.
AZs in the same region can communicate with each other over an intranet, but AZs in different regions cannot.
-Cloud data centers are deployed in locations around the world, including Europe and Asia, 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 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.
diff --git a/docs/as/umn/en-us_topic_0042018383.html b/docs/as/umn/en-us_topic_0042018383.html index 4d541ae8..7abc9b78 100644 --- a/docs/as/umn/en-us_topic_0042018383.html +++ b/docs/as/umn/en-us_topic_0042018383.html @@ -1,14 +1,14 @@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.
What Is Auto Scaling?
-AS Introduction
Auto Scaling (AS) helps you automatically scale Elastic Cloud Server (ECS) and bandwidth resources to keep up with changes in demand based on pre-configured AS policies. It allows you to add ECS instances or increase bandwidths to handle increases in load and also save money by removing resources that are sitting idle.
+AS Introduction
Auto Scaling (AS) helps you automatically scale Elastic Cloud Server (ECS) and bandwidth resources to keep up with changes in demand based on pre-configured AS policies. It allows you to add ECS instances or increase bandwidths to handle load increases and also save money by removing resources that are sitting idle.
Architecture
AS allows you to scale ECS instances and bandwidths.
-- Scaling control: You can configure AS policies, configure metric thresholds, and schedule when different scaling actions are taken. AS will trigger scaling actions on a repeating schedule, at a specific time, or when the configured thresholds are reached.
- Policy configuration: You can configure alarm-based, scheduled, and periodic policies as needed.
- Alarm-based policies: You can configure scaling actions to be taken when alarm metrics such as vCPU, memory, disk, and inbound traffic reaches the thresholds.
- Scheduled policies: You can schedule scaling actions to be taken at a specific time.
- Periodic policies: You can configure scaling actions to be taken at scheduled intervals, a specific time, or within a particular time range.
- When Cloud Eye generates an alarm for a monitoring metric, for example, CPU usage, AS automatically increases or decreases the number of instances in the AS group or the bandwidths.
- When the configured triggering time arrives, a scaling action is triggered to increase or decrease the number of ECS instances or the bandwidths.
- Scaling control: You can configure AS policies, configure metric thresholds, and schedule when different scaling actions are taken. AS will trigger scaling actions on a repeating schedule, at a specific time, or when the configured thresholds are reached.
- Policy configuration: You can configure alarm-based, scheduled, and periodic policies as needed.
- Alarm-based policies: You can configure scaling actions to be taken when alarm metrics such as vCPU, memory, disk, and inbound traffic reach the thresholds.
- Scheduled policies: You can schedule scaling actions to be taken at a specific time.
- Periodic policies: You can configure scaling actions to be taken at scheduled intervals, at specific time, or within a particular time range.
- When Cloud Eye generates an alarm for a monitoring metric, for example, CPU usage, AS automatically increases or decreases the number of instances in the AS group or the bandwidths.
- When the configured triggering time arrives, a scaling action is triggered to increase or decrease the number of ECS instances or the bandwidths.
Figure 1 AS architecture
diff --git a/docs/as/umn/en-us_topic_0044453521.html b/docs/as/umn/en-us_topic_0044453521.html index c1f03580..a286e73c 100644 --- a/docs/as/umn/en-us_topic_0044453521.html +++ b/docs/as/umn/en-us_topic_0044453521.html @@ -8,7 +8,19 @@Accessing AS
The public cloud provides a web-based service management platform. You can access AS using HTTPS-compliant application programming interfaces (APIs) or the management console.
-- Calling APIs
Use this method if you are required to integrate AS on the public cloud into a third-party system for secondary development. For details, see Auto Scaling API Reference.
+- Calling APIs
Use this method if you are required to integrate AS on the public cloud into a third-party system for secondary development. For more information, see Auto Scaling API Reference.
- Management console
Use this method if you do not need to integrate AS with a third-party system.
After registering on the public cloud, log in to the management console and select Auto Scaling from the service list on the homepage.
- Calling APIs
- AS Group and Instance Monitoring
+ - Permissions Management
+
2022-09-06
+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:
+Redesigned the table structure in Instance Lifecycle.
+2022-09-06
The release incorporates the following changes:
Optimized keywords.
diff --git a/docs/as/umn/en-us_topic_0112331243.html b/docs/as/umn/en-us_topic_0112331243.html index efa19980..f4c3f86b 100644 --- a/docs/as/umn/en-us_topic_0112331243.html +++ b/docs/as/umn/en-us_topic_0112331243.html @@ -49,7 +49,7 @@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.
- - Consecutive Occurrences
Specifies the number of consecutive times, for example, one time, for triggering a scaling action during a monitoring period.
+ - Consecutive Occurrences
Specifies the number of consecutive periods in which the triggering condition is met for triggering a scaling action.
- 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. -
- After setting the parameters, click Create Now.
- After setting the parameters, click Create Now.
diff --git a/docs/as/umn/public_sys-resources/icon-arrowdn.gif b/docs/as/umn/public_sys-resources/icon-arrowdn.gif index 84eec9be..37942803 100644 Binary files a/docs/as/umn/public_sys-resources/icon-arrowdn.gif and b/docs/as/umn/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/as/umn/public_sys-resources/icon-arrowrt.gif b/docs/as/umn/public_sys-resources/icon-arrowrt.gif index 39583d16..6aaaa11c 100644 Binary files a/docs/as/umn/public_sys-resources/icon-arrowrt.gif and b/docs/as/umn/public_sys-resources/icon-arrowrt.gif differ
- Interval
- Click OK.
- System Disk
