Introduction to Alibaba Auto Scaling
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.
Hello, and welcome to this demonstration on creating a scaling group. From within the Alibaba console, I'm gonna select the menu system on the left-hand side and find auto scaling. Now, this takes me into the auto scaling homepage where I have two options. I can either create a scaling group directly from the home page, or I can select scaling groups on the left-hand side and create a scaling group from here.
If I create the scaling group from here, you see I have the option of a launch template, select an existing instance, or create from scratch. I'm gonna select the create from scratch. I need to give my scaling group a name, I'm just gonna call it test. And I then have the option of putting tags in.
Now, tags are just to keep her system to allow you to filter and group resources together. The next thing I need to choose is the instance removal policy. And these are the ECS instances that either the oldest ones that were put into the group or the latest ones that were put into the group when it comes to removing from the group. I have the option of suspending any processes if I want to set that up from here. So I can suppress things like scale out, scale in, health check, schedule tasks and event triggered tasks. This is an optional setting and can be edited afterwards.
I also have the option for setting up deletion protection so that the group cannot be accidentally deleted. I'm gonna leave that off. And health check for instances is set by default. This is so that if an unhealthy instance is found within the group, auto-scaling will automatically replace it with a healthy instance and remove the old machine.
I next get to set up the minimum number and maximum number of instances that are allowed in the group. I'll leave the default minimum at one, I'll change the maximum to five. And I can also optionally set up the expected number of instances. If I was to put a number in there, auto-scaling would try to average that number out all the time.
I then get to choose the default cool down time. The cool down time only works for event-driven tasks which means if I have a manual task that's triggered or a scheduled task that's triggered, it will override the cool down time. Next I get to choose the network type which in this case is only VPC. Next I get to set the multi-zone scaling policy.
Now, there's three options. There's priority, balanced and cost optimized. For the priority policy, the V switches are given a priority and the highest priority V switch is where the ECS instances will be created. In the balanced distribution policy, ECSs are distributed across different zones or balanced across the different zones and in a cost optimized policy, it's the cheapest zone where the ECS instances are created. I'm gonna choose the balanced distribution policy.
For the reclaim mode we have the option of release mode and shutdown and reclaim mode. I'll leave it at release in the release mode. Any ECS instances that are removed from the group are actually removed and deleted and their corresponding hard drives are deleted as well. If I was to choose shutdown and reclaim mode, the machines that are removed from the group would be shut down. There'll be no running costs. However, the discs would remain and storage costs would thus balance out.
I get next to choose the VPC. If I hit the dropdown list, I already have a virtual network running in London. So I'm gonna select that. And in London I have two switches. I've got a switch in zone B and a switch in zone A, so I'm gonna select those two. I also get to choose whether to associate a server load balancer instance, and also an RDS instance. These are optional. I can actually create new instances from here, but I'm not gonna set those up for the moment. I'm just gonna click okay.
Hit continue, and that will create my first scale group. If I want to edit the configuration, I can click on the edit link on the right-hand side. And from there, I can then change things like the instance numbers, I can change the cool down period, I can add or create switches if I require and also change the SLB instances and RDS instances from within here. Although it's worth noting, I can't actually change the settings of an SLB instance, I can only associate to an existing SLB instance or create a new one, and the same with the RDS. And correspondingly, if I want to delete one, I select the three dots on the right-hand side and I can then select delete to get rid of my scaling group.
Now, if I click on delete, it says in here that after I click on this, it will remove all ECS instances. It will delete any scaling group and any scaling configurations and scaling rules. I don't have any of those at the moment, they're coming in the next demonstrations. So I'll just cancel out of that. Okay, that concludes this demonstration on creating a scaling group.
In the next session, session four, we'll talk about auto-scaling, scaling configurations.
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.