Creating a Launch Configuration

Last updated: 2020-02-25 15:26:13

PDF

AS needs to know in advance the configurations used to produce CVM instances during scale-out. Therefore, you should predefine related resources such as images, data on disks, instance configurations, key pairs, security groups, and block storage device.

It is worth noting that a launch configuration is just a template, based on which instances will be produced during automatic scale-out. Creating a launch configuration itself will not produce any instances, so it is completely free to use.

Log in to the AS console And click Launch Configuration From the left sidebar.

Step 1. Select a region

On the menu at the top of the screen, select a region for your scaling group as needed.

Here, we should pay attention to selecting the region where Cloud Virtual Machine, which Scaling group wants to bind, is located. Launch configuration and Scaling group are both regional attributes. For example, if the region of Launch configuration chooses Guangzhou, then you can only bind Scaling group of Guangzhou, and the automatically added CVM is also the CVM of Guangzhou.

Step 2. Specify specifications

Click CREATE And follow the on-screen instructions to create a launch configuration in the same steps as purchasing a CVM instance.

  1. Enter a Configuration name Such as "frontend server cluster configuration A";

  2. Select a model such as 1-core 1G, which means 1-core CPU and 1GB memory;

You can select a clean "public image" or a "custom image" where your application has already been deployed.
In order to make an instance available directly after creation, it is highly recommended that you deploy your business application in a custom image. In addition, the application in the image should be set to run at system startup , so that the instances produced by AS can be automated.

  1. Select the capacities of system and data disks.
    If you want the data disk of the produced instance to have your own data, you can specify a data disk snapshot, so that the instance comes with the data in the snapshot upon production.
  • Since the instances in a scaling group are generally stateless, it is recommended that you put your own data into a custom image for convenience.
  • If you want to use a data disk to store data, you need to set the data disk to be mounted automatically, so that expansion does not need to participate manually. See Specific methods .
  1. Select the bandwidth just like when you purchase a CVM instance.

  2. Set the username, password, and security group.

  3. Click Confirm.

  4. Based on the Launch configuration to create Scaling group. The launch configuration determines the instances to be created during scale-out, while the scaling group determines when to scale out.