Huawei Auto Scaling User Manual

Auto Scaling

User Guide

Issue	01
Date	2020-10-27

HUAWEI TECHNOLOGIES CO., LTD.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise c fi in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every ff has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Issue 01 (2020-10-27)

Auto Scaling
User Guide	Contents

Contents

1 AS Group....................................................................................................................................							1
1.1	Creating an AS Group............................................................................................................................................................						1
1.2	(Optional) Adding a Load Balancer to an AS Group..................................................................................................						5
1.3	Replacing AS		nfig	n in an AS Group..................................................................................................................			6
1.4	Enabling an AS Group............................................................................................................................................................						6
1.5	Disabling an AS Group..........................................................................................................................................................						7
1.6	Modifying an AS Group.........................................................................................................................................................						8
1.7	Deleting an AS Group............................................................................................................................................................						9
2 AS C n			n...................................................................................................................				10
2.1	Creating an AS		nfig	n...........................................................................................................................................			10
2.2	Using an Existing ECS to Create an AS nfig				n.............................................................................................		10
2.3	Using a New		c fic	n Template to Create an AS nfig		n...............................................................	14
2.4	Copying an AS		nfig	n...........................................................................................................................................			20
2.5	Deleting an AS		nfig	n...........................................................................................................................................			20
3 AS Policy..................................................................................................................................							21
3.1	Overview..................................................................................................................................................................................						21
3.2	Creating an AS Policy..........................................................................................................................................................						22
3.3	Managing AS Policies..........................................................................................................................................................						31
4 Scaling Action........................................................................................................................							33
4.1	Dynamically Expanding Resources..................................................................................................................................						33
4.2	Expanding Resources as Planned....................................................................................................................................						35
4.3	Manually Expanding Resources.......................................................................................................................................						36
4.4	nfig	ng an Instance Removal Policy......................................................................................................................					37
4.5	Viewing a Scaling Action....................................................................................................................................................						38
4.6	Managing Lifecycle Hooks.................................................................................................................................................						39
4.7	nfig	ng Instance Protection......................................................................................................................................					45
4.8	Standby Instance...................................................................................................................................................................						46
5 Bandwidth Scaling................................................................................................................							48
5.1	Creating a Bandwidth Scaling Policy..............................................................................................................................						48
5.2	Viewing Details About a Bandwidth Scaling Policy..................................................................................................						54
5.3	Managing a Bandwidth Scaling Policy..........................................................................................................................						55
Issue 01 (2020-10-27)				Copyright © Huawei Technologies Co., Ltd.			ii

Auto Scaling
User Guide		Contents
6 AS Group and Instance Monitoring...................................................................................		58
6.1	Health Check..........................................................................................................................................................................	58
6.2	nfig ng N fic n for an AS Group....................................................................................................................	59
6.3	Recording AS Resource Operations................................................................................................................................	60
6.4	Adding Tags to AS Groups and Instances.....................................................................................................................	63
6.5	Monitoring Metrics...............................................................................................................................................................	64
6.6	Viewing Monitoring Metrics..............................................................................................................................................	69
6.7	Setting Monitoring Alarm Rules......................................................................................................................................	70

Issue 01 (2020-10-27)

iii

Auto Scaling
User Guide	1 AS Group

1AS Group

1.1 Creating an AS Group

Scenarios

An AS group consists of a collection of instances 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. The


c nfig	AS policy automatically adds or deletes instances to or from an AS
group, or maintains a fix number of instances in an AS group.
When creating an AS group, specify an AS c		nfig	n for it. Additionally, add
one or more AS policies for the AS group.
Creating an AS group involves the c nfig		n of the maximum, minimum, and

expected numbers of instances and the associated load balancer.

Notes

ECS types supported by ff	n
must choose a proper AS c	nfig

the AZs used by the AS group.

AZs may vary. When creating an AS group, you n according to the ECS type supported by

● If the ECS type c fi in the AS c nfig n is supported by none of the AZs used by the AS group, the following situations will occur:

–If the AS group is disabled, it cannot be enabled.

–If the AS group is enabled, its status will become abnormal when instances are added to it.

● If the ECS type c fi in the AS c nfig n is supported only by certain AZs used by the AS group, the ECSs added by a scaling action are distributed only in the AZs supporting the ECS type. As a result, the instances in the AS group may not be evenly distributed.

Procedure

1.Log in to the management console.

Issue 01 (2020-10-27)

Auto Scaling
User Guide	1 AS Group

2.Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.

3.Click Create AS Group.

4.Set parameters, such as Name, Max. Instances, Min. Instances, and

Expected Instances. Table 1-1 describes the key parameters to be c nfig

Table 1-1 AS group parameters

Paramet	Description			Example
er				Value

Region	A region is where an AS group resides.			N/A

AZ	An AZ is a physical region where resources use			N/A
	independent power supply and networks. AZs are
	physically isolated but interconnected through an
	internal network.

Multi-AZ	This parameter can be set to Load-balanced or			Load-
Extensio	Sequenced.			balanced
n Policy	● Load-balanced: When expanding ECSs in an
	● Load-balanced: When expanding ECSs in an
	AS group, the system preferentially distributes
	ECSs evenly among AZs used by the AS group.
	If it fails in the target AZ, it automatically
	selects another AZ based on the sequenced
	policy.
	● Sequenced: When expanding ECSs in an AS
	group, the system selects the target AZ based
	on the order in which AZs are selected.
	NOTE
	This parameter needs to be c nfig		when two or
	more AZs are selected.

Name	c fi	the name of the AS group to be created.		N/A
	The name contains 1 to 64 characters and consists
	of only letters, digits, underscores (_), and
	hyphens (-).

Max.	c fi	the maximum number of ECS instances		1
Instance	in an AS group.
s

Expected	c fi	the expected number of ECS instances in		0
Instance	an AS group.
s	After an AS group is created, you can change this
	After an AS group is created, you can change this
	value, which will trigger a scaling action.

Min.	c fi	the minimum number of ECS instances in		0
Instance	an AS group.
s

Issue 01 (2020-10-27)

Auto Scaling
User Guide								1 AS Group

	Paramet	Description						Example
	er							Value
	AS	c fi	the required AS c			nfig	n for the AS	N/A
	c nfig	group. An AS c nfig			n	fin	the
	n	c fic	n	of the ECSs to be added to an AS
		group. The		c fic	n include the ECS image
		and system disk size. You need to create the
		required AS c		nfig	n before creating an AS
		group.

	VPC	Provides a network for your ECSs.						N/A
		All ECSs in an AS group belong to the same VPC.

	Subnet	You can select a maximum of fi					subnets. The AS	N/A
		group automatically binds all NICs to the created
		ECSs. The fi		subnet is used by the primary NIC
		of the ECS by default, and other subnets are used
		by extension NICs of the ECS.

	Load	This parameter is optional. A load balancer						N/A
	Balancin	automatically distributes access					ffic to all

ginstances in an AS group to balance their service load. It enables higher levels of fault tolerance in your applications and expands application service capabilities.

NOTE

●Up to six 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 faulty, AS will replace the faulty instance with a functional one.

If you select Enhanced load balancerIf you select

Elastic load balancer, c nfig the following parameters:

●Load Balancer

●Backend ECS Group

● Backend Port:	c fi	the port on which a
backend ECS listens for		ffic

●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 Balance User Guide.

Issue 01 (2020-10-27)

Auto Scaling
User Guide							1 AS Group

	Paramet	Description					Example
	er						Value
	Instance	c fi the priority for removing instances from					Oldest
	Removal	an AS group. If	c fi	conditions are met,			instance
	Policy	scaling actions are triggered to remove instances.					created
		AS supports the following instance removal					from oldest
		policies:					AS
		● Oldest instance created from oldest AS					c nfig
		● Oldest instance created from oldest AS					n
		n	n: The oldest instance created				n
		n	n: The oldest instance created
		based on the oldest c		nfig	n is removed
		from the AS group fi
		● Newest instance created from oldest AS
		n	n: The latest instance created
		based on the oldest c		nfig	n is removed
		from the AS group fi
		● Oldest instance: The oldest instance is
		removed from the AS group fi
		● Newest instance: The latest instance is
		removed from the AS group fi
		NOTE
		● Removing instances will preferentially ensure that
		the remaining instances are load balanced in AZs.
		● A manually added ECS is removed in the lowest
		priority. AS does not delete a manually added ECS
		when removing it. If multiple manually added ECSs
		must be removed, AS preferentially removes the
		earliest-added ECS.

	EIP	If EIP has been selected in an AS c			nfig	n for	N/A
		an AS group, an EIP is automatically bound to the
		ECS added by a scaling action to the AS group. If
		you select Release, the EIP bound to an ECS is
		released when the ECS is removed from the AS
		group. Otherwise, the system unbinds the EIP
		from the ECS, but does not release it when the
		ECS is removed from the AS group.

Issue 01 (2020-10-27)

Auto Scaling
User Guide							1 AS Group

	Paramet	Description					Example
	er						Value
	Health	When a health check detects a faulty ECS, AS					N/A
	Check	removes the faulty ECS from the AS group and
	Method	adds a new one. The health check is implemented
		using any of the following methods:
		● ECS health check: checks ECS running status. If
		an ECS is stopped or deleted, it is considered as
		abnormal. This method is selected by default.
		Using this method, the AS group periodically
		determines the running status of each ECS
		based on the health check result. If the health
		check result shows that an ECS is faulty, AS
		removes the ECS 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.

	Advance	nfig	n fic	n	and tags.		-
	d	You can select Do not			n	or C n
	Settings	You can select Do not			n	or C n
	Settings	now.
		now.

5.	Click Next. On the Add AS C n					n page, you can choose to use an
	existing AS c nfig		n or create one. For details, see .
6. Click Create Now.
7.	Check the AS group and AS c			nfig		n information. Then click Submit.

8.(Optional) Add AS policies. For details, see Creating an AS Policy.

1.2(Optional) Adding a Load Balancer to an AS Group

Elastic Load Balance (ELB) automatically distributes incoming ffic across multiple backend servers based on c nfig forwarding policies. ELB expands the service capabilities of applications and improves their availability by eliminating single points of failure (SPOFs).

If ELB functions are required, perform the operations provided in this section to add a load balancer to your AS group. The load balancer added to an AS group distributes application ffic to all instances in the AS group when an instance is added to or deleted from the AS group.

Only a created load balancer can be bound to an AS group, and the AS group and load balancer must be in the same VPC. For details about how to create a load balancer, see Elastic Load Balance User Guide. To add a load balancer for an AS group, perform the following operations:

● When creating an AS group, c nfig parameter Load Balancing to add a load balancer. For details, see Creating an AS Group.

Issue 01 (2020-10-27)

Auto Scaling
User Guide	1 AS Group

●If an AS group has no scaling action ongoing, modify parameter Load Balancing to add a load balancer. For details, see Modifying an AS Group.

1.3 Replacing AS C n			n in an AS Group
Scenarios
	If you need to change the ECS		c fic n in an AS group, you need to change
	the AS c nfig	n
ff	Time of New AS C n		n
	If the AS group has an in-progress scaling action, the new AS c nfig			n will
	take ff c only for instances scaled in later scaling actions.

For example, the current AS c		nfig
new AS c nfig	n is	n
scaling action is still	n	.

n of the AS group is	n	, and the
B. The instance c nfig	n in the current


The instance c nfig	n will change to		n	B in the next scaling action.
Figure 1-1 Changing the AS c nfig		n

Procedure

1.Log in to the management console.

2.Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.

3.Click the name of the target AS group. On the Basic Information page, click

Change C n

n to the right of C n

n Name.

You can also locate the row containing the target AS group and choose More

> Change C n n in the Operation column.

4. In the displayed Change AS C n		n dialog box, select another AS
c nfig	n to be used by the AS group.

5.Click OK.

1.4Enabling an AS Group

Scenarios

You can enable an AS group to automatically increase or decrease instances.

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

Issue 01 (2020-10-27)

Auto Scaling
User Guide	1 AS Group
instances if the number of instances in the AS group is ff	n 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 c nfig	n to an AS group,
the AS group is automatically enabled.

Enabling an AS Group

1.Log in to the management console.

2.Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.

3.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.

4.In the Enable AS Group dialog box, click Yes.

Forcibly Enabling an AS Group

1.Log in to the management console.

2.Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.

3.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.

4.In the Forcibly Enable AS Group dialog box, click Yes.

1.5Disabling an AS Group

Scenarios

When you are required to stop an instance in an AS group for c nfig n or upgrade, disable the AS group before performing the operation. This prevents the instance from being deleted in a health check. When the instance status restores, enable the AS group again.

If a scaling action, for example, creating an instance or EVS disk, consistently fails (the failure cause can be viewed on the Elastic Cloud Server page) and retries in an AS group, use either of the following methods to stop the retry:

●Disable the AS group. Then, the scaling action that is being performed fails

and will not retry. Enable the AS group again when the environment recovers or after replacing the AS c nfig n

●Disable the AS group and change the expected number of instances to the number of existing instances. After the scaling action fails and ends, the scaling action will not retry.

Issue 01 (2020-10-27)

Auto Scaling
User Guide	1 AS Group
	After an AS group is disabled, its status changes to Disabled. AS does not
	automatically trigger any scaling actions for a Disabled AS group. When an AS
	group has an in-progress scaling action, the scaling action does not stop
	immediately after the AS group is disabled.
	You can disable an AS group when its status is Enabled or Abnormal.

Procedure

1.Log in to the management console.

2.Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.

3.In the AS group list, locate the row containing the target AS group and click Disable in the Operation column. You can also click the AS group name and then Disable to the right of Status on the Basic Information page to disable the AS group.

4.In the Disable AS Group dialog box, click Yes.

1.6Modifying an AS Group

Scenarios

You can modify an AS group as needed. The values of the following parameters can be changed: Name, Max. Instances, Min. Instances, Expected Instances, Health Check Method, Health Check Interval, Instance Removal Policy.

NOTE

Changing the value of Expected Instances will trigger a scaling action. Then, AS automatically increases or decreases the number of instances to the value of Expected Instances.

If the AS group is not enabled, contains no instance, and has no scaling action

ongoing, you can modify Subnet c nfig	n	If an AS group has no scaling
action ongoing, you can modify its AZ and ELB c		nfig	n

Procedure

1.Log in to the management console.

2.Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.

3.In the AS group list, locate the row containing the target AS group, click the AS group name to switch to the Basic Information page, and click Modify in the upper right corner.

You can also locate the row containing the target AS group and choose More

> Modify in the Operation column.

4.In the Modify AS Group dialog box, modify related data, for example, the expected number of instances.

5.Click OK.

Issue 01 (2020-10-27)

Auto Scaling
User Guide	1 AS Group

1.7 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	c fi period of time, you are
advised to disable it but not delete it.

●For an AS group that has an instance or ongoing scaling action, if you attempt to forcibly delete the AS group and remove and delete the instances in the AS group, the AS group enters the deleting state, rejects new scaling requests, waits until the ongoing scaling action completes, and removes all instances from the AS group. Then, the AS group is automatically deleted. Manually added instances are only removed out of the AS group, while the instances automatically created in a scaling action are removed and deleted. During the preceding process, you are not allowed to perform other operations in the AS group.

●After an AS group is deleted, its AS policies and the alarm rules generated

based on the AS policies c nfig	for the AS group will be automatically
deleted.

Procedure

1.Log in to the management console.

2.Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.

3.In the AS group list, locate the row containing the target AS group and choose More > Delete in the Operation column.

4.In the displayed Delete AS Group dialog box, click Yes.

Issue 01 (2020-10-27)

Auto Scaling
User Guide	2 AS nfig	n

2AS C n n

2.1 Creating an AS C n							n
An AS c		nfig	n	fin	the		c fic n of the ECSs to be added to an AS
group. The c fic				n include the ECS image and system disk size.
Scenarios
● When you create an AS group, create an AS c								nfig	n or use an existing
	AS c	nfig	n
● Create the required AS c						nfig	n on the Instance Scaling page.
● Change the AS c				nfig		n on the AS group details page.
Methods
●	Using an existing ECS to create an AS c nfig							n
	When you create an AS c					nfig	n using an existing ECS, the vCPU,
	memory, image, disk, and ECS type are the same as those of the selected ECS
	by default. For details, see Using an Existing ECS to Create an AS
	C n	n.
●	Using a new		c fic		n	template to create an AS c			nfig	n
	If you have special requirements on the ECSs for resource expansion, use a
	new	c fic	n template to create the AS c					nfig	n For details, see
	Using a New					n Template to Create an AS C n				n.
2.2 Using an Existing ECS to Create an AS
C n	n
Scenarios
You can use an existing ECS to rapidly create an AS c nfig									n	In such a case,
the parameter settings, such as the vCPUs, memory, image, disk, and ECS type in
the AS c		nfig	n are the same as those of the selected ECS by default.

Issue 01 (2020-10-27)

Auto Scaling
User Guide	2 AS nfig	n

Procedure

1.Log in to the management console.

2.Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.

3.	Click Create AS C n				n.
4.	Set the parameters for the AS c nfig						n	Table 2-1 lists the AS
	c nfig	n parameters.
	Table 2-1 AS c		nfig		n parameters

	Parameter		Description							Example
										Value
	Region		A region is where an AS c				nfig		n resides.	N/A

	Name			c fi	the name of an AS c nfig				n	N/A

	nfig		Select Use			n	of an existing ECS			Use
	n Template		and click Select ECS.							c fic	n
			The ECS type, vCPUs, memory, image, and							of an
			The ECS type, vCPUs, memory, image, and							existing ECS
			disk information in the AS c					nfig	n are	existing ECS
			disk information in the AS c					nfig	n are
			the same as those of the selected ECS by
			default.

	EIP		An EIP is a static public IP address bound to							Automaticall
			an ECS in a VPC. Using the EIP, the ECS							y assign
			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. The
				bandwidth size is c		nfig		b
			NOTE
				If you select Automatically assign, you need to
				specify Type, Bandwidth Type, Billed By, and
				Bandwidth.

Issue 01 (2020-10-27)

Auto Scaling
User Guide							2 AS nfig		n

	Parameter	Description						Example
								Value
	Bandwidth	You can select Dedicated or Shared.						Shared
	Type	● Dedicated: The bandwidth can be used by
		● Dedicated: The bandwidth can be used by
			only one EIP.
		● Shared: The bandwidth can be used by
			multiple EIPs.
		NOTE
			● This parameter is available only when EIP is set
				to Automatically assign.
			● If you select Dedicated, you can select
				Bandwidth or	ffi	for Billed By.
			● The shared bandwidth can be billed only by
				bandwidth. You can select a shared bandwidth
				to which the EIP is to be added.

	Login Mode	An ECS can be authorized using a key pair or						Admin@123
		a password.
		●	Key pair
			In this mode, keys are used for
			authenticating the users who attempt to
			log in to target ECSs. If you select this
			mode, create or import a key pair on the
			Key Pair page.
			NOTE
				If you use an existing key, make sure that you
				have saved the key fi		locally. Otherwise,
				logging in to the ECS will fail.
		●	Password
			In this mode, the initial password of user
			root (for Linux) or user Administrator (for
			Windows) is used for authentication. You
			can log in to an ECS using the username
			and its initial password.

	Advanced	This allows you to c			nfig		User Data	N/A
	Settings	Injection and ECS Group.
		You can select Do not				n	or
		C n		now.

Issue 01 (2020-10-27)

Auto Scaling
User Guide				2 AS nfig	n

	Parameter	Description		Example
				Value
	User Data	Enables the ECS to automatically inject user		-
	Injection	data when the ECS starts for the fi time.
		This c nfig	n is optional. After this
		function is enabled, the ECS automatically
		injects user data upon its fi startup.
		For details, see Elastic Cloud Server User
		Guide.

The following methods are available:

●As text: allows you to enter the user data in the text box below.

	● As	: allows you to inject script fi or
	other fi when you create an ECS. If you
	select As		, the system automatically
	injects the fi		into a		c fi	directory
	when creating an ECS.
	– For Linux, specify the path for storing
		the injected fi		for example /etc/
		foo.txt.
	–	For Windows, the injected fi				is
		automatically stored in the root
		directory of disk C. You only need to
		specify the fi		name, such as foo. The
		fi name can contain only letters and
		digits.
	NOTE
	● For Linux, if you use the password
		authentication mode, the user data injection
		function is unavailable.
	● If the selected image does not support user
		data injection, the user data injection
		function is unavailable.

ECS Group	An ECS group allows you to create ECSs on						N/A
	ff	n hosts, thereby improving service
	reliability.

5.	Click Create Now.
6.	Click Create Now.
7.	If you want to use the newly created AS c	nfig	n add it to the AS group.
	For details, see Replacing AS C n	n in an AS Group.

8.(Optional) Enable the AS group.

If the AS group is in Disabled state, enable it. For details, see Enabling an AS Group.

Issue 01 (2020-10-27)

Auto Scaling
User Guide	2 AS nfig	n

2.3 Using a New		n Template to Create an
AS C n	n

Scenarios

If you have special requirements on the ECSs for resource expansion, use a new

c fic	n template to create the AS c nfig		n In such a case, ECSs
meeting	c fic	n of the template will be added to the AS group in scaling
actions.

Procedure

1.Log in to the management console.

2.Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.

3. Click Create AS C n				n.
4. Set the parameters for the AS c					nfig	n Table 2-2 lists the AS
	c nfig	n parameters.
	Table 2-2 AS c		nfig	n parameters

	Parameter		Description					Example Value

	Region		A region is where an AS c			nfig	n	N/A
			resides.

	Name		c fi	the name of the AS				N/A
			c nfig	n to be created.

	nfig		Select Create a new				n	Create a new
	n Template		template.					c fic n
			If this option is selected, c			nfig		template
			If this option is selected, c			nfig
			parameters, such as the vCPUs, memory,
			image, disk, and ECS type, to create a
			new AS c nfig		n

	CPU		The following two types of CPU					x86
	Architecture		architectures are available:
			● x86: The x86-based CPU architecture
			uses Complex Instruction Set
			Computing (CISC).
			● Kunpeng: The Kunpeng-based CPU
			architecture uses Reduced Instruction
			Set Computing (RISC).

Issue 01 (2020-10-27)

Auto Scaling
User Guide								2 AS nfig	n

	Parameter		Description					Example Value

	c fic	n	The public cloud provides various ECS					Memory-
			types for		ff n	application scenarios.		optimized ECS
			For more information, see Elastic Cloud
			Server User Guide.
				nfig	the ECS	c fic	n
			including vCPUs, memory, image type,
			and disk, according to the ECS type.

	Image		●	Public image				Public image
				A public image is a standard, widely
				used image. It contains an OS and
				preinstalled public applications and is
				available to all users. You can
				c nfig	the applications or software
				in the public image as needed.
			●	Private image
				A private image is an image available
				only to the user who created it. It
				contains an OS, preinstalled public
				applications, and the user's private
				applications. Using a private image to
				create ECSs removes the need to
				c nfig	multiple ECSs repeatedly.
			●	Shared image
				A shared image is a private image
				shared by another public cloud user.

Issue 01 (2020-10-27)

Auto Scaling
User Guide				2 AS nfig	n

	Parameter	Description		Example Value

	Disk	Includes system disks and data disks.		Common I/O for
		●	System Disk	System Disk
		●	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 a full-ECS image is used, the system
			disk is restored using the disk backup.
			On the console, you can only change
			the volume type and size. In addition,
			the volume cannot be smaller than
			the disk backup.
		●	Data Disk
			You can create multiple data disks for
			an ECS. In addition, you can specify a
			data disk image for exporting data.
			If the image you selected is of the
			full-ECS image type, you can change
			the volume type and size and
			encryption attributes of the data disk
			restored using the disk backup. Ensure
			that the volume size is greater than
			or equal to the disk backup size, and
			the encryption attributes can be
			m fi only if the disk backup of
			the full-ECS image locates in the
			target region.

	Security	Controls ECS access within or between		N/A
	Group	security groups by fin ng access rules.
		ECSs added to a security group are
		protected by the access rules you fin

Issue 01 (2020-10-27)

Auto Scaling
User Guide				2 AS nfig	n

	Parameter	Description		Example Value

	EIP	An EIP is a static public IP address bound		Automatically
		to an ECS in a VPC. Using the EIP, the		assign
		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.
			NOTE
			If you select Automatically assign, you
			need to specify Type, Billed By, and
			Bandwidth.

	Bandwidth	You can select Dedicated or Shared.		Shared
		● Dedicated: The bandwidth can be
			used by only one EIP.
		● Shared: The bandwidth can be used
			by multiple EIPs.
		NOTE
			● This parameter is available only when EIP
			is set to Automatically assign.
			● If you select Dedicated, you can select
			Bandwidth or ffi for Billed By.
			● The shared bandwidth can be billed only
			by bandwidth. You can select a shared
			bandwidth to which the EIP is to be
			added.

Issue 01 (2020-10-27)

Auto Scaling
User Guide						2 AS nfig	n

	Parameter	Description				Example Value

	Login Mode	An ECS can be authorized using a key				Admin@123
		pair or a password.
		●	Key pair
			In this mode, keys are used for
			authenticating the users who attempt
			to log in to target ECSs. If you select
			this mode, create or import a key pair
			on the Key Pair page.
			NOTE
				If you use an existing key, make sure that
				you have saved the key fi locally.
				Otherwise, logging in to the ECS will fail.
		●	Password
			In this mode, the initial password of
			user root (for Linux) or user
			Administrator (for Windows) is used
			for authentication. You can log in to
			an ECS using the username and its
			initial password.

	Advanced	This parameter allows you to c			nfig	N/A
	Settings	ECS Group and User Data Injection.
		You can select Do not n			or
		C n		now.

Issue 01 (2020-10-27)

Auto Scaling
User Guide					2 AS nfig	n

	Parameter	Description			Example Value

	User Data	Enables the ECS to automatically inject			-
	Injection	user data when the ECS starts for the
		fi	time. This c nfig	n is optional.
		After this function is enabled, the ECS
		automatically injects user data upon its
		fi	startup.

For details, see Elastic Cloud Server

User Guide.

The following methods are available:

●As text: allows you to enter the user data in the text box below.

●As : allows you to inject script fi

		or other fi		when you create an ECS.
		If you select As			, the system
		automatically injects the fi				into a
		c fi	directory when creating an
		ECS.
		– For Linux, specify the path for
		storing the injected fi				for
		example /etc/foo.txt.
		– For Windows, the injected fi					is
		automatically stored in the root
		directory of disk C. You only need
		to specify the fi			name, such as
		foo. The fi		name can contain
		only letters and digits.
		NOTE
		● For Linux, if you use the password
		authentication mode, the user data
		injection function is unavailable.
		● If the selected image does not support
		user data injection, the user data
		injection function is unavailable.

	ECS Group	An ECS group allows you to create ECSs						N/A
		on ff n	hosts, thereby improving
		service reliability.

5. Click Create Now. The system displays a message indicating that the AS
	c nfig	n is successfully created.
6. If you want to use the newly created AS c nfig							n add it to the AS group.
	For details, see Replacing AS C n				n in an AS Group.

Issue 01 (2020-10-27)

+ 51 hidden pages

Huawei Auto Scaling User Manual

Contents

1 AS Group

1.1 Creating an AS Group

1.2(Optional) Adding a Load Balancer to an AS Group

1.4Enabling an AS Group

1.5Disabling an AS Group

1.6Modifying an AS Group

1.7 Deleting an AS Group