Introduction to Alibaba Auto Scaling
The course is part of this learning path
Alibaba Auto Scaling automatically creates and releases ECS instances based on pre-defined rules in order to scale services to match demand. Furthermore, it can configure server load balancer and relational database service white lists, without any manual intervention.
In this course, you will learn about the Alibaba Auto Scaling service and how it operates. You will learn about the core concepts of the service, scaling groups, scaling configurations, and scaling rules (manual and automatic). For each section of the course, there are guided demonstrations from the Alibaba Cloud platform that you can follow along with, giving you the practical experience necessary to set up auto scaling on your own environment.
If you have any feedback relating to this course, feel free to contact us at email@example.com.
- Understand the core concepts and components of Alibaba Auto Scaling
- Learn how to create, modify, enable, disable, and delete a scaling group
- Learn how to create, modify and delete the scaling configuration that provides the virtual servers in the scaling group
- Understand the different types of scaling rules that are available
- Learn how to use manual and automatic scaling operations
This course is intended for anyone who wants to learn how to set up auto scaling in their Alibaba Cloud environments.
To get the most out of this course, you should already have a basic knowledge of Alibaba Cloud or another cloud vendor.
Welcome to session six, Autoscaling, manual scaling operations. In this session, we will cover manually executing scaling rules to add and remove ECS instances from a scaling group.
Manual scaling rules. You can manually execute a scaling rule given the following conditions. If a scaling group is active and no scaling activity is being executed for the scaling group, a rule will execute directly without waiting for any cool down times to expire. To manually start a scaling rule, select the rule from the scaling rules tab inside your scaling group and select the execute link.
So what happens if we add ECS instances using scaling rules? If the number of ECS instances to be added by the scaling rule plus the number of already existing ECS instances in the group exceeds the maximum count value, then the total new instances to be added will be adjusted down so that the maximum count value is not exceeded.
If the maximum count value has been reached and the scaling rule is executed to add more ECS instances, the operation will fail.
ECS instances from your existing ECS pool can also be manually added to a scaling group. Instances that are added manually are not associated with the active scaling configuration in the scaling group. And what happens if we want to remove ECS instances using scaling rules? ECS instance removal depends on the reclaim mode you chose for the scaling group. Instances will either be stopped if you chose shutdown and reclaim mode or there'll be released if you chose release mode. If a scaling group is active and no scaling activity is been executed for the scaling group, ECS instance removal will occur immediately without waiting for any cool down times to expire.
If the number of ECS instances you're going to remove from the scaling group will take the group below the minimum count value, then the total capacity is adjusted to the minimum count value.
If the minimum count value has been reached and a scaling rule is executed to remove more ECS instances, the operation will fail.
When a manually added ECS instance from your existing ECS pool is removed from a scaling group, the instance is not stopped or released.
That concludes this session. In the next session, I will demonstrate creating a simple manual scaling rule. I look forward to seeing you there.
David’s IT career started in 1990, when he took on the role of Database Administrator as a favor for his boss. He redirected his career into the Client Server side of Microsoft with NT4, and then progressed to Active Directory and each subsequent version of Microsoft Client/Server Operating Systems. In 2007 he joined QA as a Technical Trainer, and has delivered training in Server systems from 2003 to 2016 and Client systems from XP onwards. Currently, David is a Principal Technical Learning Specialist (Cloud), and delivers training in Azure Cloud Computing, specializing in Infrastructure Compute and Storage. David also delivers training in Microsoft PowerShell, and is qualified in the Alibaba Cloud Space.