Capacity adjustment method and apparatus, system, and computing device

1 . A capacity adjustment method, wherein the capacity adjustment method comprises:

creating a scaling group;

creating a first instance on a first server set for the scaling group; and

creating a second instance on a second server set for the scaling group, wherein a quantity of instances deployed on the first server set for the scaling group is limited by a first upper limit value,

wherein an instance image used to create the first instance is different from an instance image used to create the second instance, and wherein the instance image records application configuration expected to be deployed on the instance, and

wherein the quantity of instances deployed on the first server set for the scaling group and the quantity of instances deployed on the second server set for the scaling group are maintained at a ratio.

2 . The capacity adjustment method according to claim 1 , wherein:

the quantity of instances deployed on the first server set for the scaling group is limited by a first lower limit value; and wherein:

a quantity of instances deployed on the second server set for the scaling group is limited by a second upper limit value; or

a quantity of instances deployed on the second server set for the scaling group is limited by a second lower limit value.

3 . The capacity adjustment method according to claim 1 , wherein:

a processor of a server in the first server set is a reduced instruction set computer (RISC) processor; and

a processor of a server in the second server set is a complex instruction set computer (CISC) processor.

4 . The capacity adjustment method according to claim 1 , wherein:

the scaling group comprises a third instance and a fourth instance, the third instance is an instance of a virtual machine type, and the fourth instance is an instance of a container type.

5 . The capacity adjustment method according to claim 1 , wherein the capacity adjustment method comprises:

adjusting instance deployment of the scaling group on the first server set and the second server set.

6 . The capacity adjustment method according to claim 5 , wherein the adjusting instance deployment of the scaling group on the first server set and the second server set comprises:

creating an instance on the first server set with low instance costs; or

removing an instance from the second server set with high instance costs.

7 . The capacity adjustment method according to claim 5 , wherein the adjusting instance deployment of the scaling group on the first server set and the second server set comprises:

creating an instance on the second server set with high instance performance; or

removing an instance from the first server set with low instance performance.

8 . The capacity adjustment method according to claim 5 , wherein the adjusting instance deployment of the scaling group on the first server set and the second server set comprises:

creating an instance on the second server set with low resource utilization; or

removing an instance from the first server set with high resource utilization.

9 . A computing device, comprising:

one or more processors; and

a non-transitory computer readable medium storing one or more instructions that when executed by the one or more processors, cause the computing device to perform operations comprising:

creating a scaling group; and

creating a first instance on a first server set for the scaling group, and create a second instance on a second server set for the scaling group, wherein a quantity of instances deployed on the first server set for the scaling group is limited by a first upper limit value,

wherein an instance image used to create the first instance is different from an instance image used to create the second instance, and wherein the instance image records application configuration expected to be deployed on the instance, and

wherein the quantity of instances deployed on the first server set for the scaling group and the quantity of instances deployed on the second server set for the scaling group are maintained at a ratio.

10 . The computing device according to claim 9 , wherein:

the quantity of instances deployed on the first server set for the scaling group is limited by a first lower limit value; and wherein:

a quantity of instances deployed on the second server set for the scaling group is limited by a second upper limit value; or

a quantity of instances deployed on the second server set for the scaling group is limited by a second lower limit value.

11 . The computing device according to claim 9 , wherein:

a processor of a server in the first server set is a reduced instruction set computer (RISC) processor; and

a processor of a server in the second server set is a complex instruction set computer (CISC) processor.

12 . The computing device according to claim 9 , wherein the scaling group comprises a third instance and a fourth instance, the third instance is an instance of a virtual machine type, and the fourth instance is an instance of a container type.

13 . The computing device according to claim 9 , wherein the operations further comprise adjusting instance deployment of the scaling group on the first server set and the second server set.

14 . The computing device according to claim 13 , wherein adjusting the instance deployment of the scaling group on the first server set and the second server set comprises:

creating an instance on the first server set with low instance costs; or

removing an instance from the second server set with high instance costs.

15 . The computing device according to claim 13 , wherein adjusting the instance deployment of the scaling group on the first server set and the second server set comprises:

creating an instance on the second server set with high instance performance; or

removing an instance from the first server set with low instance performance.

16 . The computing device according to claim 13 , wherein adjusting the instance deployment of the scaling group on the first server set and the second server set comprises:

creating an instance on the second server set with low resource utilization; or

removing an instance from the first server set with high resource utilization.

17 . A non-transitory computer-readable storage medium storing one or more instructions executable by a computer system to perform operations comprising:

creating a scaling group;

creating a first instance on a first server set for the scaling group; and

creating a second instance on a second server set for the scaling group, wherein a quantity of instances deployed on the first server set for the scaling group is limited by a first upper limit value,

wherein an instance image used to create the first instance is different from an instance image used to create the second instance, and wherein the instance image records application configuration expected to be deployed on the instance, and

wherein the quantity of instances deployed on the first server set for the scaling group and the quantity of instances deployed on the second server set for the scaling group are maintained at a ratio.

18 . The non-transitory computer-readable storage medium according to claim 17 , wherein:

the quantity of instances deployed on the first server set for the scaling group is limited by a first lower limit value; and wherein:

a quantity of instances deployed on the second server set for the scaling group is limited by a second upper limit value; or

a quantity of instances deployed on the second server set for the scaling group is limited by a second lower limit value.

19 . The non-transitory computer-readable storage medium according to claim 17 , wherein the operations further comprise adjusting instance deployment of the scaling group on the first server set and the second server set.

20 . The non-transitory computer-readable storage medium according to claim 19 , wherein the adjusting instance deployment of the scaling group on the first server set and the second server set comprises:

creating an instance on the first server set with low instance costs; or

removing an instance from the second server set with high instance costs.