平安云|Ping An Cloud- Building Your Smart Future

API Overview

<table border="1" cellpadding="0" cellspacing="0"> <tbody> <tr> <td> API </td> <td> Description </td> </tr> <tr> <td> AddVmToScalingGroup </td> <td> Manually add ECS into the scaling group (1) to check whether the ECS can join the scaling group, whether it is in the same vpc, region, and available area, and whether it exceeds the maximum number of ECS instances. Besides that the status of both the ECS and the scaling group must be Running (2) only if there is a health problem the instance will remove scaling groups, modify configuration, schedule tasks and alert tasks. Manually added ECS which participate only in counting will not be removed. </td> </tr> <tr> <td> CreateAutoScalingAlarmTask </td> <td> Creating alarm tasks for Scaling groups is to monitor the performance of ECS such as cpu.busy. Users need to set monitoring items, monitoring functions, alarm times, alarm threshold, and scaling rules. When the alarm task is triggered, the scaling group will scale according to the current scaling rules. </td> </tr> <tr> <td> CreateAutoScalingGroup </td> <td> Creating a scaling group requires setting up ELB, <a href="http://dict.youdao.com/w/monitor/#keyfrom=E2Ctranslation">listener</a>, minimum and maximum instance number,  quit policies, etc. ELB and listener provide the data sources for health checks. The minimum and maximum instance number specify the instance scope of the ECS scaling groups. Quit policies: the way of the ECS quit from scaling groups during scaling activities. </td> </tr> <tr> <td> CreateAutoScalingGroupConfig </td> <td> Creating configuration for the scaling groups. When a scaling group is triggered to conducting scaling activities, an ECS is created on the bases of the scaling group configuration and is defined in it. </td> </tr> <tr> <td> CreateAutoScalingRule </td> <td> Creating scaling rules: when creating alarm tasks and timed tasks, and when the task performing scaling groups uses this group to scale, scaling rules are needed </td> </tr> <tr> <td> CreateAutoScalingScheduledTask </td> <td> Creating scheduled tasks for scaling groups: If scaling groups are configured with scheduled tasks, they will perform tasks according to the scaling rules. </td> </tr> <tr> <td> DeleteAutoScalingAlarmTask </td> <td> Delete alarm tasks of the scaling groups. </td> </tr> <tr> <td> DeleteAutoScalingGroup </td> <td> The action of deleting scaling group. Prerequisite of deleting: Only stopped Status scaling group can conduct this action. Process of deleting： (1) Remove ECS from the ELB resource pool (2) Set the enableFlag of the corresponding ECS in ASGroupInstance to 0 (3) Set the configuration status of the scaling groups configuration to InActive (4) Delete listener on the scaling group. </td> </tr> <tr> <td> DeleteAutoScalingGroupScheduledTask </td> <td> Delete scheduled tasks of the scaling groups. </td> </tr> <tr> <td> DeleteAutoScalingRule </td> <td> Delete scaling rules. Prerequisite： Scaling rules are not referenced by scheduled tasks or alarm tasks. </td> </tr> <tr> <td> GetAutoScalingAlarmTask </td> <td> Obtain details about the elastic scaling alarm tasks. </td> </tr> <tr> <td> GetAutoScalingGroup </td> <td> Obtain details about scaling groups. </td> </tr> <tr> <td> GetAutoScalingGroupConfig </td> <td> Obtain configuration details about scaling groups. </td> </tr> <tr> <td> GetAutoScalingRule </td> <td> Obtain details about scaling rules. </td> </tr> <tr> <td> GetAutoScalingScheduledTask </td> <td> Obtain details about the scheduled tasks of scaling groups. </td> </tr> <tr> <td> ListASGroupInstances </td> <td> Obtain instance list of ECS in scaling groups. </td> </tr> <tr> <td> ListAutoScalingAlarmTasks </td> <td> Obtain alarm task list of scaling groups. </td> </tr> <tr> <td> ListAutoScalingGroupActives </td> <td> Obtain detailed list of scaling activities. </td> </tr> <tr> <td> ListAutoScalingGroupActivityDetail </td> <td> Present detailed list of scaling activities. </td> </tr> <tr> <td> ListAutoScalingGroups </td> <td> Obtain the list of scaling groups. </td> </tr> <tr> <td> ListAutoScalingRules </td> <td> Obtain the list of scaling rules. </td> </tr> <tr> <td> ListAutoScalingScheduledTasks </td> <td> Obtain the scheduled tasks list of scaling groups. </td> </tr> <tr> <td> ListAvailableInstances </td> <td> Query ECS list activating in scaling groups. </td> </tr> <tr> <td> StartAutoScalingGroup </td> <td> Start scaling groups. </td> </tr> <tr> <td> StopAutoScalingGroup </td> <td> Closing scaling groups refers to stop the tasks of groups and do nothing to ECS. (1) Closing the scaling group is permitted only when the status of group is at runningstatus mode (2) Before stopping the scaling activity ,you should check if there are any ECS is being added or being removed, and if so, do not stop the scaling group. </td> </tr> <tr> <td> UpdateAutoScalingAlarmTask </td> <td> Updating the alarm tasks of scaling groups. </td> </tr> <tr> <td> UpdateAutoScalingGroup </td> <td> Updating the configuration of scaling groups: 1. To determine whether the vm number of current scaling groups is greater than the maximum value after modification, if so, it is necessary to eliminate the excess and conduct according to the entry order of  vm acquiescently; 2. To determine whether the vm number of current scalable group is less than the minimum value after modification, if so, it is necessary to increase the insufficient number of vm. </td> </tr> <tr> <td> UpdateAutoScalingGroupConfig </td> <td> Updating the configuration of scaling groups（1）Modifying of the back-end port and network are not allowed. </td> </tr> <tr> <td> UpdateAutoScalingGroupScheduledTask </td> <td> Updating elastic scheduled tasks of scaling groups. </td> </tr> <tr> <td> UpdateAutoScalingRule </td> <td> Updating scaling rules: there is no status for scaling rules, so every users can modify the scaling rules in any case. </td> </tr> </tbody> </table>

Did the above content solve your problem? Yes No