@alicloud/ess20220222 1.3.2 → 1.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/client.d.ts +1646 -605
- package/dist/client.js +1716 -613
- package/dist/client.js.map +1 -1
- package/package.json +3 -3
- package/src/client.ts +1745 -605
package/dist/client.js
CHANGED
|
@@ -28,14 +28,14 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
|
|
|
28
28
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
29
29
|
exports.CreateScalingRuleRequest = exports.CreateScalingGroupResponse = exports.CreateScalingGroupResponseBody = exports.CreateScalingGroupRequest = exports.CreateScalingConfigurationResponse = exports.CreateScalingConfigurationResponseBody = exports.CreateScalingConfigurationShrinkRequest = exports.CreateScalingConfigurationRequest = exports.CreateNotificationConfigurationResponse = exports.CreateNotificationConfigurationResponseBody = exports.CreateNotificationConfigurationRequest = exports.CreateLifecycleHookResponse = exports.CreateLifecycleHookResponseBody = exports.CreateLifecycleHookRequest = exports.CreateEciScalingConfigurationResponse = exports.CreateEciScalingConfigurationResponseBody = exports.CreateEciScalingConfigurationRequest = exports.CreateAlarmResponse = exports.CreateAlarmResponseBody = exports.CreateAlarmRequest = exports.CompleteLifecycleActionResponse = exports.CompleteLifecycleActionResponseBody = exports.CompleteLifecycleActionRequest = exports.ChangeResourceGroupResponse = exports.ChangeResourceGroupResponseBody = exports.ChangeResourceGroupRequest = exports.AttachVServerGroupsResponse = exports.AttachVServerGroupsResponseBody = exports.AttachVServerGroupsRequest = exports.AttachServerGroupsResponse = exports.AttachServerGroupsResponseBody = exports.AttachServerGroupsRequest = exports.AttachLoadBalancersResponse = exports.AttachLoadBalancersResponseBody = exports.AttachLoadBalancersRequest = exports.AttachInstancesResponse = exports.AttachInstancesResponseBody = exports.AttachInstancesRequest = exports.AttachDBInstancesResponse = exports.AttachDBInstancesResponseBody = exports.AttachDBInstancesRequest = exports.AttachAlbServerGroupsResponse = exports.AttachAlbServerGroupsResponseBody = exports.AttachAlbServerGroupsRequest = exports.ApplyScalingGroupResponse = exports.ApplyScalingGroupResponseBody = exports.ApplyScalingGroupRequest = exports.ApplyEciScalingConfigurationResponse = exports.ApplyEciScalingConfigurationResponseBody = exports.ApplyEciScalingConfigurationRequest = void 0;
|
|
30
30
|
exports.DescribeLimitationResponse = exports.DescribeLimitationResponseBody = exports.DescribeLimitationRequest = exports.DescribeLifecycleHooksResponse = exports.DescribeLifecycleHooksResponseBody = exports.DescribeLifecycleHooksRequest = exports.DescribeLifecycleActionsResponse = exports.DescribeLifecycleActionsResponseBody = exports.DescribeLifecycleActionsRequest = exports.DescribeEciScalingConfigurationsResponse = exports.DescribeEciScalingConfigurationsResponseBody = exports.DescribeEciScalingConfigurationsRequest = exports.DescribeEciScalingConfigurationDetailResponse = exports.DescribeEciScalingConfigurationDetailResponseBody = exports.DescribeEciScalingConfigurationDetailRequest = exports.DescribeAlarmsResponse = exports.DescribeAlarmsResponseBody = exports.DescribeAlarmsRequest = exports.DeleteScheduledTaskResponse = exports.DeleteScheduledTaskResponseBody = exports.DeleteScheduledTaskRequest = exports.DeleteScalingRuleResponse = exports.DeleteScalingRuleResponseBody = exports.DeleteScalingRuleRequest = exports.DeleteScalingGroupResponse = exports.DeleteScalingGroupResponseBody = exports.DeleteScalingGroupRequest = exports.DeleteScalingConfigurationResponse = exports.DeleteScalingConfigurationResponseBody = exports.DeleteScalingConfigurationRequest = exports.DeleteNotificationConfigurationResponse = exports.DeleteNotificationConfigurationResponseBody = exports.DeleteNotificationConfigurationRequest = exports.DeleteLifecycleHookResponse = exports.DeleteLifecycleHookResponseBody = exports.DeleteLifecycleHookRequest = exports.DeleteEciScalingConfigurationResponse = exports.DeleteEciScalingConfigurationResponseBody = exports.DeleteEciScalingConfigurationRequest = exports.DeleteAlarmResponse = exports.DeleteAlarmResponseBody = exports.DeleteAlarmRequest = exports.DeactivateScalingConfigurationResponse = exports.DeactivateScalingConfigurationResponseBody = exports.DeactivateScalingConfigurationRequest = exports.CreateScheduledTaskResponse = exports.CreateScheduledTaskResponseBody = exports.CreateScheduledTaskRequest = exports.CreateScalingRuleResponse = exports.CreateScalingRuleResponseBody = void 0;
|
|
31
|
-
exports.
|
|
32
|
-
exports.
|
|
33
|
-
exports.
|
|
34
|
-
exports.
|
|
35
|
-
exports.
|
|
36
|
-
exports.
|
|
37
|
-
exports.
|
|
38
|
-
exports.TagResourcesRequestTags = exports.ScaleWithAdjustmentRequestOverrides = exports.ScaleWithAdjustmentRequestOverridesContainerOverrides = exports.ScaleWithAdjustmentRequestOverridesContainerOverridesEnvironmentVars = exports.ScaleWithAdjustmentRequestLifecycleHookContext = exports.ModifyScalingRuleRequestStepAdjustments = exports.ModifyScalingRuleRequestAlarmDimensions = exports.ModifyScalingGroupRequestLaunchTemplateOverrides = exports.ModifyScalingConfigurationShrinkRequestSpotPriceLimits = exports.ModifyScalingConfigurationShrinkRequestNetworkInterfaces = exports.ModifyScalingConfigurationShrinkRequestInstanceTypeOverrides = exports.ModifyScalingConfigurationShrinkRequestInstancePatternInfos = exports.ModifyScalingConfigurationShrinkRequestDataDisks = exports.ModifyScalingConfigurationShrinkRequestCustomPriorities = void 0;
|
|
31
|
+
exports.DetachServerGroupsResponseBody = exports.DetachServerGroupsRequest = exports.DetachLoadBalancersResponse = exports.DetachLoadBalancersResponseBody = exports.DetachLoadBalancersRequest = exports.DetachInstancesResponse = exports.DetachInstancesResponseBody = exports.DetachInstancesRequest = exports.DetachDBInstancesResponse = exports.DetachDBInstancesResponseBody = exports.DetachDBInstancesRequest = exports.DetachAlbServerGroupsResponse = exports.DetachAlbServerGroupsResponseBody = exports.DetachAlbServerGroupsRequest = exports.DescribeScheduledTasksResponse = exports.DescribeScheduledTasksResponseBody = exports.DescribeScheduledTasksRequest = exports.DescribeScalingRulesResponse = exports.DescribeScalingRulesResponseBody = exports.DescribeScalingRulesRequest = exports.DescribeScalingInstancesResponse = exports.DescribeScalingInstancesResponseBody = exports.DescribeScalingInstancesRequest = exports.DescribeScalingGroupsResponse = exports.DescribeScalingGroupsResponseBody = exports.DescribeScalingGroupsRequest = exports.DescribeScalingGroupDetailResponse = exports.DescribeScalingGroupDetailResponseBody = exports.DescribeScalingGroupDetailRequest = exports.DescribeScalingConfigurationsResponse = exports.DescribeScalingConfigurationsResponseBody = exports.DescribeScalingConfigurationsRequest = exports.DescribeScalingActivityDetailResponse = exports.DescribeScalingActivityDetailResponseBody = exports.DescribeScalingActivityDetailRequest = exports.DescribeScalingActivitiesResponse = exports.DescribeScalingActivitiesResponseBody = exports.DescribeScalingActivitiesRequest = exports.DescribeRegionsResponse = exports.DescribeRegionsResponseBody = exports.DescribeRegionsRequest = exports.DescribePatternTypesResponse = exports.DescribePatternTypesResponseBody = exports.DescribePatternTypesRequest = exports.DescribeNotificationTypesResponse = exports.DescribeNotificationTypesResponseBody = exports.DescribeNotificationTypesRequest = exports.DescribeNotificationConfigurationsResponse = exports.DescribeNotificationConfigurationsResponseBody = exports.DescribeNotificationConfigurationsRequest = void 0;
|
|
32
|
+
exports.ModifyScalingConfigurationRequest = exports.ModifyNotificationConfigurationResponse = exports.ModifyNotificationConfigurationResponseBody = exports.ModifyNotificationConfigurationRequest = exports.ModifyLifecycleHookResponse = exports.ModifyLifecycleHookResponseBody = exports.ModifyLifecycleHookRequest = exports.ModifyInstanceAttributeResponse = exports.ModifyInstanceAttributeResponseBody = exports.ModifyInstanceAttributeRequest = exports.ModifyEciScalingConfigurationResponse = exports.ModifyEciScalingConfigurationResponseBody = exports.ModifyEciScalingConfigurationRequest = exports.ModifyAlarmResponse = exports.ModifyAlarmResponseBody = exports.ModifyAlarmRequest = exports.ListTagValuesResponse = exports.ListTagValuesResponseBody = exports.ListTagValuesRequest = exports.ListTagResourcesResponse = exports.ListTagResourcesResponseBody = exports.ListTagResourcesRequest = exports.ListTagKeysResponse = exports.ListTagKeysResponseBody = exports.ListTagKeysRequest = exports.ExitStandbyResponse = exports.ExitStandbyResponseBody = exports.ExitStandbyRequest = exports.ExecuteScalingRuleResponse = exports.ExecuteScalingRuleResponseBody = exports.ExecuteScalingRuleRequest = exports.EnterStandbyResponse = exports.EnterStandbyResponseBody = exports.EnterStandbyRequest = exports.EnableScalingGroupResponse = exports.EnableScalingGroupResponseBody = exports.EnableScalingGroupRequest = exports.EnableAlarmResponse = exports.EnableAlarmResponseBody = exports.EnableAlarmRequest = exports.DisableScalingGroupResponse = exports.DisableScalingGroupResponseBody = exports.DisableScalingGroupRequest = exports.DisableAlarmResponse = exports.DisableAlarmResponseBody = exports.DisableAlarmRequest = exports.DetachVServerGroupsResponse = exports.DetachVServerGroupsResponseBody = exports.DetachVServerGroupsRequest = exports.DetachServerGroupsResponse = void 0;
|
|
33
|
+
exports.VerifyUserRequest = exports.VerifyAuthenticationResponse = exports.VerifyAuthenticationResponseBody = exports.VerifyAuthenticationRequest = exports.UntagResourcesResponse = exports.UntagResourcesResponseBody = exports.UntagResourcesRequest = exports.TagResourcesResponse = exports.TagResourcesResponseBody = exports.TagResourcesRequest = exports.SuspendProcessesResponse = exports.SuspendProcessesResponseBody = exports.SuspendProcessesRequest = exports.SetInstancesProtectionResponse = exports.SetInstancesProtectionResponseBody = exports.SetInstancesProtectionRequest = exports.SetInstanceHealthResponse = exports.SetInstanceHealthResponseBody = exports.SetInstanceHealthRequest = exports.SetGroupDeletionProtectionResponse = exports.SetGroupDeletionProtectionResponseBody = exports.SetGroupDeletionProtectionRequest = exports.ScaleWithAdjustmentResponse = exports.ScaleWithAdjustmentResponseBody = exports.ScaleWithAdjustmentShrinkRequest = exports.ScaleWithAdjustmentRequest = exports.ResumeProcessesResponse = exports.ResumeProcessesResponseBody = exports.ResumeProcessesRequest = exports.RemoveInstancesResponse = exports.RemoveInstancesResponseBody = exports.RemoveInstancesRequest = exports.RecordLifecycleActionHeartbeatResponse = exports.RecordLifecycleActionHeartbeatResponseBody = exports.RecordLifecycleActionHeartbeatRequest = exports.RebalanceInstancesResponse = exports.RebalanceInstancesResponseBody = exports.RebalanceInstancesRequest = exports.ModifyScheduledTaskResponse = exports.ModifyScheduledTaskResponseBody = exports.ModifyScheduledTaskRequest = exports.ModifyScalingRuleResponse = exports.ModifyScalingRuleResponseBody = exports.ModifyScalingRuleRequest = exports.ModifyScalingGroupResponse = exports.ModifyScalingGroupResponseBody = exports.ModifyScalingGroupRequest = exports.ModifyScalingConfigurationResponse = exports.ModifyScalingConfigurationResponseBody = exports.ModifyScalingConfigurationShrinkRequest = void 0;
|
|
34
|
+
exports.CreateScalingConfigurationRequestNetworkInterfaces = exports.CreateScalingConfigurationRequestInstanceTypeOverrides = exports.CreateScalingConfigurationRequestInstancePatternInfos = exports.CreateScalingConfigurationRequestDataDisks = exports.CreateScalingConfigurationRequestCustomPriorities = exports.CreateScalingConfigurationRequestSystemDisk = exports.CreateScalingConfigurationRequestPrivatePoolOptions = exports.CreateScalingConfigurationRequestImageOptions = exports.CreateEciScalingConfigurationRequestVolumes = exports.CreateEciScalingConfigurationRequestVolumesConfigFileVolumeConfigFileToPaths = exports.CreateEciScalingConfigurationRequestVolumesNFSVolume = exports.CreateEciScalingConfigurationRequestVolumesHostPathVolume = exports.CreateEciScalingConfigurationRequestVolumesFlexVolume = exports.CreateEciScalingConfigurationRequestVolumesEmptyDirVolume = exports.CreateEciScalingConfigurationRequestVolumesDiskVolume = exports.CreateEciScalingConfigurationRequestTags = exports.CreateEciScalingConfigurationRequestSecurityContextSysctls = exports.CreateEciScalingConfigurationRequestInitContainers = exports.CreateEciScalingConfigurationRequestInitContainersInitContainerVolumeMounts = exports.CreateEciScalingConfigurationRequestInitContainersInitContainerPorts = exports.CreateEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVars = exports.CreateEciScalingConfigurationRequestInitContainersSecurityContext = exports.CreateEciScalingConfigurationRequestInitContainersSecurityContextCapability = exports.CreateEciScalingConfigurationRequestImageRegistryCredentials = exports.CreateEciScalingConfigurationRequestHostAliases = exports.CreateEciScalingConfigurationRequestDnsConfigOptions = exports.CreateEciScalingConfigurationRequestContainers = exports.CreateEciScalingConfigurationRequestContainersVolumeMounts = exports.CreateEciScalingConfigurationRequestContainersPorts = exports.CreateEciScalingConfigurationRequestContainersEnvironmentVars = exports.CreateEciScalingConfigurationRequestContainersSecurityContext = exports.CreateEciScalingConfigurationRequestContainersSecurityContextCapability = exports.CreateEciScalingConfigurationRequestContainersReadinessProbe = exports.CreateEciScalingConfigurationRequestContainersReadinessProbeTcpSocket = exports.CreateEciScalingConfigurationRequestContainersReadinessProbeHttpGet = exports.CreateEciScalingConfigurationRequestContainersReadinessProbeExec = exports.CreateEciScalingConfigurationRequestContainersLivenessProbe = exports.CreateEciScalingConfigurationRequestContainersLivenessProbeTcpSocket = exports.CreateEciScalingConfigurationRequestContainersLivenessProbeHttpGet = exports.CreateEciScalingConfigurationRequestContainersLivenessProbeExec = exports.CreateEciScalingConfigurationRequestAcrRegistryInfos = exports.CreateAlarmRequestExpressions = exports.CreateAlarmRequestDimensions = exports.AttachVServerGroupsRequestVServerGroups = exports.AttachVServerGroupsRequestVServerGroupsVServerGroupAttributes = exports.AttachServerGroupsRequestServerGroups = exports.AttachLoadBalancersRequestLoadBalancerConfigs = exports.AttachAlbServerGroupsRequestAlbServerGroups = exports.VerifyUserResponse = exports.VerifyUserResponseBody = void 0;
|
|
35
|
+
exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsInitContainersInitContainerEnvironmentVars = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsImageRegistryCredentials = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsHostAliases = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsDnsConfigOptions = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsContainers = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsContainersVolumeMounts = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsContainersPorts = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsContainersEnvironmentVars = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsAcrRegistryInfos = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfiguration = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationVolumes = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationVolumesConfigFileVolumeConfigFileToPaths = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationTags = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationSecurityContextSysCtls = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationInitContainers = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationInitContainersInitContainerVolumeMounts = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationInitContainersInitContainerPorts = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationInitContainersInitContainerEnvironmentVars = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationImageRegistryCredentials = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationHostAliases = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationDnsConfigOptions = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationContainers = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationContainersVolumeMounts = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationContainersPorts = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationContainersEnvironmentVars = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationAcrRegistryInfos = exports.DescribeAlarmsResponseBodyAlarmList = exports.DescribeAlarmsResponseBodyAlarmListExpressions = exports.DescribeAlarmsResponseBodyAlarmListDimensions = exports.CreateScalingRuleRequestStepAdjustments = exports.CreateScalingRuleRequestAlarmDimensions = exports.CreateScalingGroupRequestVServerGroups = exports.CreateScalingGroupRequestVServerGroupsVServerGroupAttributes = exports.CreateScalingGroupRequestTags = exports.CreateScalingGroupRequestServerGroups = exports.CreateScalingGroupRequestLoadBalancerConfigs = exports.CreateScalingGroupRequestLifecycleHooks = exports.CreateScalingGroupRequestLaunchTemplateOverrides = exports.CreateScalingGroupRequestDBInstances = exports.CreateScalingGroupRequestAlbServerGroups = exports.CreateScalingConfigurationShrinkRequestSpotPriceLimits = exports.CreateScalingConfigurationShrinkRequestNetworkInterfaces = exports.CreateScalingConfigurationShrinkRequestInstanceTypeOverrides = exports.CreateScalingConfigurationShrinkRequestInstancePatternInfos = exports.CreateScalingConfigurationShrinkRequestDataDisks = exports.CreateScalingConfigurationShrinkRequestCustomPriorities = exports.CreateScalingConfigurationShrinkRequestSystemDisk = exports.CreateScalingConfigurationShrinkRequestPrivatePoolOptions = exports.CreateScalingConfigurationShrinkRequestImageOptions = exports.CreateScalingConfigurationRequestSpotPriceLimits = void 0;
|
|
36
|
+
exports.DetachServerGroupsRequestServerGroups = exports.DetachAlbServerGroupsRequestAlbServerGroups = exports.DescribeScheduledTasksResponseBodyScheduledTasks = exports.DescribeScalingRulesResponseBodyScalingRules = exports.DescribeScalingRulesResponseBodyScalingRulesStepAdjustments = exports.DescribeScalingRulesResponseBodyScalingRulesAlarms = exports.DescribeScalingRulesResponseBodyScalingRulesAlarmsDimensions = exports.DescribeScalingRulesResponseBodyScalingRulesAlarmDimensions = exports.DescribeScalingInstancesResponseBodyScalingInstances = exports.DescribeScalingGroupsResponseBodyScalingGroups = exports.DescribeScalingGroupsResponseBodyScalingGroupsVServerGroups = exports.DescribeScalingGroupsResponseBodyScalingGroupsVServerGroupsVServerGroupAttributes = exports.DescribeScalingGroupsResponseBodyScalingGroupsTags = exports.DescribeScalingGroupsResponseBodyScalingGroupsServerGroups = exports.DescribeScalingGroupsResponseBodyScalingGroupsLoadBalancerConfigs = exports.DescribeScalingGroupsResponseBodyScalingGroupsLaunchTemplateOverrides = exports.DescribeScalingGroupsResponseBodyScalingGroupsDBInstances = exports.DescribeScalingGroupsResponseBodyScalingGroupsAlbServerGroups = exports.DescribeScalingGroupsRequestTags = exports.DescribeScalingGroupDetailResponseBodyScalingGroup = exports.DescribeScalingGroupDetailResponseBodyScalingGroupVServerGroups = exports.DescribeScalingGroupDetailResponseBodyScalingGroupVServerGroupsVServerGroupAttributes = exports.DescribeScalingGroupDetailResponseBodyScalingGroupTags = exports.DescribeScalingGroupDetailResponseBodyScalingGroupServerGroups = exports.DescribeScalingGroupDetailResponseBodyScalingGroupLoadBalancerConfigs = exports.DescribeScalingGroupDetailResponseBodyScalingGroupLaunchTemplateOverrides = exports.DescribeScalingGroupDetailResponseBodyScalingGroupAlbServerGroups = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurations = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsTags = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsSpotPriceLimits = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsSchedulerOptions = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsNetworkInterfaces = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsInstancePatternInfos = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsDataDisks = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsCustomPriorities = exports.DescribeScalingActivitiesResponseBodyScalingActivities = exports.DescribeScalingActivitiesResponseBodyScalingActivitiesLifecycleHookContext = exports.DescribeRegionsResponseBodyRegions = exports.DescribePatternTypesResponseBodyPatternTypes = exports.DescribeNotificationConfigurationsResponseBodyNotificationConfigurationModels = exports.DescribeLifecycleHooksResponseBodyLifecycleHooks = exports.DescribeLifecycleActionsResponseBodyLifecycleActions = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurations = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsVolumes = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsVolumesConfigFileVolumeConfigFileToPaths = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsTags = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsSecurityContextSysCtls = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsInitContainers = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsInitContainersInitContainerVolumeMounts = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsInitContainersInitContainerPorts = void 0;
|
|
37
|
+
exports.ModifyScalingConfigurationRequestNetworkInterfaces = exports.ModifyScalingConfigurationRequestInstanceTypeOverrides = exports.ModifyScalingConfigurationRequestInstancePatternInfos = exports.ModifyScalingConfigurationRequestDataDisks = exports.ModifyScalingConfigurationRequestCustomPriorities = exports.ModifyScalingConfigurationRequestSystemDisk = exports.ModifyScalingConfigurationRequestPrivatePoolOptions = exports.ModifyScalingConfigurationRequestImageOptions = exports.ModifyEciScalingConfigurationRequestVolumes = exports.ModifyEciScalingConfigurationRequestVolumesConfigFileVolumeConfigFileToPath = exports.ModifyEciScalingConfigurationRequestVolumesNFSVolume = exports.ModifyEciScalingConfigurationRequestVolumesHostPathVolume = exports.ModifyEciScalingConfigurationRequestVolumesFlexVolume = exports.ModifyEciScalingConfigurationRequestVolumesEmptyDirVolume = exports.ModifyEciScalingConfigurationRequestVolumesDiskVolume = exports.ModifyEciScalingConfigurationRequestTags = exports.ModifyEciScalingConfigurationRequestSecurityContextSysCtls = exports.ModifyEciScalingConfigurationRequestInitContainers = exports.ModifyEciScalingConfigurationRequestInitContainersInitContainerVolumeMounts = exports.ModifyEciScalingConfigurationRequestInitContainersInitContainerPorts = exports.ModifyEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVars = exports.ModifyEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVarsFieldRef = exports.ModifyEciScalingConfigurationRequestInitContainersSecurityContext = exports.ModifyEciScalingConfigurationRequestInitContainersSecurityContextCapability = exports.ModifyEciScalingConfigurationRequestImageRegistryCredentials = exports.ModifyEciScalingConfigurationRequestHostAliases = exports.ModifyEciScalingConfigurationRequestDnsConfigOptions = exports.ModifyEciScalingConfigurationRequestContainers = exports.ModifyEciScalingConfigurationRequestContainersVolumeMounts = exports.ModifyEciScalingConfigurationRequestContainersPorts = exports.ModifyEciScalingConfigurationRequestContainersEnvironmentVars = exports.ModifyEciScalingConfigurationRequestContainersEnvironmentVarsFieldRef = exports.ModifyEciScalingConfigurationRequestContainersSecurityContext = exports.ModifyEciScalingConfigurationRequestContainersSecurityContextCapability = exports.ModifyEciScalingConfigurationRequestContainersReadinessProbe = exports.ModifyEciScalingConfigurationRequestContainersReadinessProbeTcpSocket = exports.ModifyEciScalingConfigurationRequestContainersReadinessProbeHttpGet = exports.ModifyEciScalingConfigurationRequestContainersReadinessProbeExec = exports.ModifyEciScalingConfigurationRequestContainersLivenessProbe = exports.ModifyEciScalingConfigurationRequestContainersLivenessProbeTcpSocket = exports.ModifyEciScalingConfigurationRequestContainersLivenessProbeHttpGet = exports.ModifyEciScalingConfigurationRequestContainersLivenessProbeExec = exports.ModifyEciScalingConfigurationRequestAcrRegistryInfos = exports.ModifyAlarmRequestExpressions = exports.ModifyAlarmRequestDimensions = exports.ListTagResourcesResponseBodyTagResources = exports.ListTagResourcesRequestTags = exports.EnableScalingGroupRequestLaunchTemplateOverrides = exports.DetachVServerGroupsRequestVServerGroups = exports.DetachVServerGroupsRequestVServerGroupsVServerGroupAttributes = void 0;
|
|
38
|
+
exports.TagResourcesRequestTags = exports.ScaleWithAdjustmentRequestOverrides = exports.ScaleWithAdjustmentRequestOverridesContainerOverrides = exports.ScaleWithAdjustmentRequestOverridesContainerOverridesEnvironmentVars = exports.ScaleWithAdjustmentRequestLifecycleHookContext = exports.ModifyScalingRuleRequestStepAdjustments = exports.ModifyScalingRuleRequestAlarmDimensions = exports.ModifyScalingGroupRequestLaunchTemplateOverrides = exports.ModifyScalingConfigurationShrinkRequestSpotPriceLimits = exports.ModifyScalingConfigurationShrinkRequestNetworkInterfaces = exports.ModifyScalingConfigurationShrinkRequestInstanceTypeOverrides = exports.ModifyScalingConfigurationShrinkRequestInstancePatternInfos = exports.ModifyScalingConfigurationShrinkRequestDataDisks = exports.ModifyScalingConfigurationShrinkRequestCustomPriorities = exports.ModifyScalingConfigurationShrinkRequestSystemDisk = exports.ModifyScalingConfigurationShrinkRequestPrivatePoolOptions = exports.ModifyScalingConfigurationShrinkRequestImageOptions = exports.ModifyScalingConfigurationRequestSpotPriceLimits = void 0;
|
|
39
39
|
// This file is auto-generated, don't edit it
|
|
40
40
|
/**
|
|
41
41
|
*
|
|
@@ -2805,6 +2805,84 @@ class DescribeNotificationTypesResponse extends $tea.Model {
|
|
|
2805
2805
|
}
|
|
2806
2806
|
}
|
|
2807
2807
|
exports.DescribeNotificationTypesResponse = DescribeNotificationTypesResponse;
|
|
2808
|
+
class DescribePatternTypesRequest extends $tea.Model {
|
|
2809
|
+
static names() {
|
|
2810
|
+
return {
|
|
2811
|
+
architecture: 'Architecture',
|
|
2812
|
+
burstablePerformance: 'BurstablePerformance',
|
|
2813
|
+
channelId: 'ChannelId',
|
|
2814
|
+
cores: 'Cores',
|
|
2815
|
+
coresList: 'CoresList',
|
|
2816
|
+
excludedInstanceType: 'ExcludedInstanceType',
|
|
2817
|
+
instanceFamilyLevel: 'InstanceFamilyLevel',
|
|
2818
|
+
maxPrice: 'MaxPrice',
|
|
2819
|
+
memory: 'Memory',
|
|
2820
|
+
memoryList: 'MemoryList',
|
|
2821
|
+
regionId: 'RegionId',
|
|
2822
|
+
spotStrategy: 'SpotStrategy',
|
|
2823
|
+
vSwitchId: 'VSwitchId',
|
|
2824
|
+
};
|
|
2825
|
+
}
|
|
2826
|
+
static types() {
|
|
2827
|
+
return {
|
|
2828
|
+
architecture: { 'type': 'array', 'itemType': 'string' },
|
|
2829
|
+
burstablePerformance: 'string',
|
|
2830
|
+
channelId: 'number',
|
|
2831
|
+
cores: 'number',
|
|
2832
|
+
coresList: { 'type': 'array', 'itemType': 'number' },
|
|
2833
|
+
excludedInstanceType: { 'type': 'array', 'itemType': 'string' },
|
|
2834
|
+
instanceFamilyLevel: 'string',
|
|
2835
|
+
maxPrice: 'number',
|
|
2836
|
+
memory: 'number',
|
|
2837
|
+
memoryList: { 'type': 'array', 'itemType': 'number' },
|
|
2838
|
+
regionId: 'string',
|
|
2839
|
+
spotStrategy: 'string',
|
|
2840
|
+
vSwitchId: { 'type': 'array', 'itemType': 'string' },
|
|
2841
|
+
};
|
|
2842
|
+
}
|
|
2843
|
+
constructor(map) {
|
|
2844
|
+
super(map);
|
|
2845
|
+
}
|
|
2846
|
+
}
|
|
2847
|
+
exports.DescribePatternTypesRequest = DescribePatternTypesRequest;
|
|
2848
|
+
class DescribePatternTypesResponseBody extends $tea.Model {
|
|
2849
|
+
static names() {
|
|
2850
|
+
return {
|
|
2851
|
+
patternTypes: 'PatternTypes',
|
|
2852
|
+
requestId: 'RequestId',
|
|
2853
|
+
};
|
|
2854
|
+
}
|
|
2855
|
+
static types() {
|
|
2856
|
+
return {
|
|
2857
|
+
patternTypes: { 'type': 'array', 'itemType': DescribePatternTypesResponseBodyPatternTypes },
|
|
2858
|
+
requestId: 'string',
|
|
2859
|
+
};
|
|
2860
|
+
}
|
|
2861
|
+
constructor(map) {
|
|
2862
|
+
super(map);
|
|
2863
|
+
}
|
|
2864
|
+
}
|
|
2865
|
+
exports.DescribePatternTypesResponseBody = DescribePatternTypesResponseBody;
|
|
2866
|
+
class DescribePatternTypesResponse extends $tea.Model {
|
|
2867
|
+
static names() {
|
|
2868
|
+
return {
|
|
2869
|
+
headers: 'headers',
|
|
2870
|
+
statusCode: 'statusCode',
|
|
2871
|
+
body: 'body',
|
|
2872
|
+
};
|
|
2873
|
+
}
|
|
2874
|
+
static types() {
|
|
2875
|
+
return {
|
|
2876
|
+
headers: { 'type': 'map', 'keyType': 'string', 'valueType': 'string' },
|
|
2877
|
+
statusCode: 'number',
|
|
2878
|
+
body: DescribePatternTypesResponseBody,
|
|
2879
|
+
};
|
|
2880
|
+
}
|
|
2881
|
+
constructor(map) {
|
|
2882
|
+
super(map);
|
|
2883
|
+
}
|
|
2884
|
+
}
|
|
2885
|
+
exports.DescribePatternTypesResponse = DescribePatternTypesResponse;
|
|
2808
2886
|
class DescribeRegionsRequest extends $tea.Model {
|
|
2809
2887
|
static names() {
|
|
2810
2888
|
return {
|
|
@@ -3623,6 +3701,7 @@ class DetachInstancesRequest extends $tea.Model {
|
|
|
3623
3701
|
clientToken: 'ClientToken',
|
|
3624
3702
|
decreaseDesiredCapacity: 'DecreaseDesiredCapacity',
|
|
3625
3703
|
detachOption: 'DetachOption',
|
|
3704
|
+
ignoreInvalidInstance: 'IgnoreInvalidInstance',
|
|
3626
3705
|
instanceIds: 'InstanceIds',
|
|
3627
3706
|
lifecycleHook: 'LifecycleHook',
|
|
3628
3707
|
ownerAccount: 'OwnerAccount',
|
|
@@ -3637,6 +3716,7 @@ class DetachInstancesRequest extends $tea.Model {
|
|
|
3637
3716
|
clientToken: 'string',
|
|
3638
3717
|
decreaseDesiredCapacity: 'boolean',
|
|
3639
3718
|
detachOption: 'string',
|
|
3719
|
+
ignoreInvalidInstance: 'boolean',
|
|
3640
3720
|
instanceIds: { 'type': 'array', 'itemType': 'string' },
|
|
3641
3721
|
lifecycleHook: 'boolean',
|
|
3642
3722
|
ownerAccount: 'string',
|
|
@@ -5688,6 +5768,7 @@ class RemoveInstancesRequest extends $tea.Model {
|
|
|
5688
5768
|
return {
|
|
5689
5769
|
clientToken: 'ClientToken',
|
|
5690
5770
|
decreaseDesiredCapacity: 'DecreaseDesiredCapacity',
|
|
5771
|
+
ignoreInvalidInstance: 'IgnoreInvalidInstance',
|
|
5691
5772
|
instanceIds: 'InstanceIds',
|
|
5692
5773
|
ownerAccount: 'OwnerAccount',
|
|
5693
5774
|
ownerId: 'OwnerId',
|
|
@@ -5702,6 +5783,7 @@ class RemoveInstancesRequest extends $tea.Model {
|
|
|
5702
5783
|
return {
|
|
5703
5784
|
clientToken: 'string',
|
|
5704
5785
|
decreaseDesiredCapacity: 'boolean',
|
|
5786
|
+
ignoreInvalidInstance: 'boolean',
|
|
5705
5787
|
instanceIds: { 'type': 'array', 'itemType': 'string' },
|
|
5706
5788
|
ownerAccount: 'string',
|
|
5707
5789
|
ownerId: 'number',
|
|
@@ -9291,6 +9373,30 @@ class DescribeNotificationConfigurationsResponseBodyNotificationConfigurationMod
|
|
|
9291
9373
|
}
|
|
9292
9374
|
}
|
|
9293
9375
|
exports.DescribeNotificationConfigurationsResponseBodyNotificationConfigurationModels = DescribeNotificationConfigurationsResponseBodyNotificationConfigurationModels;
|
|
9376
|
+
class DescribePatternTypesResponseBodyPatternTypes extends $tea.Model {
|
|
9377
|
+
static names() {
|
|
9378
|
+
return {
|
|
9379
|
+
cores: 'Cores',
|
|
9380
|
+
instanceFamilyLevel: 'InstanceFamilyLevel',
|
|
9381
|
+
instanceType: 'InstanceType',
|
|
9382
|
+
instanceTypeFamily: 'InstanceTypeFamily',
|
|
9383
|
+
memory: 'Memory',
|
|
9384
|
+
};
|
|
9385
|
+
}
|
|
9386
|
+
static types() {
|
|
9387
|
+
return {
|
|
9388
|
+
cores: 'number',
|
|
9389
|
+
instanceFamilyLevel: 'string',
|
|
9390
|
+
instanceType: 'string',
|
|
9391
|
+
instanceTypeFamily: 'string',
|
|
9392
|
+
memory: 'number',
|
|
9393
|
+
};
|
|
9394
|
+
}
|
|
9395
|
+
constructor(map) {
|
|
9396
|
+
super(map);
|
|
9397
|
+
}
|
|
9398
|
+
}
|
|
9399
|
+
exports.DescribePatternTypesResponseBodyPatternTypes = DescribePatternTypesResponseBodyPatternTypes;
|
|
9294
9400
|
class DescribeRegionsResponseBodyRegions extends $tea.Model {
|
|
9295
9401
|
static names() {
|
|
9296
9402
|
return {
|
|
@@ -12143,6 +12249,16 @@ class Client extends openapi_client_1.default {
|
|
|
12143
12249
|
}
|
|
12144
12250
|
return endpoint_util_1.default.getEndpointRules(productId, regionId, endpointRule, network, suffix);
|
|
12145
12251
|
}
|
|
12252
|
+
/**
|
|
12253
|
+
* @summary Manages scaling configurations of the Elastic Container Instance type. If you want to efficiently create or update a scaling configuration of the Elastic Container Instance type by using a configuration file, you can call the ApplyEciScalingConfiguration operation.
|
|
12254
|
+
*
|
|
12255
|
+
* @description You can manage scaling configurations of the Elastic Container Instance type by using a YAML configuration file based on the following logic:
|
|
12256
|
+
* If you specify the ID of a scaling configuration, you can update the scaling configuration by using the YAML configuration file. If you do not specify the ID of a scaling configuration, you can create a scaling configuration by using the YAML configuration file.
|
|
12257
|
+
*
|
|
12258
|
+
* @param request ApplyEciScalingConfigurationRequest
|
|
12259
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
12260
|
+
* @return ApplyEciScalingConfigurationResponse
|
|
12261
|
+
*/
|
|
12146
12262
|
async applyEciScalingConfigurationWithOptions(request, runtime) {
|
|
12147
12263
|
tea_util_1.default.validateModel(request);
|
|
12148
12264
|
let query = {};
|
|
@@ -12177,10 +12293,60 @@ class Client extends openapi_client_1.default {
|
|
|
12177
12293
|
});
|
|
12178
12294
|
return $tea.cast(await this.callApi(params, req, runtime), new ApplyEciScalingConfigurationResponse({}));
|
|
12179
12295
|
}
|
|
12296
|
+
/**
|
|
12297
|
+
* @summary Manages scaling configurations of the Elastic Container Instance type. If you want to efficiently create or update a scaling configuration of the Elastic Container Instance type by using a configuration file, you can call the ApplyEciScalingConfiguration operation.
|
|
12298
|
+
*
|
|
12299
|
+
* @description You can manage scaling configurations of the Elastic Container Instance type by using a YAML configuration file based on the following logic:
|
|
12300
|
+
* If you specify the ID of a scaling configuration, you can update the scaling configuration by using the YAML configuration file. If you do not specify the ID of a scaling configuration, you can create a scaling configuration by using the YAML configuration file.
|
|
12301
|
+
*
|
|
12302
|
+
* @param request ApplyEciScalingConfigurationRequest
|
|
12303
|
+
* @return ApplyEciScalingConfigurationResponse
|
|
12304
|
+
*/
|
|
12180
12305
|
async applyEciScalingConfiguration(request) {
|
|
12181
12306
|
let runtime = new $Util.RuntimeOptions({});
|
|
12182
12307
|
return await this.applyEciScalingConfigurationWithOptions(request, runtime);
|
|
12183
12308
|
}
|
|
12309
|
+
/**
|
|
12310
|
+
* @summary 基于yaml配置进行弹性伸缩管理
|
|
12311
|
+
*
|
|
12312
|
+
* @description You can call the ApplyScalingGroup operation to create scaling groups of the Elastic Container Instance type with ease. The resources of the scaling groups are defined in Kubernetes Deployment YAML files. You can also call this operation to extend annotations for elastic container instances in Kubernetes Deployment YAML files. For more information, see "Supported annotations" in this topic.
|
|
12313
|
+
* Mapping between YAML files and scaling groups: You can map the triplet of namespace, kind, and name in a YAML file to a scaling group name. A YAML file and a scaling group have a one-to-one mapping relationship in a region. For example, if you use the Kubernetes Deployment YAML file whose name is NGINX in the default namespace to create a scaling group in a region, the unique name of the mapped scaling group is k8s_default_Deployment_nginx.
|
|
12314
|
+
* You can use a Kubernetes Deployment YAML file to manage a scaling group based on the following logic:
|
|
12315
|
+
* * If an existing scaling group has a mapping relationship with your Kubernetes Deployment YAML file, you can update the scaling group by using the YAML file.
|
|
12316
|
+
* * If no scaling group that has a mapping relationship with your Kubernetes Deployment YAML file exists, you can create a scaling group with ease by using the YAML file.
|
|
12317
|
+
* ### Precautions
|
|
12318
|
+
* 1. If you do not specify a virtual private cloud (VPC), vSwitch, security group, or annotation in your Kubernetes Deployment YAML file, the system creates a default VPC that has default vSwitches and uses the default security group ess-default-sg of Auto Scaling. By default, the security group rule allows traffic on Transmission Control Protocol (TCP)-based port 22 and port 3389 and enables Internet Control Message Protocol (ICMP) for IPv4 addresses. If you want to enable other ports or protocols, you can create custom security group rules.
|
|
12319
|
+
* 2. If you want to use a public image, you must enable the Internet access feature and configure the k8s.aliyun.com/eci-with-eip pod annotation to enable the elastic IP address (EIP) feature.
|
|
12320
|
+
* 3. After you call the ApplyScalingGroup operation to apply a Kubernetes Deployment YAML file, the scaling group immediately enters the Enabled state and the scaling configuration immediately enters the Active state. If the number of replicas that you specified in the YAML file is grater than 0, elastic container instances are automatically created.
|
|
12321
|
+
* ### Supported annotations
|
|
12322
|
+
* For more information about annotations, see [ECI Pod Annotation](https://help.aliyun.com/document_detail/186939.html).
|
|
12323
|
+
* |Annotation|Example|Description|
|
|
12324
|
+
* |---|---|---|
|
|
12325
|
+
* |k8s.aliyun.com/ess-scaling-group-min-size|1|The minimum size of the scaling group that you want to create. Default value: 0.|
|
|
12326
|
+
* |k8s.aliyun.com/ess-scaling-group-max-size|20|The maximum size of the scaling group that you want to create. Default value: maximum number of replicas or 30, whichever is greater.|
|
|
12327
|
+
* |k8s.aliyun.com/eci-ntp-server|100.100.*.*|The IP address of the Network Time Protocol (NTP) server.|
|
|
12328
|
+
* |k8s.aliyun.com/eci-use-specs|2-4Gi|The specifications of 2 vCPUs and 4 GB memory. For more information, see [Create pods by specifying multiple specifications](https://help.aliyun.com/document_detail/451267.html).|
|
|
12329
|
+
* |k8s.aliyun.com/eci-vswitch|vsw-bp1xpiowfm5vo8o3c\\*\\*\\*\\*|The ID of the vSwitch. You can specify multiple vSwitches to specify multiple zones.|
|
|
12330
|
+
* |k8s.aliyun.com/eci-security-group|sg-bp1dktddjsg5nktv\\*\\*\\*\\*|The ID of the security group. Before you configure this annotation, take note of the following requirements:<ul data-sourcepos="26:74-26:168"><li data-sourcepos="26:78-26:114">You can specify one or more security groups. You can specify up to five security groups for each scaling group.</li><li data-sourcepos="26:114-26:140">If you specify multiple security groups, the security groups must belong to the same VPC.</li><li data-sourcepos="26:140-26:163">If you specify multiple security groups, the security groups must be of the same type.</li></ul>|
|
|
12331
|
+
* |k8s.aliyun.com/eci-sls-enable|"false"|If you set the value to false, the log collection feature is disabled.
|
|
12332
|
+
* If you do not want to use Custom Resource Definition (CRD) for Simple Log Service to collect logs of specific pods, you can configure this annotation for the pods and set the value to false. This prevents resource wastes caused by Logtails created by the system.|
|
|
12333
|
+
* |k8s.aliyun.com/eci-spot-strategy|SpotAsPriceGo|The bidding policy for the preemptible instance. Valid values:<ul data-sourcepos="28:69-28:204"><li data-sourcepos="28:73-28:158">SpotWithPriceLimit: The instance is created as a preemptible instance for which you specify the maximum hourly price If you set the value to SpotWithPriceLimit, you must configure the k8s.aliyun.com/eci-spot-price-limit annotation.</li><li data-sourcepos="28:158-28:199">SpotAsPriceGo: The instance is a preemptible instance for which the market price at the time of purchase is used as the bid price.</li></ul>|
|
|
12334
|
+
* |k8s.aliyun.com/eci-spot-price-limit|"0.5"|The maximum hourly price of the preemptible instance. This value can be accurate to up to three decimal places.
|
|
12335
|
+
* This annotation takes effect only when you set the k8s.aliyun.com/eci-spot-strategy annotation to SpotWithPriceLimit.|
|
|
12336
|
+
* |k8s.aliyun.com/eci-with-eip|"true"|If you set the value to true, an EIP is automatically created and bound to each elastic container instance.|
|
|
12337
|
+
* |k8s.aliyun.com/eci-data-cache-bucket|default|The bucket of the specified DataCache. If you want to use a DataCache to create a pod, you must configure this annotation.|
|
|
12338
|
+
* |k8s.aliyun.com/eci-data-cache-pl|PL1|The performance level (PL) of the cloud disk that you want to create by using the specified DataCache.
|
|
12339
|
+
* By default, enhanced SSDs (ESSDs) are created. Default value: PL1.|
|
|
12340
|
+
* |k8s.aliyun.com/eci-data-cache-provisionedIops|"40000"|The provisioned read/write IOPS of the ESSD AutoPL disk. Valid values: 0 to min{50000, 1000 × Capacity - Baseline IOPS}. Baseline IOPS = min{1,800 + 50 × Capacity, 50,000}. For more information, see [ESSD AutoPL](https://help.aliyun.com/document_detail/368372.html).
|
|
12341
|
+
* If you configure this annotation, the cloud disk that is created by using the specified DataCache is of the ESSD AutoPL type.|
|
|
12342
|
+
* |k8s.aliyun.com/eci-data-cache-burstingEnabled|"true"|Specifies whether the Burst feature is enabled for the ESSD AutoPL disk. For more information, see [ESSD AutoPL](https://help.aliyun.com/document_detail/368372.html).
|
|
12343
|
+
* If you configure this annotation, the cloud disk that is created by using the specified DataCache is of the ESSD AutoPL type.|
|
|
12344
|
+
* |k8s.aliyun.com/eci-custom-tags|"env:test,name:alice"|The tags that you want to add to each elastic container instance. You can add up to three tags for each elastic container instance. Separate a tag key and a tag value with a colon (:). Separate multiple tags with commas (,).|
|
|
12345
|
+
*
|
|
12346
|
+
* @param request ApplyScalingGroupRequest
|
|
12347
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
12348
|
+
* @return ApplyScalingGroupResponse
|
|
12349
|
+
*/
|
|
12184
12350
|
async applyScalingGroupWithOptions(request, runtime) {
|
|
12185
12351
|
tea_util_1.default.validateModel(request);
|
|
12186
12352
|
let query = {};
|
|
@@ -12209,19 +12375,61 @@ class Client extends openapi_client_1.default {
|
|
|
12209
12375
|
});
|
|
12210
12376
|
return $tea.cast(await this.callApi(params, req, runtime), new ApplyScalingGroupResponse({}));
|
|
12211
12377
|
}
|
|
12378
|
+
/**
|
|
12379
|
+
* @summary 基于yaml配置进行弹性伸缩管理
|
|
12380
|
+
*
|
|
12381
|
+
* @description You can call the ApplyScalingGroup operation to create scaling groups of the Elastic Container Instance type with ease. The resources of the scaling groups are defined in Kubernetes Deployment YAML files. You can also call this operation to extend annotations for elastic container instances in Kubernetes Deployment YAML files. For more information, see "Supported annotations" in this topic.
|
|
12382
|
+
* Mapping between YAML files and scaling groups: You can map the triplet of namespace, kind, and name in a YAML file to a scaling group name. A YAML file and a scaling group have a one-to-one mapping relationship in a region. For example, if you use the Kubernetes Deployment YAML file whose name is NGINX in the default namespace to create a scaling group in a region, the unique name of the mapped scaling group is k8s_default_Deployment_nginx.
|
|
12383
|
+
* You can use a Kubernetes Deployment YAML file to manage a scaling group based on the following logic:
|
|
12384
|
+
* * If an existing scaling group has a mapping relationship with your Kubernetes Deployment YAML file, you can update the scaling group by using the YAML file.
|
|
12385
|
+
* * If no scaling group that has a mapping relationship with your Kubernetes Deployment YAML file exists, you can create a scaling group with ease by using the YAML file.
|
|
12386
|
+
* ### Precautions
|
|
12387
|
+
* 1. If you do not specify a virtual private cloud (VPC), vSwitch, security group, or annotation in your Kubernetes Deployment YAML file, the system creates a default VPC that has default vSwitches and uses the default security group ess-default-sg of Auto Scaling. By default, the security group rule allows traffic on Transmission Control Protocol (TCP)-based port 22 and port 3389 and enables Internet Control Message Protocol (ICMP) for IPv4 addresses. If you want to enable other ports or protocols, you can create custom security group rules.
|
|
12388
|
+
* 2. If you want to use a public image, you must enable the Internet access feature and configure the k8s.aliyun.com/eci-with-eip pod annotation to enable the elastic IP address (EIP) feature.
|
|
12389
|
+
* 3. After you call the ApplyScalingGroup operation to apply a Kubernetes Deployment YAML file, the scaling group immediately enters the Enabled state and the scaling configuration immediately enters the Active state. If the number of replicas that you specified in the YAML file is grater than 0, elastic container instances are automatically created.
|
|
12390
|
+
* ### Supported annotations
|
|
12391
|
+
* For more information about annotations, see [ECI Pod Annotation](https://help.aliyun.com/document_detail/186939.html).
|
|
12392
|
+
* |Annotation|Example|Description|
|
|
12393
|
+
* |---|---|---|
|
|
12394
|
+
* |k8s.aliyun.com/ess-scaling-group-min-size|1|The minimum size of the scaling group that you want to create. Default value: 0.|
|
|
12395
|
+
* |k8s.aliyun.com/ess-scaling-group-max-size|20|The maximum size of the scaling group that you want to create. Default value: maximum number of replicas or 30, whichever is greater.|
|
|
12396
|
+
* |k8s.aliyun.com/eci-ntp-server|100.100.*.*|The IP address of the Network Time Protocol (NTP) server.|
|
|
12397
|
+
* |k8s.aliyun.com/eci-use-specs|2-4Gi|The specifications of 2 vCPUs and 4 GB memory. For more information, see [Create pods by specifying multiple specifications](https://help.aliyun.com/document_detail/451267.html).|
|
|
12398
|
+
* |k8s.aliyun.com/eci-vswitch|vsw-bp1xpiowfm5vo8o3c\\*\\*\\*\\*|The ID of the vSwitch. You can specify multiple vSwitches to specify multiple zones.|
|
|
12399
|
+
* |k8s.aliyun.com/eci-security-group|sg-bp1dktddjsg5nktv\\*\\*\\*\\*|The ID of the security group. Before you configure this annotation, take note of the following requirements:<ul data-sourcepos="26:74-26:168"><li data-sourcepos="26:78-26:114">You can specify one or more security groups. You can specify up to five security groups for each scaling group.</li><li data-sourcepos="26:114-26:140">If you specify multiple security groups, the security groups must belong to the same VPC.</li><li data-sourcepos="26:140-26:163">If you specify multiple security groups, the security groups must be of the same type.</li></ul>|
|
|
12400
|
+
* |k8s.aliyun.com/eci-sls-enable|"false"|If you set the value to false, the log collection feature is disabled.
|
|
12401
|
+
* If you do not want to use Custom Resource Definition (CRD) for Simple Log Service to collect logs of specific pods, you can configure this annotation for the pods and set the value to false. This prevents resource wastes caused by Logtails created by the system.|
|
|
12402
|
+
* |k8s.aliyun.com/eci-spot-strategy|SpotAsPriceGo|The bidding policy for the preemptible instance. Valid values:<ul data-sourcepos="28:69-28:204"><li data-sourcepos="28:73-28:158">SpotWithPriceLimit: The instance is created as a preemptible instance for which you specify the maximum hourly price If you set the value to SpotWithPriceLimit, you must configure the k8s.aliyun.com/eci-spot-price-limit annotation.</li><li data-sourcepos="28:158-28:199">SpotAsPriceGo: The instance is a preemptible instance for which the market price at the time of purchase is used as the bid price.</li></ul>|
|
|
12403
|
+
* |k8s.aliyun.com/eci-spot-price-limit|"0.5"|The maximum hourly price of the preemptible instance. This value can be accurate to up to three decimal places.
|
|
12404
|
+
* This annotation takes effect only when you set the k8s.aliyun.com/eci-spot-strategy annotation to SpotWithPriceLimit.|
|
|
12405
|
+
* |k8s.aliyun.com/eci-with-eip|"true"|If you set the value to true, an EIP is automatically created and bound to each elastic container instance.|
|
|
12406
|
+
* |k8s.aliyun.com/eci-data-cache-bucket|default|The bucket of the specified DataCache. If you want to use a DataCache to create a pod, you must configure this annotation.|
|
|
12407
|
+
* |k8s.aliyun.com/eci-data-cache-pl|PL1|The performance level (PL) of the cloud disk that you want to create by using the specified DataCache.
|
|
12408
|
+
* By default, enhanced SSDs (ESSDs) are created. Default value: PL1.|
|
|
12409
|
+
* |k8s.aliyun.com/eci-data-cache-provisionedIops|"40000"|The provisioned read/write IOPS of the ESSD AutoPL disk. Valid values: 0 to min{50000, 1000 × Capacity - Baseline IOPS}. Baseline IOPS = min{1,800 + 50 × Capacity, 50,000}. For more information, see [ESSD AutoPL](https://help.aliyun.com/document_detail/368372.html).
|
|
12410
|
+
* If you configure this annotation, the cloud disk that is created by using the specified DataCache is of the ESSD AutoPL type.|
|
|
12411
|
+
* |k8s.aliyun.com/eci-data-cache-burstingEnabled|"true"|Specifies whether the Burst feature is enabled for the ESSD AutoPL disk. For more information, see [ESSD AutoPL](https://help.aliyun.com/document_detail/368372.html).
|
|
12412
|
+
* If you configure this annotation, the cloud disk that is created by using the specified DataCache is of the ESSD AutoPL type.|
|
|
12413
|
+
* |k8s.aliyun.com/eci-custom-tags|"env:test,name:alice"|The tags that you want to add to each elastic container instance. You can add up to three tags for each elastic container instance. Separate a tag key and a tag value with a colon (:). Separate multiple tags with commas (,).|
|
|
12414
|
+
*
|
|
12415
|
+
* @param request ApplyScalingGroupRequest
|
|
12416
|
+
* @return ApplyScalingGroupResponse
|
|
12417
|
+
*/
|
|
12212
12418
|
async applyScalingGroup(request) {
|
|
12213
12419
|
let runtime = new $Util.RuntimeOptions({});
|
|
12214
12420
|
return await this.applyScalingGroupWithOptions(request, runtime);
|
|
12215
12421
|
}
|
|
12216
12422
|
/**
|
|
12217
|
-
|
|
12218
|
-
|
|
12219
|
-
|
|
12220
|
-
|
|
12221
|
-
|
|
12222
|
-
|
|
12223
|
-
|
|
12224
|
-
|
|
12423
|
+
* @summary Associates Application Load Balancer (ALB) server groups with a scaling group.
|
|
12424
|
+
*
|
|
12425
|
+
* @description Before you associate an ALB server group with a scaling group, make sure that the following requirements are met:
|
|
12426
|
+
* * The scaling group resides in a virtual private cloud (VPC). The scaling group and the ALB server group must reside in the same VPC.
|
|
12427
|
+
* * The ALB server group is in the Available state.
|
|
12428
|
+
* * You can associate only a limited number of ALB server groups with a scaling group. To view the quota or manually request a quota increase, go to [Quota Center](https://quotas.console.aliyun.com/products/ess/quotas).
|
|
12429
|
+
*
|
|
12430
|
+
* @param request AttachAlbServerGroupsRequest
|
|
12431
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
12432
|
+
* @return AttachAlbServerGroupsResponse
|
|
12225
12433
|
*/
|
|
12226
12434
|
async attachAlbServerGroupsWithOptions(request, runtime) {
|
|
12227
12435
|
tea_util_1.default.validateModel(request);
|
|
@@ -12264,28 +12472,32 @@ class Client extends openapi_client_1.default {
|
|
|
12264
12472
|
return $tea.cast(await this.callApi(params, req, runtime), new AttachAlbServerGroupsResponse({}));
|
|
12265
12473
|
}
|
|
12266
12474
|
/**
|
|
12267
|
-
|
|
12268
|
-
|
|
12269
|
-
|
|
12270
|
-
|
|
12271
|
-
|
|
12272
|
-
|
|
12273
|
-
|
|
12475
|
+
* @summary Associates Application Load Balancer (ALB) server groups with a scaling group.
|
|
12476
|
+
*
|
|
12477
|
+
* @description Before you associate an ALB server group with a scaling group, make sure that the following requirements are met:
|
|
12478
|
+
* * The scaling group resides in a virtual private cloud (VPC). The scaling group and the ALB server group must reside in the same VPC.
|
|
12479
|
+
* * The ALB server group is in the Available state.
|
|
12480
|
+
* * You can associate only a limited number of ALB server groups with a scaling group. To view the quota or manually request a quota increase, go to [Quota Center](https://quotas.console.aliyun.com/products/ess/quotas).
|
|
12481
|
+
*
|
|
12482
|
+
* @param request AttachAlbServerGroupsRequest
|
|
12483
|
+
* @return AttachAlbServerGroupsResponse
|
|
12274
12484
|
*/
|
|
12275
12485
|
async attachAlbServerGroups(request) {
|
|
12276
12486
|
let runtime = new $Util.RuntimeOptions({});
|
|
12277
12487
|
return await this.attachAlbServerGroupsWithOptions(request, runtime);
|
|
12278
12488
|
}
|
|
12279
12489
|
/**
|
|
12280
|
-
|
|
12281
|
-
|
|
12282
|
-
|
|
12283
|
-
|
|
12284
|
-
|
|
12285
|
-
|
|
12286
|
-
|
|
12287
|
-
|
|
12288
|
-
|
|
12490
|
+
* @summary Associates one or more ApsaraDB RDS instances with a scaling group.
|
|
12491
|
+
*
|
|
12492
|
+
* @description Before you associate an ApsaraDB RDS instance with a scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
|
|
12493
|
+
* * The ApsaraDB RDS instance and the scaling group must belong to the same Alibaba Cloud account.
|
|
12494
|
+
* * The ApsaraDB RDS instance must be unlocked. For more information about the lock policy, see [ApsaraDB RDS usage notes](https://help.aliyun.com/document_detail/41872.html).
|
|
12495
|
+
* * The ApsaraDB RDS instance must be in the Running state.
|
|
12496
|
+
* After an ApsaraDB RDS instance is associated with the scaling group, the default IP address whitelist of the ApsaraDB RDS instance can contain no more than 1,000 IP addresses. For more information, see [Set the whitelist](https://help.aliyun.com/document_detail/43185.html).
|
|
12497
|
+
*
|
|
12498
|
+
* @param request AttachDBInstancesRequest
|
|
12499
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
12500
|
+
* @return AttachDBInstancesResponse
|
|
12289
12501
|
*/
|
|
12290
12502
|
async attachDBInstancesWithOptions(request, runtime) {
|
|
12291
12503
|
tea_util_1.default.validateModel(request);
|
|
@@ -12334,38 +12546,42 @@ class Client extends openapi_client_1.default {
|
|
|
12334
12546
|
return $tea.cast(await this.callApi(params, req, runtime), new AttachDBInstancesResponse({}));
|
|
12335
12547
|
}
|
|
12336
12548
|
/**
|
|
12337
|
-
|
|
12338
|
-
|
|
12339
|
-
|
|
12340
|
-
|
|
12341
|
-
|
|
12342
|
-
|
|
12343
|
-
|
|
12344
|
-
|
|
12549
|
+
* @summary Associates one or more ApsaraDB RDS instances with a scaling group.
|
|
12550
|
+
*
|
|
12551
|
+
* @description Before you associate an ApsaraDB RDS instance with a scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
|
|
12552
|
+
* * The ApsaraDB RDS instance and the scaling group must belong to the same Alibaba Cloud account.
|
|
12553
|
+
* * The ApsaraDB RDS instance must be unlocked. For more information about the lock policy, see [ApsaraDB RDS usage notes](https://help.aliyun.com/document_detail/41872.html).
|
|
12554
|
+
* * The ApsaraDB RDS instance must be in the Running state.
|
|
12555
|
+
* After an ApsaraDB RDS instance is associated with the scaling group, the default IP address whitelist of the ApsaraDB RDS instance can contain no more than 1,000 IP addresses. For more information, see [Set the whitelist](https://help.aliyun.com/document_detail/43185.html).
|
|
12556
|
+
*
|
|
12557
|
+
* @param request AttachDBInstancesRequest
|
|
12558
|
+
* @return AttachDBInstancesResponse
|
|
12345
12559
|
*/
|
|
12346
12560
|
async attachDBInstances(request) {
|
|
12347
12561
|
let runtime = new $Util.RuntimeOptions({});
|
|
12348
12562
|
return await this.attachDBInstancesWithOptions(request, runtime);
|
|
12349
12563
|
}
|
|
12350
12564
|
/**
|
|
12351
|
-
|
|
12352
|
-
|
|
12353
|
-
|
|
12354
|
-
|
|
12355
|
-
|
|
12356
|
-
|
|
12357
|
-
|
|
12358
|
-
|
|
12359
|
-
|
|
12360
|
-
|
|
12361
|
-
|
|
12362
|
-
|
|
12363
|
-
|
|
12364
|
-
|
|
12365
|
-
|
|
12366
|
-
|
|
12367
|
-
|
|
12368
|
-
|
|
12565
|
+
* @summary Adds instances to a scaling group. You can call the AttachInstances operation to add independent Elastic Compute Service (ECS) instances, elastic container instances, or non-Alibaba Cloud instances to your scaling group to provide services. You can also call this operation to change the state of ECS instances in your scaling group from Economical Mode to In Service.
|
|
12566
|
+
*
|
|
12567
|
+
* @description Before you call this operation, take note of the following items:
|
|
12568
|
+
* * The scaling group is in the Active state.
|
|
12569
|
+
* * No scaling activities in the scaling group are in progress.
|
|
12570
|
+
* The ECS instances or the elastic container instances that you want to add to a scaling group must meet the following requirements:
|
|
12571
|
+
* * The instances reside in the same region as the scaling group.
|
|
12572
|
+
* * The instances must be in the Running state.
|
|
12573
|
+
* * The instances are not added to other scaling groups.
|
|
12574
|
+
* * The instances use the subscription or pay-as-you-go billing method, or are preemptible instances.
|
|
12575
|
+
* * If the VswitchID parameter is specified for a scaling group, the instances that are in the classic network or those that are not in the same virtual private cloud (VPC) as the specified vSwitch cannot be added to the scaling group.
|
|
12576
|
+
* * If the VswitchID parameter is not specified for a scaling group, the instances that are in VPCs cannot be added to the scaling group.
|
|
12577
|
+
* If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
|
|
12578
|
+
* A successful call indicates that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity by using the value of the ScalingActivityId parameter in the response.
|
|
12579
|
+
* If the sum of the number of instances that you want to add and the number of existing instances in the scaling group is greater than the value of the MaxSize parameter, the call fails.
|
|
12580
|
+
* Instances that are manually added by calling the AttachInstances operation are not associated with the active scaling configuration of the scaling group.
|
|
12581
|
+
*
|
|
12582
|
+
* @param request AttachInstancesRequest
|
|
12583
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
12584
|
+
* @return AttachInstancesResponse
|
|
12369
12585
|
*/
|
|
12370
12586
|
async attachInstancesWithOptions(request, runtime) {
|
|
12371
12587
|
tea_util_1.default.validateModel(request);
|
|
@@ -12420,41 +12636,44 @@ class Client extends openapi_client_1.default {
|
|
|
12420
12636
|
return $tea.cast(await this.callApi(params, req, runtime), new AttachInstancesResponse({}));
|
|
12421
12637
|
}
|
|
12422
12638
|
/**
|
|
12423
|
-
|
|
12424
|
-
|
|
12425
|
-
|
|
12426
|
-
|
|
12427
|
-
|
|
12428
|
-
|
|
12429
|
-
|
|
12430
|
-
|
|
12431
|
-
|
|
12432
|
-
|
|
12433
|
-
|
|
12434
|
-
|
|
12435
|
-
|
|
12436
|
-
|
|
12437
|
-
|
|
12438
|
-
|
|
12439
|
-
|
|
12639
|
+
* @summary Adds instances to a scaling group. You can call the AttachInstances operation to add independent Elastic Compute Service (ECS) instances, elastic container instances, or non-Alibaba Cloud instances to your scaling group to provide services. You can also call this operation to change the state of ECS instances in your scaling group from Economical Mode to In Service.
|
|
12640
|
+
*
|
|
12641
|
+
* @description Before you call this operation, take note of the following items:
|
|
12642
|
+
* * The scaling group is in the Active state.
|
|
12643
|
+
* * No scaling activities in the scaling group are in progress.
|
|
12644
|
+
* The ECS instances or the elastic container instances that you want to add to a scaling group must meet the following requirements:
|
|
12645
|
+
* * The instances reside in the same region as the scaling group.
|
|
12646
|
+
* * The instances must be in the Running state.
|
|
12647
|
+
* * The instances are not added to other scaling groups.
|
|
12648
|
+
* * The instances use the subscription or pay-as-you-go billing method, or are preemptible instances.
|
|
12649
|
+
* * If the VswitchID parameter is specified for a scaling group, the instances that are in the classic network or those that are not in the same virtual private cloud (VPC) as the specified vSwitch cannot be added to the scaling group.
|
|
12650
|
+
* * If the VswitchID parameter is not specified for a scaling group, the instances that are in VPCs cannot be added to the scaling group.
|
|
12651
|
+
* If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
|
|
12652
|
+
* A successful call indicates that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity by using the value of the ScalingActivityId parameter in the response.
|
|
12653
|
+
* If the sum of the number of instances that you want to add and the number of existing instances in the scaling group is greater than the value of the MaxSize parameter, the call fails.
|
|
12654
|
+
* Instances that are manually added by calling the AttachInstances operation are not associated with the active scaling configuration of the scaling group.
|
|
12655
|
+
*
|
|
12656
|
+
* @param request AttachInstancesRequest
|
|
12657
|
+
* @return AttachInstancesResponse
|
|
12440
12658
|
*/
|
|
12441
12659
|
async attachInstances(request) {
|
|
12442
12660
|
let runtime = new $Util.RuntimeOptions({});
|
|
12443
12661
|
return await this.attachInstancesWithOptions(request, runtime);
|
|
12444
12662
|
}
|
|
12445
12663
|
/**
|
|
12446
|
-
|
|
12447
|
-
|
|
12448
|
-
|
|
12449
|
-
|
|
12450
|
-
|
|
12451
|
-
|
|
12452
|
-
|
|
12453
|
-
|
|
12454
|
-
|
|
12455
|
-
|
|
12456
|
-
|
|
12457
|
-
|
|
12664
|
+
* @summary Attaches load balancers to a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups. Load balancers help distribute the access traffic to the instances in scaling groups, which effectively improves the service performance of the scaling groups. You can call the AttachLoadBalancers operation to attach one or more load balancers to your scaling group.
|
|
12665
|
+
*
|
|
12666
|
+
* @description Before you call this operation, make sure that the following requirements are met:
|
|
12667
|
+
* * The load balancer and the scaling group belong to the same Alibaba Cloud account and region.
|
|
12668
|
+
* * The load balancer is in the `Running` state.
|
|
12669
|
+
* * At least one listener is configured for the load balancer, and the health check feature is enabled for the load balancer.
|
|
12670
|
+
* * If the network type of the load balancer and the scaling group is virtual private cloud (VPC), they use the same VPC.
|
|
12671
|
+
* * If the network type of the scaling group is VPC, and that of the load balancer is classic network and a backend server of the load balancer uses a VPC, the scaling group and the backend server use the same VPC.
|
|
12672
|
+
* * The attachment of load balancers ensures that the cumulative number of load balancers attached to the scaling group stays within the predefined maximum limit. For information about the load balancer quota, see [Limits](https://help.aliyun.com/document_detail/25863.html).
|
|
12673
|
+
*
|
|
12674
|
+
* @param request AttachLoadBalancersRequest
|
|
12675
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
12676
|
+
* @return AttachLoadBalancersResponse
|
|
12458
12677
|
*/
|
|
12459
12678
|
async attachLoadBalancersWithOptions(request, runtime) {
|
|
12460
12679
|
tea_util_1.default.validateModel(request);
|
|
@@ -12500,22 +12719,30 @@ class Client extends openapi_client_1.default {
|
|
|
12500
12719
|
return $tea.cast(await this.callApi(params, req, runtime), new AttachLoadBalancersResponse({}));
|
|
12501
12720
|
}
|
|
12502
12721
|
/**
|
|
12503
|
-
|
|
12504
|
-
|
|
12505
|
-
|
|
12506
|
-
|
|
12507
|
-
|
|
12508
|
-
|
|
12509
|
-
|
|
12510
|
-
|
|
12511
|
-
|
|
12512
|
-
|
|
12513
|
-
|
|
12722
|
+
* @summary Attaches load balancers to a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups. Load balancers help distribute the access traffic to the instances in scaling groups, which effectively improves the service performance of the scaling groups. You can call the AttachLoadBalancers operation to attach one or more load balancers to your scaling group.
|
|
12723
|
+
*
|
|
12724
|
+
* @description Before you call this operation, make sure that the following requirements are met:
|
|
12725
|
+
* * The load balancer and the scaling group belong to the same Alibaba Cloud account and region.
|
|
12726
|
+
* * The load balancer is in the `Running` state.
|
|
12727
|
+
* * At least one listener is configured for the load balancer, and the health check feature is enabled for the load balancer.
|
|
12728
|
+
* * If the network type of the load balancer and the scaling group is virtual private cloud (VPC), they use the same VPC.
|
|
12729
|
+
* * If the network type of the scaling group is VPC, and that of the load balancer is classic network and a backend server of the load balancer uses a VPC, the scaling group and the backend server use the same VPC.
|
|
12730
|
+
* * The attachment of load balancers ensures that the cumulative number of load balancers attached to the scaling group stays within the predefined maximum limit. For information about the load balancer quota, see [Limits](https://help.aliyun.com/document_detail/25863.html).
|
|
12731
|
+
*
|
|
12732
|
+
* @param request AttachLoadBalancersRequest
|
|
12733
|
+
* @return AttachLoadBalancersResponse
|
|
12514
12734
|
*/
|
|
12515
12735
|
async attachLoadBalancers(request) {
|
|
12516
12736
|
let runtime = new $Util.RuntimeOptions({});
|
|
12517
12737
|
return await this.attachLoadBalancersWithOptions(request, runtime);
|
|
12518
12738
|
}
|
|
12739
|
+
/**
|
|
12740
|
+
* @summary Attaches one or more server groups to a scaling group. You can attach the following server groups to a scaling group: Application Load Balancer (ALB) and Network Load Balancer (NLB) server groups.
|
|
12741
|
+
*
|
|
12742
|
+
* @param request AttachServerGroupsRequest
|
|
12743
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
12744
|
+
* @return AttachServerGroupsResponse
|
|
12745
|
+
*/
|
|
12519
12746
|
async attachServerGroupsWithOptions(request, runtime) {
|
|
12520
12747
|
tea_util_1.default.validateModel(request);
|
|
12521
12748
|
let query = {};
|
|
@@ -12556,29 +12783,37 @@ class Client extends openapi_client_1.default {
|
|
|
12556
12783
|
});
|
|
12557
12784
|
return $tea.cast(await this.callApi(params, req, runtime), new AttachServerGroupsResponse({}));
|
|
12558
12785
|
}
|
|
12786
|
+
/**
|
|
12787
|
+
* @summary Attaches one or more server groups to a scaling group. You can attach the following server groups to a scaling group: Application Load Balancer (ALB) and Network Load Balancer (NLB) server groups.
|
|
12788
|
+
*
|
|
12789
|
+
* @param request AttachServerGroupsRequest
|
|
12790
|
+
* @return AttachServerGroupsResponse
|
|
12791
|
+
*/
|
|
12559
12792
|
async attachServerGroups(request) {
|
|
12560
12793
|
let runtime = new $Util.RuntimeOptions({});
|
|
12561
12794
|
return await this.attachServerGroupsWithOptions(request, runtime);
|
|
12562
12795
|
}
|
|
12563
12796
|
/**
|
|
12564
|
-
|
|
12565
|
-
|
|
12566
|
-
|
|
12567
|
-
|
|
12568
|
-
|
|
12569
|
-
|
|
12570
|
-
|
|
12571
|
-
|
|
12572
|
-
|
|
12573
|
-
|
|
12574
|
-
|
|
12575
|
-
|
|
12576
|
-
|
|
12577
|
-
|
|
12578
|
-
|
|
12579
|
-
|
|
12580
|
-
|
|
12581
|
-
|
|
12797
|
+
* @summary Associates Sever Load Balancer (SLB) vServer groups with a scaling group.
|
|
12798
|
+
*
|
|
12799
|
+
* @description Before you call this operation to attach a vServer group to your scaling group, take note of the following items:
|
|
12800
|
+
* * The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
|
|
12801
|
+
* * The CLB instance and the scaling group must reside in the same region.
|
|
12802
|
+
* * The CLB instance must be in the Running state.
|
|
12803
|
+
* * The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
|
|
12804
|
+
* * The CLB instance and the scaling group must be in the same VPC if their network type is VPC.
|
|
12805
|
+
* * If the network type of the scaling group is VPC, the network type of the CLB instance is classic network, and the vServer groups of the CLB instance contain instances of the VPC network type, the instances and the scaling group must be in the same VPC.
|
|
12806
|
+
* * The vServer group that you want to attach to your scaling group must belong to the CLB instance.
|
|
12807
|
+
* * You can attach only a limited number of vServer groups to a scaling group. For information about the quota on vServer groups, see [Limits](https://help.aliyun.com/document_detail/25863.html).
|
|
12808
|
+
* When you call this operation, you must specify the following parameters:
|
|
12809
|
+
* * LoadBalancerId: the ID of the CLB instance.
|
|
12810
|
+
* * VServerGroupId: the ID of the vServer group.
|
|
12811
|
+
* * Port: the port number of the vServer group.
|
|
12812
|
+
* If a vServer group is attached to a scaling group by using different ports, Auto Scaling considers that more than one vServer group is attached to the scaling group. If multiple vServer groups with the same group ID and port number are specified in the request parameters, only the first vServer group is used. The other vServer groups are ignored.
|
|
12813
|
+
*
|
|
12814
|
+
* @param request AttachVServerGroupsRequest
|
|
12815
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
12816
|
+
* @return AttachVServerGroupsResponse
|
|
12582
12817
|
*/
|
|
12583
12818
|
async attachVServerGroupsWithOptions(request, runtime) {
|
|
12584
12819
|
tea_util_1.default.validateModel(request);
|
|
@@ -12621,28 +12856,37 @@ class Client extends openapi_client_1.default {
|
|
|
12621
12856
|
return $tea.cast(await this.callApi(params, req, runtime), new AttachVServerGroupsResponse({}));
|
|
12622
12857
|
}
|
|
12623
12858
|
/**
|
|
12624
|
-
|
|
12625
|
-
|
|
12626
|
-
|
|
12627
|
-
|
|
12628
|
-
|
|
12629
|
-
|
|
12630
|
-
|
|
12631
|
-
|
|
12632
|
-
|
|
12633
|
-
|
|
12634
|
-
|
|
12635
|
-
|
|
12636
|
-
|
|
12637
|
-
|
|
12638
|
-
|
|
12639
|
-
|
|
12640
|
-
|
|
12859
|
+
* @summary Associates Sever Load Balancer (SLB) vServer groups with a scaling group.
|
|
12860
|
+
*
|
|
12861
|
+
* @description Before you call this operation to attach a vServer group to your scaling group, take note of the following items:
|
|
12862
|
+
* * The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
|
|
12863
|
+
* * The CLB instance and the scaling group must reside in the same region.
|
|
12864
|
+
* * The CLB instance must be in the Running state.
|
|
12865
|
+
* * The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
|
|
12866
|
+
* * The CLB instance and the scaling group must be in the same VPC if their network type is VPC.
|
|
12867
|
+
* * If the network type of the scaling group is VPC, the network type of the CLB instance is classic network, and the vServer groups of the CLB instance contain instances of the VPC network type, the instances and the scaling group must be in the same VPC.
|
|
12868
|
+
* * The vServer group that you want to attach to your scaling group must belong to the CLB instance.
|
|
12869
|
+
* * You can attach only a limited number of vServer groups to a scaling group. For information about the quota on vServer groups, see [Limits](https://help.aliyun.com/document_detail/25863.html).
|
|
12870
|
+
* When you call this operation, you must specify the following parameters:
|
|
12871
|
+
* * LoadBalancerId: the ID of the CLB instance.
|
|
12872
|
+
* * VServerGroupId: the ID of the vServer group.
|
|
12873
|
+
* * Port: the port number of the vServer group.
|
|
12874
|
+
* If a vServer group is attached to a scaling group by using different ports, Auto Scaling considers that more than one vServer group is attached to the scaling group. If multiple vServer groups with the same group ID and port number are specified in the request parameters, only the first vServer group is used. The other vServer groups are ignored.
|
|
12875
|
+
*
|
|
12876
|
+
* @param request AttachVServerGroupsRequest
|
|
12877
|
+
* @return AttachVServerGroupsResponse
|
|
12641
12878
|
*/
|
|
12642
12879
|
async attachVServerGroups(request) {
|
|
12643
12880
|
let runtime = new $Util.RuntimeOptions({});
|
|
12644
12881
|
return await this.attachVServerGroupsWithOptions(request, runtime);
|
|
12645
12882
|
}
|
|
12883
|
+
/**
|
|
12884
|
+
* @summary Adds a scaling group to a resource group.
|
|
12885
|
+
*
|
|
12886
|
+
* @param request ChangeResourceGroupRequest
|
|
12887
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
12888
|
+
* @return ChangeResourceGroupResponse
|
|
12889
|
+
*/
|
|
12646
12890
|
async changeResourceGroupWithOptions(request, runtime) {
|
|
12647
12891
|
tea_util_1.default.validateModel(request);
|
|
12648
12892
|
let query = {};
|
|
@@ -12680,16 +12924,24 @@ class Client extends openapi_client_1.default {
|
|
|
12680
12924
|
});
|
|
12681
12925
|
return $tea.cast(await this.callApi(params, req, runtime), new ChangeResourceGroupResponse({}));
|
|
12682
12926
|
}
|
|
12927
|
+
/**
|
|
12928
|
+
* @summary Adds a scaling group to a resource group.
|
|
12929
|
+
*
|
|
12930
|
+
* @param request ChangeResourceGroupRequest
|
|
12931
|
+
* @return ChangeResourceGroupResponse
|
|
12932
|
+
*/
|
|
12683
12933
|
async changeResourceGroup(request) {
|
|
12684
12934
|
let runtime = new $Util.RuntimeOptions({});
|
|
12685
12935
|
return await this.changeResourceGroupWithOptions(request, runtime);
|
|
12686
12936
|
}
|
|
12687
12937
|
/**
|
|
12688
|
-
|
|
12689
|
-
|
|
12690
|
-
|
|
12691
|
-
|
|
12692
|
-
|
|
12938
|
+
* @summary Ends the timeout period of a lifecycle hook ahead of schedule. If you have created a lifecycle hook for your scaling group, you can call the CompleteLifecycleAction operation to end the timeout period of the lifecycle hook ahead of schedule based on your business requirements.
|
|
12939
|
+
*
|
|
12940
|
+
* @description When you manually cut short the timeout period of a lifecycle hook, Auto Scaling proceeds with one of the following actions based on the predefined settings: responding to the scaling request, aborting the scaling request, and initiating a rollback process.
|
|
12941
|
+
*
|
|
12942
|
+
* @param request CompleteLifecycleActionRequest
|
|
12943
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
12944
|
+
* @return CompleteLifecycleActionResponse
|
|
12693
12945
|
*/
|
|
12694
12946
|
async completeLifecycleActionWithOptions(request, runtime) {
|
|
12695
12947
|
tea_util_1.default.validateModel(request);
|
|
@@ -12735,15 +12987,30 @@ class Client extends openapi_client_1.default {
|
|
|
12735
12987
|
return $tea.cast(await this.callApi(params, req, runtime), new CompleteLifecycleActionResponse({}));
|
|
12736
12988
|
}
|
|
12737
12989
|
/**
|
|
12738
|
-
|
|
12739
|
-
|
|
12740
|
-
|
|
12741
|
-
|
|
12990
|
+
* @summary Ends the timeout period of a lifecycle hook ahead of schedule. If you have created a lifecycle hook for your scaling group, you can call the CompleteLifecycleAction operation to end the timeout period of the lifecycle hook ahead of schedule based on your business requirements.
|
|
12991
|
+
*
|
|
12992
|
+
* @description When you manually cut short the timeout period of a lifecycle hook, Auto Scaling proceeds with one of the following actions based on the predefined settings: responding to the scaling request, aborting the scaling request, and initiating a rollback process.
|
|
12993
|
+
*
|
|
12994
|
+
* @param request CompleteLifecycleActionRequest
|
|
12995
|
+
* @return CompleteLifecycleActionResponse
|
|
12742
12996
|
*/
|
|
12743
12997
|
async completeLifecycleAction(request) {
|
|
12744
12998
|
let runtime = new $Util.RuntimeOptions({});
|
|
12745
12999
|
return await this.completeLifecycleActionWithOptions(request, runtime);
|
|
12746
13000
|
}
|
|
13001
|
+
/**
|
|
13002
|
+
* @summary Creates an event-triggered task.
|
|
13003
|
+
*
|
|
13004
|
+
* @description * If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using custom metrics. For more information, see [Custom monitoring event-triggered tasks](https://help.aliyun.com/document_detail/74861.html).
|
|
13005
|
+
* * When you create an event-triggered task, you must specify the MetricName, DimensionKey, and DimensionValue parameters to determine the range of statistics that you want to aggregate for the metrics of the scaling group. For example, you can specify the user_id and scaling_group dimensions for an event-triggered task to aggregate monitoring data of all Elastic Compute Service (ECS) instances or elastic container instances in a scaling group within an Alibaba Cloud account.
|
|
13006
|
+
* * If you set the MetricType parameter to custom, the valid values are your custom metrics.
|
|
13007
|
+
* * For information about the supported metrics when you set the MetricType parameter to system, see [Event-triggered task for system monitoring](https://help.aliyun.com/document_detail/74854.html).
|
|
13008
|
+
* > The user_id and scaling_group dimensions are automatically populated. You need to only specify the device and state dimensions. For more information, see the `DimensionKey` and `DimensionValue` parameters in the "Request parameters" section of this topic.
|
|
13009
|
+
*
|
|
13010
|
+
* @param request CreateAlarmRequest
|
|
13011
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
13012
|
+
* @return CreateAlarmResponse
|
|
13013
|
+
*/
|
|
12747
13014
|
async createAlarmWithOptions(request, runtime) {
|
|
12748
13015
|
tea_util_1.default.validateModel(request);
|
|
12749
13016
|
let query = {};
|
|
@@ -12820,17 +13087,31 @@ class Client extends openapi_client_1.default {
|
|
|
12820
13087
|
});
|
|
12821
13088
|
return $tea.cast(await this.callApi(params, req, runtime), new CreateAlarmResponse({}));
|
|
12822
13089
|
}
|
|
13090
|
+
/**
|
|
13091
|
+
* @summary Creates an event-triggered task.
|
|
13092
|
+
*
|
|
13093
|
+
* @description * If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using custom metrics. For more information, see [Custom monitoring event-triggered tasks](https://help.aliyun.com/document_detail/74861.html).
|
|
13094
|
+
* * When you create an event-triggered task, you must specify the MetricName, DimensionKey, and DimensionValue parameters to determine the range of statistics that you want to aggregate for the metrics of the scaling group. For example, you can specify the user_id and scaling_group dimensions for an event-triggered task to aggregate monitoring data of all Elastic Compute Service (ECS) instances or elastic container instances in a scaling group within an Alibaba Cloud account.
|
|
13095
|
+
* * If you set the MetricType parameter to custom, the valid values are your custom metrics.
|
|
13096
|
+
* * For information about the supported metrics when you set the MetricType parameter to system, see [Event-triggered task for system monitoring](https://help.aliyun.com/document_detail/74854.html).
|
|
13097
|
+
* > The user_id and scaling_group dimensions are automatically populated. You need to only specify the device and state dimensions. For more information, see the `DimensionKey` and `DimensionValue` parameters in the "Request parameters" section of this topic.
|
|
13098
|
+
*
|
|
13099
|
+
* @param request CreateAlarmRequest
|
|
13100
|
+
* @return CreateAlarmResponse
|
|
13101
|
+
*/
|
|
12823
13102
|
async createAlarm(request) {
|
|
12824
13103
|
let runtime = new $Util.RuntimeOptions({});
|
|
12825
13104
|
return await this.createAlarmWithOptions(request, runtime);
|
|
12826
13105
|
}
|
|
12827
13106
|
/**
|
|
12828
|
-
|
|
12829
|
-
|
|
12830
|
-
|
|
12831
|
-
|
|
12832
|
-
|
|
12833
|
-
|
|
13107
|
+
* @summary Creates a scaling configuration of the Elastic Container Instance type. Auto Scaling uses the scaling configuration as a template to create elastic container instances to meet your business requirements during scale-outs.
|
|
13108
|
+
*
|
|
13109
|
+
* @description A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
|
|
13110
|
+
* You can specify the Cpu and Memory parameters to determine the range of instance types. If you specify the parameters, Auto Scaling determines the available instance types based on factors such as I/O optimization requirements and zones. Auto Scaling preferentially creates elastic container instances of the instance type that is provided at the lowest price. This scaling mode is available only if Scaling Policy is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
|
|
13111
|
+
*
|
|
13112
|
+
* @param request CreateEciScalingConfigurationRequest
|
|
13113
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
13114
|
+
* @return CreateEciScalingConfigurationResponse
|
|
12834
13115
|
*/
|
|
12835
13116
|
async createEciScalingConfigurationWithOptions(request, runtime) {
|
|
12836
13117
|
tea_util_1.default.validateModel(request);
|
|
@@ -12999,25 +13280,29 @@ class Client extends openapi_client_1.default {
|
|
|
12999
13280
|
return $tea.cast(await this.callApi(params, req, runtime), new CreateEciScalingConfigurationResponse({}));
|
|
13000
13281
|
}
|
|
13001
13282
|
/**
|
|
13002
|
-
|
|
13003
|
-
|
|
13004
|
-
|
|
13005
|
-
|
|
13006
|
-
|
|
13283
|
+
* @summary Creates a scaling configuration of the Elastic Container Instance type. Auto Scaling uses the scaling configuration as a template to create elastic container instances to meet your business requirements during scale-outs.
|
|
13284
|
+
*
|
|
13285
|
+
* @description A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
|
|
13286
|
+
* You can specify the Cpu and Memory parameters to determine the range of instance types. If you specify the parameters, Auto Scaling determines the available instance types based on factors such as I/O optimization requirements and zones. Auto Scaling preferentially creates elastic container instances of the instance type that is provided at the lowest price. This scaling mode is available only if Scaling Policy is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
|
|
13287
|
+
*
|
|
13288
|
+
* @param request CreateEciScalingConfigurationRequest
|
|
13289
|
+
* @return CreateEciScalingConfigurationResponse
|
|
13007
13290
|
*/
|
|
13008
13291
|
async createEciScalingConfiguration(request) {
|
|
13009
13292
|
let runtime = new $Util.RuntimeOptions({});
|
|
13010
13293
|
return await this.createEciScalingConfigurationWithOptions(request, runtime);
|
|
13011
13294
|
}
|
|
13012
13295
|
/**
|
|
13013
|
-
|
|
13014
|
-
|
|
13015
|
-
|
|
13016
|
-
|
|
13017
|
-
|
|
13018
|
-
|
|
13019
|
-
|
|
13020
|
-
|
|
13296
|
+
* @summary Creates one or more lifecycle hooks.
|
|
13297
|
+
*
|
|
13298
|
+
* @description You can create up to six lifecycle hooks for each scaling group. After a lifecycle hook is created for a scaling group, Elastic Compute Service (ECS) instances in the scaling group waits to be added to or removed from the scaling group during scaling activities. You can use the HeartbeatTimeout parameter to specify the timeout period of the lifecycle hook. During the timeout period of a lifecycle hook, you can perform custom operations such as initialize ECS instance configurations and download ECS instance data on the ECS instances for which the lifecycle hook is applied.
|
|
13299
|
+
* During a scale-out activity and the timeout period of a lifecycle hook, the private IP addresses of ECS instances wait to be added to the associated whitelist that manages access to the ApsaraDB RDS instance. The ECS instances also wait to be added to the backend server group of the associated Classic Load Balancer (CLB) instance. After the lifecycle hook times out, the private IP addresses of the ECS instances are added to the whitelist that manages access to the associated ApsaraDB RDS instance. The ECS instances are also added to the backend server group of the associated CLB instance. During a scale-in activity and the timeout period of a lifecycle hook, the private IP addresses of ECS instances wait to be removed from the whitelist that manages access to the associated ApsaraDB RDS instance. The ECS instances also wait to be removed from the backend server group of the associated CLB instance. After the lifecycle hook times out, the private IP addresses of the ECS instances are removed from the whitelist that manages access to the associated ApsaraDB RDS instance. The ECS instances are also removed from the backend server group of the associated CLB instance.
|
|
13300
|
+
* You can configure a notification method for a lifecycle hook. When the lifecycle hook is triggered, a notification can be sent to the specified Message Service (MNS) topic or queue, or an operation can be performed based on the specified Operation Orchestration Service (OOS) template. If you want to configure an OOS template, you must create a Resource Access Management (RAM) role for OOS. For more information, see [Grant RAM permissions to OOS](https://help.aliyun.com/document_detail/120810.html).
|
|
13301
|
+
* > If your scaling group has existing ECS instances and you configured an OOS template that is used to add the private IP addresses of ECS instances to or remove the private IP addresses of ECS instances from the whitelists that manage access to cloud databases that are not ApsaraDB RDS databases, you must manually add the private IP addresses of the ECS instances to or remove the private IP addresses of the ECS instances from the whitelists that manage access to the cloud databases.
|
|
13302
|
+
*
|
|
13303
|
+
* @param request CreateLifecycleHookRequest
|
|
13304
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
13305
|
+
* @return CreateLifecycleHookResponse
|
|
13021
13306
|
*/
|
|
13022
13307
|
async createLifecycleHookWithOptions(request, runtime) {
|
|
13023
13308
|
tea_util_1.default.validateModel(request);
|
|
@@ -13069,25 +13354,29 @@ class Client extends openapi_client_1.default {
|
|
|
13069
13354
|
return $tea.cast(await this.callApi(params, req, runtime), new CreateLifecycleHookResponse({}));
|
|
13070
13355
|
}
|
|
13071
13356
|
/**
|
|
13072
|
-
|
|
13073
|
-
|
|
13074
|
-
|
|
13075
|
-
|
|
13076
|
-
|
|
13077
|
-
|
|
13078
|
-
|
|
13357
|
+
* @summary Creates one or more lifecycle hooks.
|
|
13358
|
+
*
|
|
13359
|
+
* @description You can create up to six lifecycle hooks for each scaling group. After a lifecycle hook is created for a scaling group, Elastic Compute Service (ECS) instances in the scaling group waits to be added to or removed from the scaling group during scaling activities. You can use the HeartbeatTimeout parameter to specify the timeout period of the lifecycle hook. During the timeout period of a lifecycle hook, you can perform custom operations such as initialize ECS instance configurations and download ECS instance data on the ECS instances for which the lifecycle hook is applied.
|
|
13360
|
+
* During a scale-out activity and the timeout period of a lifecycle hook, the private IP addresses of ECS instances wait to be added to the associated whitelist that manages access to the ApsaraDB RDS instance. The ECS instances also wait to be added to the backend server group of the associated Classic Load Balancer (CLB) instance. After the lifecycle hook times out, the private IP addresses of the ECS instances are added to the whitelist that manages access to the associated ApsaraDB RDS instance. The ECS instances are also added to the backend server group of the associated CLB instance. During a scale-in activity and the timeout period of a lifecycle hook, the private IP addresses of ECS instances wait to be removed from the whitelist that manages access to the associated ApsaraDB RDS instance. The ECS instances also wait to be removed from the backend server group of the associated CLB instance. After the lifecycle hook times out, the private IP addresses of the ECS instances are removed from the whitelist that manages access to the associated ApsaraDB RDS instance. The ECS instances are also removed from the backend server group of the associated CLB instance.
|
|
13361
|
+
* You can configure a notification method for a lifecycle hook. When the lifecycle hook is triggered, a notification can be sent to the specified Message Service (MNS) topic or queue, or an operation can be performed based on the specified Operation Orchestration Service (OOS) template. If you want to configure an OOS template, you must create a Resource Access Management (RAM) role for OOS. For more information, see [Grant RAM permissions to OOS](https://help.aliyun.com/document_detail/120810.html).
|
|
13362
|
+
* > If your scaling group has existing ECS instances and you configured an OOS template that is used to add the private IP addresses of ECS instances to or remove the private IP addresses of ECS instances from the whitelists that manage access to cloud databases that are not ApsaraDB RDS databases, you must manually add the private IP addresses of the ECS instances to or remove the private IP addresses of the ECS instances from the whitelists that manage access to the cloud databases.
|
|
13363
|
+
*
|
|
13364
|
+
* @param request CreateLifecycleHookRequest
|
|
13365
|
+
* @return CreateLifecycleHookResponse
|
|
13079
13366
|
*/
|
|
13080
13367
|
async createLifecycleHook(request) {
|
|
13081
13368
|
let runtime = new $Util.RuntimeOptions({});
|
|
13082
13369
|
return await this.createLifecycleHookWithOptions(request, runtime);
|
|
13083
13370
|
}
|
|
13084
13371
|
/**
|
|
13085
|
-
|
|
13086
|
-
|
|
13087
|
-
|
|
13088
|
-
|
|
13089
|
-
|
|
13090
|
-
|
|
13372
|
+
* @summary Creates a notification rule. You can call the CreateNotificationConfiguration operation to create a notification rule to stay informed about scaling events or resource changes. This helps you learn about the dynamic status of your scaling group in real time and further automates the management of scaling events.
|
|
13373
|
+
*
|
|
13374
|
+
* @description ## Description
|
|
13375
|
+
* You can configure CloudMonitor system events, Message Service (MNS) queues, or MNS topics to receive notifications. When a specified type of scaling activity or resource change occurs in a scaling group, Auto Scaling sends notifications by using CloudMonitor or MNS.
|
|
13376
|
+
*
|
|
13377
|
+
* @param request CreateNotificationConfigurationRequest
|
|
13378
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
13379
|
+
* @return CreateNotificationConfigurationResponse
|
|
13091
13380
|
*/
|
|
13092
13381
|
async createNotificationConfigurationWithOptions(request, runtime) {
|
|
13093
13382
|
tea_util_1.default.validateModel(request);
|
|
@@ -13127,28 +13416,32 @@ class Client extends openapi_client_1.default {
|
|
|
13127
13416
|
return $tea.cast(await this.callApi(params, req, runtime), new CreateNotificationConfigurationResponse({}));
|
|
13128
13417
|
}
|
|
13129
13418
|
/**
|
|
13130
|
-
|
|
13131
|
-
|
|
13132
|
-
|
|
13133
|
-
|
|
13134
|
-
|
|
13419
|
+
* @summary Creates a notification rule. You can call the CreateNotificationConfiguration operation to create a notification rule to stay informed about scaling events or resource changes. This helps you learn about the dynamic status of your scaling group in real time and further automates the management of scaling events.
|
|
13420
|
+
*
|
|
13421
|
+
* @description ## Description
|
|
13422
|
+
* You can configure CloudMonitor system events, Message Service (MNS) queues, or MNS topics to receive notifications. When a specified type of scaling activity or resource change occurs in a scaling group, Auto Scaling sends notifications by using CloudMonitor or MNS.
|
|
13423
|
+
*
|
|
13424
|
+
* @param request CreateNotificationConfigurationRequest
|
|
13425
|
+
* @return CreateNotificationConfigurationResponse
|
|
13135
13426
|
*/
|
|
13136
13427
|
async createNotificationConfiguration(request) {
|
|
13137
13428
|
let runtime = new $Util.RuntimeOptions({});
|
|
13138
13429
|
return await this.createNotificationConfigurationWithOptions(request, runtime);
|
|
13139
13430
|
}
|
|
13140
13431
|
/**
|
|
13141
|
-
|
|
13142
|
-
|
|
13143
|
-
|
|
13144
|
-
|
|
13145
|
-
|
|
13146
|
-
|
|
13147
|
-
|
|
13148
|
-
|
|
13149
|
-
|
|
13150
|
-
|
|
13151
|
-
|
|
13432
|
+
* @summary Creates a scaling configuration.
|
|
13433
|
+
*
|
|
13434
|
+
* @description Auto Scaling automatically creates Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be created in the following modes:
|
|
13435
|
+
* * InstancePatternInfos: intelligent configuration mode. In this mode, you need to only specify the number of vCPUs, memory size, instance family, and maximum price. Auto Scaling selects the instance type that has the lowest price based on the configurations to create ECS instances. This mode is available only for scaling groups that reside in virtual private clouds (VPCs). This mode reduces scale-out failures caused by insufficient inventory of instance types.
|
|
13436
|
+
* * InstanceType: In this mode, you must specify one instance type.
|
|
13437
|
+
* * InstanceTypes: In this mode, you can specify more than one instance type.
|
|
13438
|
+
* * InstanceTypeOverrides: In this mode, you can specify multiple instance types and weights for the instance types.
|
|
13439
|
+
* * Cpu and Memory: In this mode, you must specify the number of vCPUs and the memory size. Auto Scaling determines the range of available instance types based on factors such as I/O optimization requirements and zones. Then, Auto Scaling creates ECS instances by using the lowest-priced instance type. This mode is available only if Scaling Policy is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
|
|
13440
|
+
* > You cannot specify InstanceType, InstanceTypes, InstanceTypeOverrides, and Cpu and Memory at the same time. You can specify InstanceType and InstancePatternInfos or specify InstanceTypes and InstancePatternInfo at the same time. If you specify InstanceType and InstancePatternInfos or specify InstanceTypes and InstancePatternInfos at the same time, Auto Scaling preferentially uses the instance types that are specified by InstanceType or InstanceTypes for scale-outs. If the instance types that are specified by InstanceType or InstanceTypes do not have sufficient inventory, Auto Scaling uses the instance types that are specified by InstancePatternInfos for scale-outs.
|
|
13441
|
+
*
|
|
13442
|
+
* @param tmpReq CreateScalingConfigurationRequest
|
|
13443
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
13444
|
+
* @return CreateScalingConfigurationResponse
|
|
13152
13445
|
*/
|
|
13153
13446
|
async createScalingConfigurationWithOptions(tmpReq, runtime) {
|
|
13154
13447
|
tea_util_1.default.validateModel(tmpReq);
|
|
@@ -13346,48 +13639,52 @@ class Client extends openapi_client_1.default {
|
|
|
13346
13639
|
return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingConfigurationResponse({}));
|
|
13347
13640
|
}
|
|
13348
13641
|
/**
|
|
13349
|
-
|
|
13350
|
-
|
|
13351
|
-
|
|
13352
|
-
|
|
13353
|
-
|
|
13354
|
-
|
|
13355
|
-
|
|
13356
|
-
|
|
13357
|
-
|
|
13358
|
-
|
|
13642
|
+
* @summary Creates a scaling configuration.
|
|
13643
|
+
*
|
|
13644
|
+
* @description Auto Scaling automatically creates Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be created in the following modes:
|
|
13645
|
+
* * InstancePatternInfos: intelligent configuration mode. In this mode, you need to only specify the number of vCPUs, memory size, instance family, and maximum price. Auto Scaling selects the instance type that has the lowest price based on the configurations to create ECS instances. This mode is available only for scaling groups that reside in virtual private clouds (VPCs). This mode reduces scale-out failures caused by insufficient inventory of instance types.
|
|
13646
|
+
* * InstanceType: In this mode, you must specify one instance type.
|
|
13647
|
+
* * InstanceTypes: In this mode, you can specify more than one instance type.
|
|
13648
|
+
* * InstanceTypeOverrides: In this mode, you can specify multiple instance types and weights for the instance types.
|
|
13649
|
+
* * Cpu and Memory: In this mode, you must specify the number of vCPUs and the memory size. Auto Scaling determines the range of available instance types based on factors such as I/O optimization requirements and zones. Then, Auto Scaling creates ECS instances by using the lowest-priced instance type. This mode is available only if Scaling Policy is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
|
|
13650
|
+
* > You cannot specify InstanceType, InstanceTypes, InstanceTypeOverrides, and Cpu and Memory at the same time. You can specify InstanceType and InstancePatternInfos or specify InstanceTypes and InstancePatternInfo at the same time. If you specify InstanceType and InstancePatternInfos or specify InstanceTypes and InstancePatternInfos at the same time, Auto Scaling preferentially uses the instance types that are specified by InstanceType or InstanceTypes for scale-outs. If the instance types that are specified by InstanceType or InstanceTypes do not have sufficient inventory, Auto Scaling uses the instance types that are specified by InstancePatternInfos for scale-outs.
|
|
13651
|
+
*
|
|
13652
|
+
* @param request CreateScalingConfigurationRequest
|
|
13653
|
+
* @return CreateScalingConfigurationResponse
|
|
13359
13654
|
*/
|
|
13360
13655
|
async createScalingConfiguration(request) {
|
|
13361
13656
|
let runtime = new $Util.RuntimeOptions({});
|
|
13362
13657
|
return await this.createScalingConfigurationWithOptions(request, runtime);
|
|
13363
13658
|
}
|
|
13364
13659
|
/**
|
|
13365
|
-
|
|
13366
|
-
|
|
13367
|
-
|
|
13368
|
-
|
|
13369
|
-
|
|
13370
|
-
|
|
13371
|
-
|
|
13372
|
-
|
|
13373
|
-
|
|
13374
|
-
|
|
13375
|
-
|
|
13376
|
-
|
|
13377
|
-
|
|
13378
|
-
|
|
13379
|
-
|
|
13380
|
-
|
|
13381
|
-
|
|
13382
|
-
|
|
13383
|
-
|
|
13384
|
-
|
|
13385
|
-
|
|
13386
|
-
|
|
13387
|
-
|
|
13388
|
-
|
|
13389
|
-
|
|
13390
|
-
|
|
13660
|
+
* @summary Creates a scaling group.
|
|
13661
|
+
*
|
|
13662
|
+
* @description A scaling group is a group of Elastic Compute Service (ECS) instances that can be used in similar business scenarios.
|
|
13663
|
+
* You can create only a limited number of scaling groups in a region. Go to Quota Center to check the quota of the scaling groups.
|
|
13664
|
+
* A scaling group does not immediately take effect after you create the scaling group. You must call the EnableScalingGroup operation to enable the scaling group. After you enable the scaling group, Auto Scaling can execute scaling rules to trigger scaling activities in the scaling group.
|
|
13665
|
+
* The Classic Load Balancer (CLB) instances and ApsaraDB RDS instances that you want to associate with a scaling group must reside in the same region as the scaling group. CLB instances are formerly known as Server Load Balancer (SLB) instances. For more information, see the [Regions and zones](https://help.aliyun.com/document_detail/40654.html) topic.
|
|
13666
|
+
* If you associate a CLB instance when you create a scaling group, Auto Scaling automatically adds ECS instances in the scaling group to the backend server group of the associated CLB instance. You can specify a server group to which ECS instances can be added. You can add ECS instances to the following types of server groups:
|
|
13667
|
+
* * Default server group: a group of ECS instances that are used to receive requests. If you do not specify a vServer group or a primary/secondary server group for a listener, requests are forwarded to the ECS instances in the default server group.
|
|
13668
|
+
* * vServer group: If you want to forward requests to backend servers that are not in the default server group or configure domain name-based or URL-based forwarding rules, you can use vServer groups.
|
|
13669
|
+
* > If you specify the default server group and multiple vServer groups at the same time, ECS instances are added to all specified server groups.
|
|
13670
|
+
* The default weight of an ECS instance that is added as a backend server of a CLB instance is 50. The CLB instance that you want to associate with your scaling group must meet the following requirements:
|
|
13671
|
+
* * The CLB instance must be in the Active state. You can call the DescribeLoadBalancers operation to query the state of the CLB instance.
|
|
13672
|
+
* * The health check feature must be enabled on all listener ports that are configured for the CLB instance. Otherwise, the scaling group fails to be created.
|
|
13673
|
+
* If you associate an Application Load Balancer (ALB) server group with a scaling group, Auto Scaling automatically adds ECS instances that are in the scaling group to the ALB server group to process requests distributed by the ALB instance to which the ALB server group belongs. You can specify multiple ALB server groups. The server groups must reside in the same virtual private cloud (VPC) as the scaling group. For more information, see the "AttachAlbServerGroups" topic.
|
|
13674
|
+
* If you associate an ApsaraDB RDS instance with a scaling group, Auto Scaling automatically adds the private IP addresses of the ECS instances in the scaling group to the IP address whitelist of the ApsaraDB RDS instance. The ApsaraDB RDS instance that you want to associate with your scaling group must meet the following requirements:
|
|
13675
|
+
* * The ApsaraDB RDS instance must be in the Running state. You can call the DescribeDBInstances operation to query the state of the ApsaraDB RDS instance.
|
|
13676
|
+
* * The number of IP addresses in the IP address whitelist of the ApsaraDB RDS instance cannot exceed the upper limit. For more information, see the "Configure whitelists" topic.
|
|
13677
|
+
* If you set the MultiAZPolicy parameter of the scaling group to COST_OPTIMIZED, take note of the following items:
|
|
13678
|
+
* * You can use the OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, and SpotInstancePools parameters to specify the instance allocation method based on the cost optimization policy. This instance allocation method is prioritized during scaling.
|
|
13679
|
+
* * If you do not specify the OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, or SpotInstancePools parameter, the instance types that are provided at the lowest price are used to create instances based on the cost optimization policy.
|
|
13680
|
+
* If you set the `Tags.Propagate` parameter of the scaling group to true, the following rules apply:
|
|
13681
|
+
* * Tags that you add to the scaling group cannot be propagated to existing instances in the scaling group. Tags that you add to the scaling group are propagated to only new instances.
|
|
13682
|
+
* * If you specify instance tags in the scaling configuration that is used to create instances and propagate the tags that you add to the scaling group to the instances, all tags exist at the same time.
|
|
13683
|
+
* * If the tag key that you specify in a scaling configuration and the tag key that you add to the scaling group of the scaling configuration are the same, the tag value that you specify in the scaling configuration is preferentially used.
|
|
13684
|
+
*
|
|
13685
|
+
* @param request CreateScalingGroupRequest
|
|
13686
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
13687
|
+
* @return CreateScalingGroupResponse
|
|
13391
13688
|
*/
|
|
13392
13689
|
async createScalingGroupWithOptions(request, runtime) {
|
|
13393
13690
|
tea_util_1.default.validateModel(request);
|
|
@@ -13544,54 +13841,58 @@ class Client extends openapi_client_1.default {
|
|
|
13544
13841
|
return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingGroupResponse({}));
|
|
13545
13842
|
}
|
|
13546
13843
|
/**
|
|
13547
|
-
|
|
13548
|
-
|
|
13549
|
-
|
|
13550
|
-
|
|
13551
|
-
|
|
13552
|
-
|
|
13553
|
-
|
|
13554
|
-
|
|
13555
|
-
|
|
13556
|
-
|
|
13557
|
-
|
|
13558
|
-
|
|
13559
|
-
|
|
13560
|
-
|
|
13561
|
-
|
|
13562
|
-
|
|
13563
|
-
|
|
13564
|
-
|
|
13565
|
-
|
|
13566
|
-
|
|
13567
|
-
|
|
13568
|
-
|
|
13569
|
-
|
|
13570
|
-
|
|
13571
|
-
|
|
13844
|
+
* @summary Creates a scaling group.
|
|
13845
|
+
*
|
|
13846
|
+
* @description A scaling group is a group of Elastic Compute Service (ECS) instances that can be used in similar business scenarios.
|
|
13847
|
+
* You can create only a limited number of scaling groups in a region. Go to Quota Center to check the quota of the scaling groups.
|
|
13848
|
+
* A scaling group does not immediately take effect after you create the scaling group. You must call the EnableScalingGroup operation to enable the scaling group. After you enable the scaling group, Auto Scaling can execute scaling rules to trigger scaling activities in the scaling group.
|
|
13849
|
+
* The Classic Load Balancer (CLB) instances and ApsaraDB RDS instances that you want to associate with a scaling group must reside in the same region as the scaling group. CLB instances are formerly known as Server Load Balancer (SLB) instances. For more information, see the [Regions and zones](https://help.aliyun.com/document_detail/40654.html) topic.
|
|
13850
|
+
* If you associate a CLB instance when you create a scaling group, Auto Scaling automatically adds ECS instances in the scaling group to the backend server group of the associated CLB instance. You can specify a server group to which ECS instances can be added. You can add ECS instances to the following types of server groups:
|
|
13851
|
+
* * Default server group: a group of ECS instances that are used to receive requests. If you do not specify a vServer group or a primary/secondary server group for a listener, requests are forwarded to the ECS instances in the default server group.
|
|
13852
|
+
* * vServer group: If you want to forward requests to backend servers that are not in the default server group or configure domain name-based or URL-based forwarding rules, you can use vServer groups.
|
|
13853
|
+
* > If you specify the default server group and multiple vServer groups at the same time, ECS instances are added to all specified server groups.
|
|
13854
|
+
* The default weight of an ECS instance that is added as a backend server of a CLB instance is 50. The CLB instance that you want to associate with your scaling group must meet the following requirements:
|
|
13855
|
+
* * The CLB instance must be in the Active state. You can call the DescribeLoadBalancers operation to query the state of the CLB instance.
|
|
13856
|
+
* * The health check feature must be enabled on all listener ports that are configured for the CLB instance. Otherwise, the scaling group fails to be created.
|
|
13857
|
+
* If you associate an Application Load Balancer (ALB) server group with a scaling group, Auto Scaling automatically adds ECS instances that are in the scaling group to the ALB server group to process requests distributed by the ALB instance to which the ALB server group belongs. You can specify multiple ALB server groups. The server groups must reside in the same virtual private cloud (VPC) as the scaling group. For more information, see the "AttachAlbServerGroups" topic.
|
|
13858
|
+
* If you associate an ApsaraDB RDS instance with a scaling group, Auto Scaling automatically adds the private IP addresses of the ECS instances in the scaling group to the IP address whitelist of the ApsaraDB RDS instance. The ApsaraDB RDS instance that you want to associate with your scaling group must meet the following requirements:
|
|
13859
|
+
* * The ApsaraDB RDS instance must be in the Running state. You can call the DescribeDBInstances operation to query the state of the ApsaraDB RDS instance.
|
|
13860
|
+
* * The number of IP addresses in the IP address whitelist of the ApsaraDB RDS instance cannot exceed the upper limit. For more information, see the "Configure whitelists" topic.
|
|
13861
|
+
* If you set the MultiAZPolicy parameter of the scaling group to COST_OPTIMIZED, take note of the following items:
|
|
13862
|
+
* * You can use the OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, and SpotInstancePools parameters to specify the instance allocation method based on the cost optimization policy. This instance allocation method is prioritized during scaling.
|
|
13863
|
+
* * If you do not specify the OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, or SpotInstancePools parameter, the instance types that are provided at the lowest price are used to create instances based on the cost optimization policy.
|
|
13864
|
+
* If you set the `Tags.Propagate` parameter of the scaling group to true, the following rules apply:
|
|
13865
|
+
* * Tags that you add to the scaling group cannot be propagated to existing instances in the scaling group. Tags that you add to the scaling group are propagated to only new instances.
|
|
13866
|
+
* * If you specify instance tags in the scaling configuration that is used to create instances and propagate the tags that you add to the scaling group to the instances, all tags exist at the same time.
|
|
13867
|
+
* * If the tag key that you specify in a scaling configuration and the tag key that you add to the scaling group of the scaling configuration are the same, the tag value that you specify in the scaling configuration is preferentially used.
|
|
13868
|
+
*
|
|
13869
|
+
* @param request CreateScalingGroupRequest
|
|
13870
|
+
* @return CreateScalingGroupResponse
|
|
13572
13871
|
*/
|
|
13573
13872
|
async createScalingGroup(request) {
|
|
13574
13873
|
let runtime = new $Util.RuntimeOptions({});
|
|
13575
13874
|
return await this.createScalingGroupWithOptions(request, runtime);
|
|
13576
13875
|
}
|
|
13577
13876
|
/**
|
|
13578
|
-
|
|
13579
|
-
|
|
13580
|
-
|
|
13581
|
-
|
|
13582
|
-
|
|
13583
|
-
|
|
13584
|
-
|
|
13585
|
-
|
|
13586
|
-
|
|
13587
|
-
|
|
13588
|
-
|
|
13589
|
-
|
|
13590
|
-
|
|
13591
|
-
|
|
13592
|
-
|
|
13593
|
-
|
|
13594
|
-
|
|
13877
|
+
* @summary Creates a scaling rule.
|
|
13878
|
+
*
|
|
13879
|
+
* @description ## Description
|
|
13880
|
+
* A scaling rule defines a specific scaling activity, such as adding or removing N instances. If the number of Elastic Compute Service (ECS) instances in a scaling group is less than the minimum number allowed or greater than the maximum number allowed after a scaling rule is executed, Auto Scaling adjusts the number of ECS instances that you want to add or remove. This way, the number of ECS instances can be maintained within the valid range after the scaling rule is executed. The number of ECS instances that is specified in the scaling rule remains unchanged. Example:
|
|
13881
|
+
* * If your scaling group contains two ECS instances and allows up to three ECS instances, only one ECS instance is added to your scaling group after you execute a scale-out rule in which three ECS instances are specified. The number of ECS instances that is specified in the scaling rule remains unchanged.
|
|
13882
|
+
* * If your scaling group contains three ECS instances and requires at least two ECS instances, only one ECS instance is removed from your scaling group after you execute a scale-in rule in which five ECS instances are specified. The number of ECS instances that is specified in the scaling rule remains unchanged.
|
|
13883
|
+
* Before you call this operation, take note of the following items:
|
|
13884
|
+
* * If you set the AdjustmentType parameter to TotalCapacity, the number of ECS instances in the scaling group is adjusted to the specified value. The value of the AdjustmentValue parameter must be greater than or equal to 0.
|
|
13885
|
+
* * If you set the AdjustmentType parameter to QuantityChangeInCapacity or PercentChangeInCapacity, a positive value of AdjustmentValue specifies the number of ECS instances that are added to the scaling group, and a negative value of AdjustmentValue specifies the number of ECS instances that are removed from the scaling group.
|
|
13886
|
+
* * If you set the AdjustmentType parameter to PercentChangeInCapacity, Auto Scaling uses the following formula to calculate a value, and then rounds the value to the nearest integer to obtain the number of ECS instances that need to be scaled: Value of TotalCapacity × Value of AdjustmentValue/100.
|
|
13887
|
+
* * If the cooldown time is specified in a scaling rule, the specified time applies to the scaling group after the rule is executed. Otherwise, the value of the DefaultCooldown parameter of the scaling group applies to the scaling group.
|
|
13888
|
+
* * You can create only a limited number of scaling rules for a scaling group. For more information, see the "Limits" topic.
|
|
13889
|
+
* * The unique identifier (ScalingRuleAri) of a scaling rule can be used by the following operations:
|
|
13890
|
+
* * ExecuteScalingRule: You can call this operation to manually execute a specific scaling rule by setting the ScalingRuleAri parameter to the unique identifier of the scaling rule.
|
|
13891
|
+
* * CreateScheduledTask: You can call this operation to create a scheduled task for a specific scaling rule by setting the ScheduledAction parameter to the unique identifier of the scaling rule.
|
|
13892
|
+
*
|
|
13893
|
+
* @param request CreateScalingRuleRequest
|
|
13894
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
13895
|
+
* @return CreateScalingRuleResponse
|
|
13595
13896
|
*/
|
|
13596
13897
|
async createScalingRuleWithOptions(request, runtime) {
|
|
13597
13898
|
tea_util_1.default.validateModel(request);
|
|
@@ -13685,38 +13986,42 @@ class Client extends openapi_client_1.default {
|
|
|
13685
13986
|
return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingRuleResponse({}));
|
|
13686
13987
|
}
|
|
13687
13988
|
/**
|
|
13688
|
-
|
|
13689
|
-
|
|
13690
|
-
|
|
13691
|
-
|
|
13692
|
-
|
|
13693
|
-
|
|
13694
|
-
|
|
13695
|
-
|
|
13696
|
-
|
|
13697
|
-
|
|
13698
|
-
|
|
13699
|
-
|
|
13700
|
-
|
|
13701
|
-
|
|
13702
|
-
|
|
13703
|
-
|
|
13989
|
+
* @summary Creates a scaling rule.
|
|
13990
|
+
*
|
|
13991
|
+
* @description ## Description
|
|
13992
|
+
* A scaling rule defines a specific scaling activity, such as adding or removing N instances. If the number of Elastic Compute Service (ECS) instances in a scaling group is less than the minimum number allowed or greater than the maximum number allowed after a scaling rule is executed, Auto Scaling adjusts the number of ECS instances that you want to add or remove. This way, the number of ECS instances can be maintained within the valid range after the scaling rule is executed. The number of ECS instances that is specified in the scaling rule remains unchanged. Example:
|
|
13993
|
+
* * If your scaling group contains two ECS instances and allows up to three ECS instances, only one ECS instance is added to your scaling group after you execute a scale-out rule in which three ECS instances are specified. The number of ECS instances that is specified in the scaling rule remains unchanged.
|
|
13994
|
+
* * If your scaling group contains three ECS instances and requires at least two ECS instances, only one ECS instance is removed from your scaling group after you execute a scale-in rule in which five ECS instances are specified. The number of ECS instances that is specified in the scaling rule remains unchanged.
|
|
13995
|
+
* Before you call this operation, take note of the following items:
|
|
13996
|
+
* * If you set the AdjustmentType parameter to TotalCapacity, the number of ECS instances in the scaling group is adjusted to the specified value. The value of the AdjustmentValue parameter must be greater than or equal to 0.
|
|
13997
|
+
* * If you set the AdjustmentType parameter to QuantityChangeInCapacity or PercentChangeInCapacity, a positive value of AdjustmentValue specifies the number of ECS instances that are added to the scaling group, and a negative value of AdjustmentValue specifies the number of ECS instances that are removed from the scaling group.
|
|
13998
|
+
* * If you set the AdjustmentType parameter to PercentChangeInCapacity, Auto Scaling uses the following formula to calculate a value, and then rounds the value to the nearest integer to obtain the number of ECS instances that need to be scaled: Value of TotalCapacity × Value of AdjustmentValue/100.
|
|
13999
|
+
* * If the cooldown time is specified in a scaling rule, the specified time applies to the scaling group after the rule is executed. Otherwise, the value of the DefaultCooldown parameter of the scaling group applies to the scaling group.
|
|
14000
|
+
* * You can create only a limited number of scaling rules for a scaling group. For more information, see the "Limits" topic.
|
|
14001
|
+
* * The unique identifier (ScalingRuleAri) of a scaling rule can be used by the following operations:
|
|
14002
|
+
* * ExecuteScalingRule: You can call this operation to manually execute a specific scaling rule by setting the ScalingRuleAri parameter to the unique identifier of the scaling rule.
|
|
14003
|
+
* * CreateScheduledTask: You can call this operation to create a scheduled task for a specific scaling rule by setting the ScheduledAction parameter to the unique identifier of the scaling rule.
|
|
14004
|
+
*
|
|
14005
|
+
* @param request CreateScalingRuleRequest
|
|
14006
|
+
* @return CreateScalingRuleResponse
|
|
13704
14007
|
*/
|
|
13705
14008
|
async createScalingRule(request) {
|
|
13706
14009
|
let runtime = new $Util.RuntimeOptions({});
|
|
13707
14010
|
return await this.createScalingRuleWithOptions(request, runtime);
|
|
13708
14011
|
}
|
|
13709
14012
|
/**
|
|
13710
|
-
|
|
13711
|
-
|
|
13712
|
-
|
|
13713
|
-
|
|
13714
|
-
|
|
13715
|
-
|
|
13716
|
-
|
|
13717
|
-
|
|
13718
|
-
|
|
13719
|
-
|
|
14013
|
+
* @summary Creates a scheduled task. A scheduled task is a type of scaling task that enables automatic execution of a specific scaling rule at a specified point in time. You can call the CreateScheduledTask operation to create a scheduled task to implement automatic scaling of computing resources. This ensures your business continuity and minimizes resource costs.
|
|
14014
|
+
*
|
|
14015
|
+
* @description * If a scheduled task fails to trigger a scaling activity due to an ongoing scaling activity in a scaling group or because the scaling group is disabled, the scheduled task is automatically retried during the period that is specified by the LaunchExpirationTime parameter. If the scheduled task still fails to trigger a scaling activity after the period ends, the task is automatically skipped.
|
|
14016
|
+
* * If multiple tasks are scheduled at similar points in time to trigger scaling activities in the same scaling group, the earliest task triggers the scaling activity first. Other tasks trigger scaling activities within their launch expiration time. Only one scaling activity can be triggered in a scaling group at a time.`` If the previous scaling activity is complete and another scheduled task attempts to trigger a scaling activity, Auto Scaling executes the scaling rule that is specified in the scheduled task and then triggers a scaling activity.``
|
|
14017
|
+
* * A scheduled task supports the following scaling methods:
|
|
14018
|
+
* * `ScheduledAction`: Specify an existing scaling rule that you want Auto Scaling to execute when the scheduled task is triggered.
|
|
14019
|
+
* * `ScalingGroupId`: Specify the minimum number, maximum number, or expected number of instances for the scaling group for which you created the scheduled task.
|
|
14020
|
+
* > You cannot specify the `ScheduledAction` and ScalingGroupId parameters at the same time.
|
|
14021
|
+
*
|
|
14022
|
+
* @param request CreateScheduledTaskRequest
|
|
14023
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14024
|
+
* @return CreateScheduledTaskResponse
|
|
13720
14025
|
*/
|
|
13721
14026
|
async createScheduledTaskWithOptions(request, runtime) {
|
|
13722
14027
|
tea_util_1.default.validateModel(request);
|
|
@@ -13789,20 +14094,31 @@ class Client extends openapi_client_1.default {
|
|
|
13789
14094
|
return $tea.cast(await this.callApi(params, req, runtime), new CreateScheduledTaskResponse({}));
|
|
13790
14095
|
}
|
|
13791
14096
|
/**
|
|
13792
|
-
|
|
13793
|
-
|
|
13794
|
-
|
|
13795
|
-
|
|
13796
|
-
|
|
13797
|
-
|
|
13798
|
-
|
|
13799
|
-
|
|
13800
|
-
|
|
14097
|
+
* @summary Creates a scheduled task. A scheduled task is a type of scaling task that enables automatic execution of a specific scaling rule at a specified point in time. You can call the CreateScheduledTask operation to create a scheduled task to implement automatic scaling of computing resources. This ensures your business continuity and minimizes resource costs.
|
|
14098
|
+
*
|
|
14099
|
+
* @description * If a scheduled task fails to trigger a scaling activity due to an ongoing scaling activity in a scaling group or because the scaling group is disabled, the scheduled task is automatically retried during the period that is specified by the LaunchExpirationTime parameter. If the scheduled task still fails to trigger a scaling activity after the period ends, the task is automatically skipped.
|
|
14100
|
+
* * If multiple tasks are scheduled at similar points in time to trigger scaling activities in the same scaling group, the earliest task triggers the scaling activity first. Other tasks trigger scaling activities within their launch expiration time. Only one scaling activity can be triggered in a scaling group at a time.`` If the previous scaling activity is complete and another scheduled task attempts to trigger a scaling activity, Auto Scaling executes the scaling rule that is specified in the scheduled task and then triggers a scaling activity.``
|
|
14101
|
+
* * A scheduled task supports the following scaling methods:
|
|
14102
|
+
* * `ScheduledAction`: Specify an existing scaling rule that you want Auto Scaling to execute when the scheduled task is triggered.
|
|
14103
|
+
* * `ScalingGroupId`: Specify the minimum number, maximum number, or expected number of instances for the scaling group for which you created the scheduled task.
|
|
14104
|
+
* > You cannot specify the `ScheduledAction` and ScalingGroupId parameters at the same time.
|
|
14105
|
+
*
|
|
14106
|
+
* @param request CreateScheduledTaskRequest
|
|
14107
|
+
* @return CreateScheduledTaskResponse
|
|
13801
14108
|
*/
|
|
13802
14109
|
async createScheduledTask(request) {
|
|
13803
14110
|
let runtime = new $Util.RuntimeOptions({});
|
|
13804
14111
|
return await this.createScheduledTaskWithOptions(request, runtime);
|
|
13805
14112
|
}
|
|
14113
|
+
/**
|
|
14114
|
+
* @summary Deactivates a scaling configuration.
|
|
14115
|
+
*
|
|
14116
|
+
* @description * You can call this operation to deactivate a scaling configuration only in a disabled scaling group.
|
|
14117
|
+
*
|
|
14118
|
+
* @param request DeactivateScalingConfigurationRequest
|
|
14119
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14120
|
+
* @return DeactivateScalingConfigurationResponse
|
|
14121
|
+
*/
|
|
13806
14122
|
async deactivateScalingConfigurationWithOptions(request, runtime) {
|
|
13807
14123
|
tea_util_1.default.validateModel(request);
|
|
13808
14124
|
let query = {};
|
|
@@ -13834,10 +14150,25 @@ class Client extends openapi_client_1.default {
|
|
|
13834
14150
|
});
|
|
13835
14151
|
return $tea.cast(await this.callApi(params, req, runtime), new DeactivateScalingConfigurationResponse({}));
|
|
13836
14152
|
}
|
|
14153
|
+
/**
|
|
14154
|
+
* @summary Deactivates a scaling configuration.
|
|
14155
|
+
*
|
|
14156
|
+
* @description * You can call this operation to deactivate a scaling configuration only in a disabled scaling group.
|
|
14157
|
+
*
|
|
14158
|
+
* @param request DeactivateScalingConfigurationRequest
|
|
14159
|
+
* @return DeactivateScalingConfigurationResponse
|
|
14160
|
+
*/
|
|
13837
14161
|
async deactivateScalingConfiguration(request) {
|
|
13838
14162
|
let runtime = new $Util.RuntimeOptions({});
|
|
13839
14163
|
return await this.deactivateScalingConfigurationWithOptions(request, runtime);
|
|
13840
14164
|
}
|
|
14165
|
+
/**
|
|
14166
|
+
* @summary Deletes an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you no longer need an event-triggered task, you can call the DeleteAlarm operation to delete it.
|
|
14167
|
+
*
|
|
14168
|
+
* @param request DeleteAlarmRequest
|
|
14169
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14170
|
+
* @return DeleteAlarmResponse
|
|
14171
|
+
*/
|
|
13841
14172
|
async deleteAlarmWithOptions(request, runtime) {
|
|
13842
14173
|
tea_util_1.default.validateModel(request);
|
|
13843
14174
|
let query = {};
|
|
@@ -13869,18 +14200,26 @@ class Client extends openapi_client_1.default {
|
|
|
13869
14200
|
});
|
|
13870
14201
|
return $tea.cast(await this.callApi(params, req, runtime), new DeleteAlarmResponse({}));
|
|
13871
14202
|
}
|
|
14203
|
+
/**
|
|
14204
|
+
* @summary Deletes an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you no longer need an event-triggered task, you can call the DeleteAlarm operation to delete it.
|
|
14205
|
+
*
|
|
14206
|
+
* @param request DeleteAlarmRequest
|
|
14207
|
+
* @return DeleteAlarmResponse
|
|
14208
|
+
*/
|
|
13872
14209
|
async deleteAlarm(request) {
|
|
13873
14210
|
let runtime = new $Util.RuntimeOptions({});
|
|
13874
14211
|
return await this.deleteAlarmWithOptions(request, runtime);
|
|
13875
14212
|
}
|
|
13876
14213
|
/**
|
|
13877
|
-
|
|
13878
|
-
|
|
13879
|
-
|
|
13880
|
-
|
|
13881
|
-
|
|
13882
|
-
|
|
13883
|
-
|
|
14214
|
+
* @summary Deletes a scaling configuration of the Elastic Container Instance type. If the scaling configuration of a scaling group is in the Inactive state and the scaling group contains no elastic container instances created from the scaling configuration, you can call the DeleteEciScalingConfiguration operation to delete the scaling configuration to free up the scaling configuration quota.
|
|
14215
|
+
*
|
|
14216
|
+
* @description You cannot call this operation to delete a scaling configuration in the following scenarios:
|
|
14217
|
+
* * The scaling configuration is in the Active state.
|
|
14218
|
+
* * The scaling group contains elastic container instances created from the scaling configuration.
|
|
14219
|
+
*
|
|
14220
|
+
* @param request DeleteEciScalingConfigurationRequest
|
|
14221
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14222
|
+
* @return DeleteEciScalingConfigurationResponse
|
|
13884
14223
|
*/
|
|
13885
14224
|
async deleteEciScalingConfigurationWithOptions(request, runtime) {
|
|
13886
14225
|
tea_util_1.default.validateModel(request);
|
|
@@ -13917,17 +14256,30 @@ class Client extends openapi_client_1.default {
|
|
|
13917
14256
|
return $tea.cast(await this.callApi(params, req, runtime), new DeleteEciScalingConfigurationResponse({}));
|
|
13918
14257
|
}
|
|
13919
14258
|
/**
|
|
13920
|
-
|
|
13921
|
-
|
|
13922
|
-
|
|
13923
|
-
|
|
13924
|
-
|
|
13925
|
-
|
|
14259
|
+
* @summary Deletes a scaling configuration of the Elastic Container Instance type. If the scaling configuration of a scaling group is in the Inactive state and the scaling group contains no elastic container instances created from the scaling configuration, you can call the DeleteEciScalingConfiguration operation to delete the scaling configuration to free up the scaling configuration quota.
|
|
14260
|
+
*
|
|
14261
|
+
* @description You cannot call this operation to delete a scaling configuration in the following scenarios:
|
|
14262
|
+
* * The scaling configuration is in the Active state.
|
|
14263
|
+
* * The scaling group contains elastic container instances created from the scaling configuration.
|
|
14264
|
+
*
|
|
14265
|
+
* @param request DeleteEciScalingConfigurationRequest
|
|
14266
|
+
* @return DeleteEciScalingConfigurationResponse
|
|
13926
14267
|
*/
|
|
13927
14268
|
async deleteEciScalingConfiguration(request) {
|
|
13928
14269
|
let runtime = new $Util.RuntimeOptions({});
|
|
13929
14270
|
return await this.deleteEciScalingConfigurationWithOptions(request, runtime);
|
|
13930
14271
|
}
|
|
14272
|
+
/**
|
|
14273
|
+
* @summary Deletes a lifecycle hook.
|
|
14274
|
+
*
|
|
14275
|
+
* @description If you delete a lifecycle hook that is in effect in a scaling group, instances exit the Pending state in advance. You can use one of the following methods to specify the lifecycle hooks that you want to delete:
|
|
14276
|
+
* * Specify the scaling group ID of the lifecycle hook that you want to delete by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter.
|
|
14277
|
+
* * Specify the lifecycle hook ID by using the LifecycleHookId parameter. In this case, the ScalingGroupId parameter and the LifecycleHookName parameter are ignored.
|
|
14278
|
+
*
|
|
14279
|
+
* @param request DeleteLifecycleHookRequest
|
|
14280
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14281
|
+
* @return DeleteLifecycleHookResponse
|
|
14282
|
+
*/
|
|
13931
14283
|
async deleteLifecycleHookWithOptions(request, runtime) {
|
|
13932
14284
|
tea_util_1.default.validateModel(request);
|
|
13933
14285
|
let query = {};
|
|
@@ -13968,10 +14320,27 @@ class Client extends openapi_client_1.default {
|
|
|
13968
14320
|
});
|
|
13969
14321
|
return $tea.cast(await this.callApi(params, req, runtime), new DeleteLifecycleHookResponse({}));
|
|
13970
14322
|
}
|
|
14323
|
+
/**
|
|
14324
|
+
* @summary Deletes a lifecycle hook.
|
|
14325
|
+
*
|
|
14326
|
+
* @description If you delete a lifecycle hook that is in effect in a scaling group, instances exit the Pending state in advance. You can use one of the following methods to specify the lifecycle hooks that you want to delete:
|
|
14327
|
+
* * Specify the scaling group ID of the lifecycle hook that you want to delete by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter.
|
|
14328
|
+
* * Specify the lifecycle hook ID by using the LifecycleHookId parameter. In this case, the ScalingGroupId parameter and the LifecycleHookName parameter are ignored.
|
|
14329
|
+
*
|
|
14330
|
+
* @param request DeleteLifecycleHookRequest
|
|
14331
|
+
* @return DeleteLifecycleHookResponse
|
|
14332
|
+
*/
|
|
13971
14333
|
async deleteLifecycleHook(request) {
|
|
13972
14334
|
let runtime = new $Util.RuntimeOptions({});
|
|
13973
14335
|
return await this.deleteLifecycleHookWithOptions(request, runtime);
|
|
13974
14336
|
}
|
|
14337
|
+
/**
|
|
14338
|
+
* @summary Deletes event notification rules. The event notification feature facilitates efficient issue identification and event management by automatically forwarding notifications from Auto Scaling to designated endpoints such as CloudMonitor or Message Service (MNS) topics and queues. If you no longer require an event notification rule, you can call the DeleteNotificationConfiguration operation to delete it.
|
|
14339
|
+
*
|
|
14340
|
+
* @param request DeleteNotificationConfigurationRequest
|
|
14341
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14342
|
+
* @return DeleteNotificationConfigurationResponse
|
|
14343
|
+
*/
|
|
13975
14344
|
async deleteNotificationConfigurationWithOptions(request, runtime) {
|
|
13976
14345
|
tea_util_1.default.validateModel(request);
|
|
13977
14346
|
let query = {};
|
|
@@ -14006,18 +14375,26 @@ class Client extends openapi_client_1.default {
|
|
|
14006
14375
|
});
|
|
14007
14376
|
return $tea.cast(await this.callApi(params, req, runtime), new DeleteNotificationConfigurationResponse({}));
|
|
14008
14377
|
}
|
|
14378
|
+
/**
|
|
14379
|
+
* @summary Deletes event notification rules. The event notification feature facilitates efficient issue identification and event management by automatically forwarding notifications from Auto Scaling to designated endpoints such as CloudMonitor or Message Service (MNS) topics and queues. If you no longer require an event notification rule, you can call the DeleteNotificationConfiguration operation to delete it.
|
|
14380
|
+
*
|
|
14381
|
+
* @param request DeleteNotificationConfigurationRequest
|
|
14382
|
+
* @return DeleteNotificationConfigurationResponse
|
|
14383
|
+
*/
|
|
14009
14384
|
async deleteNotificationConfiguration(request) {
|
|
14010
14385
|
let runtime = new $Util.RuntimeOptions({});
|
|
14011
14386
|
return await this.deleteNotificationConfigurationWithOptions(request, runtime);
|
|
14012
14387
|
}
|
|
14013
14388
|
/**
|
|
14014
|
-
|
|
14015
|
-
|
|
14016
|
-
|
|
14017
|
-
|
|
14018
|
-
|
|
14019
|
-
|
|
14020
|
-
|
|
14389
|
+
* @summary Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
|
|
14390
|
+
*
|
|
14391
|
+
* @description You cannot delete a scaling configuration in one of the following scenarios:
|
|
14392
|
+
* * The scaling configuration in your scaling group is in the Active state.
|
|
14393
|
+
* * The scaling group contains ECS instances that were created based on the scaling configuration.
|
|
14394
|
+
*
|
|
14395
|
+
* @param request DeleteScalingConfigurationRequest
|
|
14396
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14397
|
+
* @return DeleteScalingConfigurationResponse
|
|
14021
14398
|
*/
|
|
14022
14399
|
async deleteScalingConfigurationWithOptions(request, runtime) {
|
|
14023
14400
|
tea_util_1.default.validateModel(request);
|
|
@@ -14051,17 +14428,37 @@ class Client extends openapi_client_1.default {
|
|
|
14051
14428
|
return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingConfigurationResponse({}));
|
|
14052
14429
|
}
|
|
14053
14430
|
/**
|
|
14054
|
-
|
|
14055
|
-
|
|
14056
|
-
|
|
14057
|
-
|
|
14058
|
-
|
|
14059
|
-
|
|
14431
|
+
* @summary Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
|
|
14432
|
+
*
|
|
14433
|
+
* @description You cannot delete a scaling configuration in one of the following scenarios:
|
|
14434
|
+
* * The scaling configuration in your scaling group is in the Active state.
|
|
14435
|
+
* * The scaling group contains ECS instances that were created based on the scaling configuration.
|
|
14436
|
+
*
|
|
14437
|
+
* @param request DeleteScalingConfigurationRequest
|
|
14438
|
+
* @return DeleteScalingConfigurationResponse
|
|
14060
14439
|
*/
|
|
14061
14440
|
async deleteScalingConfiguration(request) {
|
|
14062
14441
|
let runtime = new $Util.RuntimeOptions({});
|
|
14063
14442
|
return await this.deleteScalingConfigurationWithOptions(request, runtime);
|
|
14064
14443
|
}
|
|
14444
|
+
/**
|
|
14445
|
+
* @summary Deletes a scaling group. If you want to enable policy-based automatic addition or removal of instances of a specific type to meet evolving business requirements, you can create scaling groups to manage your computing power with ease. The computing power refers to the instances that provide the computing capability. If you no longer require a scaling group, you can call the DeleteScalingGroup operation to delete it to free up the scaling group quota.
|
|
14446
|
+
*
|
|
14447
|
+
* @description Before you call the DeleteScalingGroup operation, take note of the following items:
|
|
14448
|
+
* * If you delete a scaling group, the scaling configurations, scaling rules, scaling activities, and scaling requests related to the scaling group are also deleted.
|
|
14449
|
+
* * If you delete a scaling group, the scheduled tasks and event-triggered tasks of the scaling group are not deleted. The Server Load Balancer (SLB) instances and ApsaraDB RDS instances that are attached to the scaling group are also not deleted.
|
|
14450
|
+
* * If the scaling group that you want to delete contains ECS instances or elastic container instances that are in the In Service state, Auto Scaling stops the instances and then removes all manually added instances from the scaling group or releases all automatically created instances in the scaling group before the scaling group is deleted.
|
|
14451
|
+
* **
|
|
14452
|
+
* **Note** Before you delete a scaling group, make sure that the Deletion Protection feature is disabled. If you have enabled the Deletion Protection feature for a scaling group, disable the feature on the Modify Scaling Group page before you delete the scaling group.
|
|
14453
|
+
* * If you do not disable the Deletion Protection feature for a scaling group, you cannot delete the scaling group by using the Auto Scaling console or calling this operation. The Deletion Protection feature is an effective measure to safeguard scaling groups against unintended deletion.
|
|
14454
|
+
* * Prior to deleting a scaling group, make sure that your ECS instances within the scaling group are safeguarded against unintended release. Even if you have already enabled the Release Protection feature for the ECS instances, you must manually put these ECS instances into the Protected state. Doing so guarantees that the ECS instances will not be forcibly released during the deletion process of the scaling group, providing an extra layer of security.
|
|
14455
|
+
* **
|
|
14456
|
+
* **Note** Before you delete a scaling group, we recommend that you enable the Deletion Protection feature for ECS instances that you want to retain. This action guarantees that the ECS instances are not forcibly released after you delete the scaling group. For more information, see [SetInstancesProtection](https://help.aliyun.com/document_detail/459342.html).
|
|
14457
|
+
*
|
|
14458
|
+
* @param request DeleteScalingGroupRequest
|
|
14459
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14460
|
+
* @return DeleteScalingGroupResponse
|
|
14461
|
+
*/
|
|
14065
14462
|
async deleteScalingGroupWithOptions(request, runtime) {
|
|
14066
14463
|
tea_util_1.default.validateModel(request);
|
|
14067
14464
|
let query = {};
|
|
@@ -14099,10 +14496,34 @@ class Client extends openapi_client_1.default {
|
|
|
14099
14496
|
});
|
|
14100
14497
|
return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingGroupResponse({}));
|
|
14101
14498
|
}
|
|
14499
|
+
/**
|
|
14500
|
+
* @summary Deletes a scaling group. If you want to enable policy-based automatic addition or removal of instances of a specific type to meet evolving business requirements, you can create scaling groups to manage your computing power with ease. The computing power refers to the instances that provide the computing capability. If you no longer require a scaling group, you can call the DeleteScalingGroup operation to delete it to free up the scaling group quota.
|
|
14501
|
+
*
|
|
14502
|
+
* @description Before you call the DeleteScalingGroup operation, take note of the following items:
|
|
14503
|
+
* * If you delete a scaling group, the scaling configurations, scaling rules, scaling activities, and scaling requests related to the scaling group are also deleted.
|
|
14504
|
+
* * If you delete a scaling group, the scheduled tasks and event-triggered tasks of the scaling group are not deleted. The Server Load Balancer (SLB) instances and ApsaraDB RDS instances that are attached to the scaling group are also not deleted.
|
|
14505
|
+
* * If the scaling group that you want to delete contains ECS instances or elastic container instances that are in the In Service state, Auto Scaling stops the instances and then removes all manually added instances from the scaling group or releases all automatically created instances in the scaling group before the scaling group is deleted.
|
|
14506
|
+
* **
|
|
14507
|
+
* **Note** Before you delete a scaling group, make sure that the Deletion Protection feature is disabled. If you have enabled the Deletion Protection feature for a scaling group, disable the feature on the Modify Scaling Group page before you delete the scaling group.
|
|
14508
|
+
* * If you do not disable the Deletion Protection feature for a scaling group, you cannot delete the scaling group by using the Auto Scaling console or calling this operation. The Deletion Protection feature is an effective measure to safeguard scaling groups against unintended deletion.
|
|
14509
|
+
* * Prior to deleting a scaling group, make sure that your ECS instances within the scaling group are safeguarded against unintended release. Even if you have already enabled the Release Protection feature for the ECS instances, you must manually put these ECS instances into the Protected state. Doing so guarantees that the ECS instances will not be forcibly released during the deletion process of the scaling group, providing an extra layer of security.
|
|
14510
|
+
* **
|
|
14511
|
+
* **Note** Before you delete a scaling group, we recommend that you enable the Deletion Protection feature for ECS instances that you want to retain. This action guarantees that the ECS instances are not forcibly released after you delete the scaling group. For more information, see [SetInstancesProtection](https://help.aliyun.com/document_detail/459342.html).
|
|
14512
|
+
*
|
|
14513
|
+
* @param request DeleteScalingGroupRequest
|
|
14514
|
+
* @return DeleteScalingGroupResponse
|
|
14515
|
+
*/
|
|
14102
14516
|
async deleteScalingGroup(request) {
|
|
14103
14517
|
let runtime = new $Util.RuntimeOptions({});
|
|
14104
14518
|
return await this.deleteScalingGroupWithOptions(request, runtime);
|
|
14105
14519
|
}
|
|
14520
|
+
/**
|
|
14521
|
+
* @summary Deletes a scaling rule.
|
|
14522
|
+
*
|
|
14523
|
+
* @param request DeleteScalingRuleRequest
|
|
14524
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14525
|
+
* @return DeleteScalingRuleResponse
|
|
14526
|
+
*/
|
|
14106
14527
|
async deleteScalingRuleWithOptions(request, runtime) {
|
|
14107
14528
|
tea_util_1.default.validateModel(request);
|
|
14108
14529
|
let query = {};
|
|
@@ -14137,10 +14558,23 @@ class Client extends openapi_client_1.default {
|
|
|
14137
14558
|
});
|
|
14138
14559
|
return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingRuleResponse({}));
|
|
14139
14560
|
}
|
|
14561
|
+
/**
|
|
14562
|
+
* @summary Deletes a scaling rule.
|
|
14563
|
+
*
|
|
14564
|
+
* @param request DeleteScalingRuleRequest
|
|
14565
|
+
* @return DeleteScalingRuleResponse
|
|
14566
|
+
*/
|
|
14140
14567
|
async deleteScalingRule(request) {
|
|
14141
14568
|
let runtime = new $Util.RuntimeOptions({});
|
|
14142
14569
|
return await this.deleteScalingRuleWithOptions(request, runtime);
|
|
14143
14570
|
}
|
|
14571
|
+
/**
|
|
14572
|
+
* @summary Deletes scheduled tasks. For workloads with predictable patterns, you can create scheduled tasks to align with your business requirements and optimize resource utilization for cost savings. These tasks automatically ensure that sufficient computing resources are provisioned in anticipation of peak hours and efficiently release unused resources during off-peak hours, thereby streamlining operational efficiency and reducing expenses. If you no longer require a scheduled task, you can call the DeleteScheduledTask operation to delete it.
|
|
14573
|
+
*
|
|
14574
|
+
* @param request DeleteScheduledTaskRequest
|
|
14575
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14576
|
+
* @return DeleteScheduledTaskResponse
|
|
14577
|
+
*/
|
|
14144
14578
|
async deleteScheduledTaskWithOptions(request, runtime) {
|
|
14145
14579
|
tea_util_1.default.validateModel(request);
|
|
14146
14580
|
let query = {};
|
|
@@ -14175,10 +14609,23 @@ class Client extends openapi_client_1.default {
|
|
|
14175
14609
|
});
|
|
14176
14610
|
return $tea.cast(await this.callApi(params, req, runtime), new DeleteScheduledTaskResponse({}));
|
|
14177
14611
|
}
|
|
14612
|
+
/**
|
|
14613
|
+
* @summary Deletes scheduled tasks. For workloads with predictable patterns, you can create scheduled tasks to align with your business requirements and optimize resource utilization for cost savings. These tasks automatically ensure that sufficient computing resources are provisioned in anticipation of peak hours and efficiently release unused resources during off-peak hours, thereby streamlining operational efficiency and reducing expenses. If you no longer require a scheduled task, you can call the DeleteScheduledTask operation to delete it.
|
|
14614
|
+
*
|
|
14615
|
+
* @param request DeleteScheduledTaskRequest
|
|
14616
|
+
* @return DeleteScheduledTaskResponse
|
|
14617
|
+
*/
|
|
14178
14618
|
async deleteScheduledTask(request) {
|
|
14179
14619
|
let runtime = new $Util.RuntimeOptions({});
|
|
14180
14620
|
return await this.deleteScheduledTaskWithOptions(request, runtime);
|
|
14181
14621
|
}
|
|
14622
|
+
/**
|
|
14623
|
+
* @summary Queries event-triggered tasks.
|
|
14624
|
+
*
|
|
14625
|
+
* @param request DescribeAlarmsRequest
|
|
14626
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14627
|
+
* @return DescribeAlarmsResponse
|
|
14628
|
+
*/
|
|
14182
14629
|
async describeAlarmsWithOptions(request, runtime) {
|
|
14183
14630
|
tea_util_1.default.validateModel(request);
|
|
14184
14631
|
let query = {};
|
|
@@ -14231,10 +14678,23 @@ class Client extends openapi_client_1.default {
|
|
|
14231
14678
|
});
|
|
14232
14679
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeAlarmsResponse({}));
|
|
14233
14680
|
}
|
|
14681
|
+
/**
|
|
14682
|
+
* @summary Queries event-triggered tasks.
|
|
14683
|
+
*
|
|
14684
|
+
* @param request DescribeAlarmsRequest
|
|
14685
|
+
* @return DescribeAlarmsResponse
|
|
14686
|
+
*/
|
|
14234
14687
|
async describeAlarms(request) {
|
|
14235
14688
|
let runtime = new $Util.RuntimeOptions({});
|
|
14236
14689
|
return await this.describeAlarmsWithOptions(request, runtime);
|
|
14237
14690
|
}
|
|
14691
|
+
/**
|
|
14692
|
+
* @summary Queries scaling configurations of the Elastic Container Instance type to learn the scaling configuration details. This allows you to select an appropriate template when you create elastic container instances. If you set OutputFormat to yaml, the output is a Kubernetes Deployment file in the YAML format.
|
|
14693
|
+
*
|
|
14694
|
+
* @param request DescribeEciScalingConfigurationDetailRequest
|
|
14695
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14696
|
+
* @return DescribeEciScalingConfigurationDetailResponse
|
|
14697
|
+
*/
|
|
14238
14698
|
async describeEciScalingConfigurationDetailWithOptions(request, runtime) {
|
|
14239
14699
|
tea_util_1.default.validateModel(request);
|
|
14240
14700
|
let query = {};
|
|
@@ -14266,10 +14726,23 @@ class Client extends openapi_client_1.default {
|
|
|
14266
14726
|
});
|
|
14267
14727
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeEciScalingConfigurationDetailResponse({}));
|
|
14268
14728
|
}
|
|
14729
|
+
/**
|
|
14730
|
+
* @summary Queries scaling configurations of the Elastic Container Instance type to learn the scaling configuration details. This allows you to select an appropriate template when you create elastic container instances. If you set OutputFormat to yaml, the output is a Kubernetes Deployment file in the YAML format.
|
|
14731
|
+
*
|
|
14732
|
+
* @param request DescribeEciScalingConfigurationDetailRequest
|
|
14733
|
+
* @return DescribeEciScalingConfigurationDetailResponse
|
|
14734
|
+
*/
|
|
14269
14735
|
async describeEciScalingConfigurationDetail(request) {
|
|
14270
14736
|
let runtime = new $Util.RuntimeOptions({});
|
|
14271
14737
|
return await this.describeEciScalingConfigurationDetailWithOptions(request, runtime);
|
|
14272
14738
|
}
|
|
14739
|
+
/**
|
|
14740
|
+
* @summary Queries scaling configurations of the Elastic Container Instance type to learn the scaling configuration details. This allows you to select an appropriate template when you create elastic container instances.
|
|
14741
|
+
*
|
|
14742
|
+
* @param request DescribeEciScalingConfigurationsRequest
|
|
14743
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14744
|
+
* @return DescribeEciScalingConfigurationsResponse
|
|
14745
|
+
*/
|
|
14273
14746
|
async describeEciScalingConfigurationsWithOptions(request, runtime) {
|
|
14274
14747
|
tea_util_1.default.validateModel(request);
|
|
14275
14748
|
let query = {};
|
|
@@ -14319,20 +14792,28 @@ class Client extends openapi_client_1.default {
|
|
|
14319
14792
|
});
|
|
14320
14793
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeEciScalingConfigurationsResponse({}));
|
|
14321
14794
|
}
|
|
14795
|
+
/**
|
|
14796
|
+
* @summary Queries scaling configurations of the Elastic Container Instance type to learn the scaling configuration details. This allows you to select an appropriate template when you create elastic container instances.
|
|
14797
|
+
*
|
|
14798
|
+
* @param request DescribeEciScalingConfigurationsRequest
|
|
14799
|
+
* @return DescribeEciScalingConfigurationsResponse
|
|
14800
|
+
*/
|
|
14322
14801
|
async describeEciScalingConfigurations(request) {
|
|
14323
14802
|
let runtime = new $Util.RuntimeOptions({});
|
|
14324
14803
|
return await this.describeEciScalingConfigurationsWithOptions(request, runtime);
|
|
14325
14804
|
}
|
|
14326
14805
|
/**
|
|
14327
|
-
|
|
14328
|
-
|
|
14329
|
-
|
|
14330
|
-
|
|
14331
|
-
|
|
14332
|
-
|
|
14333
|
-
|
|
14334
|
-
|
|
14335
|
-
|
|
14806
|
+
* @summary Queries lifecycle actions.
|
|
14807
|
+
*
|
|
14808
|
+
* @description If a scaling activity is executed and a lifecycle hook is created for the scaling activity, the lifecycle hook triggers a lifecycle action. A lifecycle action can be in one of the following states:
|
|
14809
|
+
* * If a lifecycle action is in the Pending state, Elastic Compute Service (ECS) instances are waiting to be added to a scaling group or waiting to be removed from a scaling group.
|
|
14810
|
+
* * If a lifecycle action is in the Timeout state, the lifecycle hook that triggers the lifecycle action expires and ECS instances are added to or removed from a scaling group.
|
|
14811
|
+
* * If a lifecycle action is in the Completed state, you manually end the lifecycle hook that triggers the lifecycle action ahead of schedule.
|
|
14812
|
+
* If you do not specify the action to perform, such as execute a specific OOS template, after a lifecycle hook ends, you can call this operation to obtain the token of the lifecycle action that corresponds to the lifecycle hook. Then, you can specify a custom action to perform after the lifecycle hook ends.
|
|
14813
|
+
*
|
|
14814
|
+
* @param request DescribeLifecycleActionsRequest
|
|
14815
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14816
|
+
* @return DescribeLifecycleActionsResponse
|
|
14336
14817
|
*/
|
|
14337
14818
|
async describeLifecycleActionsWithOptions(request, runtime) {
|
|
14338
14819
|
tea_util_1.default.validateModel(request);
|
|
@@ -14375,19 +14856,33 @@ class Client extends openapi_client_1.default {
|
|
|
14375
14856
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeLifecycleActionsResponse({}));
|
|
14376
14857
|
}
|
|
14377
14858
|
/**
|
|
14378
|
-
|
|
14379
|
-
|
|
14380
|
-
|
|
14381
|
-
|
|
14382
|
-
|
|
14383
|
-
|
|
14384
|
-
|
|
14385
|
-
|
|
14859
|
+
* @summary Queries lifecycle actions.
|
|
14860
|
+
*
|
|
14861
|
+
* @description If a scaling activity is executed and a lifecycle hook is created for the scaling activity, the lifecycle hook triggers a lifecycle action. A lifecycle action can be in one of the following states:
|
|
14862
|
+
* * If a lifecycle action is in the Pending state, Elastic Compute Service (ECS) instances are waiting to be added to a scaling group or waiting to be removed from a scaling group.
|
|
14863
|
+
* * If a lifecycle action is in the Timeout state, the lifecycle hook that triggers the lifecycle action expires and ECS instances are added to or removed from a scaling group.
|
|
14864
|
+
* * If a lifecycle action is in the Completed state, you manually end the lifecycle hook that triggers the lifecycle action ahead of schedule.
|
|
14865
|
+
* If you do not specify the action to perform, such as execute a specific OOS template, after a lifecycle hook ends, you can call this operation to obtain the token of the lifecycle action that corresponds to the lifecycle hook. Then, you can specify a custom action to perform after the lifecycle hook ends.
|
|
14866
|
+
*
|
|
14867
|
+
* @param request DescribeLifecycleActionsRequest
|
|
14868
|
+
* @return DescribeLifecycleActionsResponse
|
|
14386
14869
|
*/
|
|
14387
14870
|
async describeLifecycleActions(request) {
|
|
14388
14871
|
let runtime = new $Util.RuntimeOptions({});
|
|
14389
14872
|
return await this.describeLifecycleActionsWithOptions(request, runtime);
|
|
14390
14873
|
}
|
|
14874
|
+
/**
|
|
14875
|
+
* @summary Queries lifecycle hooks.
|
|
14876
|
+
*
|
|
14877
|
+
* @description You can use one of the following methods to query lifecycle hooks:
|
|
14878
|
+
* * Specify a list of lifecycle hook IDs by using the LifecycleHookIds parameter. In this case, you do not need to specify the ScalingGroupId and LifecycleHookName parameters.
|
|
14879
|
+
* * Specify the scaling group ID by using the ScalingGroupId parameter.
|
|
14880
|
+
* * Specify the scaling group ID by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter at the same time.
|
|
14881
|
+
*
|
|
14882
|
+
* @param request DescribeLifecycleHooksRequest
|
|
14883
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14884
|
+
* @return DescribeLifecycleHooksResponse
|
|
14885
|
+
*/
|
|
14391
14886
|
async describeLifecycleHooksWithOptions(request, runtime) {
|
|
14392
14887
|
tea_util_1.default.validateModel(request);
|
|
14393
14888
|
let query = {};
|
|
@@ -14434,10 +14929,28 @@ class Client extends openapi_client_1.default {
|
|
|
14434
14929
|
});
|
|
14435
14930
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeLifecycleHooksResponse({}));
|
|
14436
14931
|
}
|
|
14932
|
+
/**
|
|
14933
|
+
* @summary Queries lifecycle hooks.
|
|
14934
|
+
*
|
|
14935
|
+
* @description You can use one of the following methods to query lifecycle hooks:
|
|
14936
|
+
* * Specify a list of lifecycle hook IDs by using the LifecycleHookIds parameter. In this case, you do not need to specify the ScalingGroupId and LifecycleHookName parameters.
|
|
14937
|
+
* * Specify the scaling group ID by using the ScalingGroupId parameter.
|
|
14938
|
+
* * Specify the scaling group ID by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter at the same time.
|
|
14939
|
+
*
|
|
14940
|
+
* @param request DescribeLifecycleHooksRequest
|
|
14941
|
+
* @return DescribeLifecycleHooksResponse
|
|
14942
|
+
*/
|
|
14437
14943
|
async describeLifecycleHooks(request) {
|
|
14438
14944
|
let runtime = new $Util.RuntimeOptions({});
|
|
14439
14945
|
return await this.describeLifecycleHooksWithOptions(request, runtime);
|
|
14440
14946
|
}
|
|
14947
|
+
/**
|
|
14948
|
+
* @summary Queries resource quotas. You can call the DescribeLimitation operation to query the upper limits on resources such as scheduled tasks that can be created in a scaling group, load balancers that can be attached to a scaling group, instances that can be contained in a scaling group, and scaling configurations that can be created in a scaling group.
|
|
14949
|
+
*
|
|
14950
|
+
* @param request DescribeLimitationRequest
|
|
14951
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14952
|
+
* @return DescribeLimitationResponse
|
|
14953
|
+
*/
|
|
14441
14954
|
async describeLimitationWithOptions(request, runtime) {
|
|
14442
14955
|
tea_util_1.default.validateModel(request);
|
|
14443
14956
|
let query = {};
|
|
@@ -14463,10 +14976,23 @@ class Client extends openapi_client_1.default {
|
|
|
14463
14976
|
});
|
|
14464
14977
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeLimitationResponse({}));
|
|
14465
14978
|
}
|
|
14979
|
+
/**
|
|
14980
|
+
* @summary Queries resource quotas. You can call the DescribeLimitation operation to query the upper limits on resources such as scheduled tasks that can be created in a scaling group, load balancers that can be attached to a scaling group, instances that can be contained in a scaling group, and scaling configurations that can be created in a scaling group.
|
|
14981
|
+
*
|
|
14982
|
+
* @param request DescribeLimitationRequest
|
|
14983
|
+
* @return DescribeLimitationResponse
|
|
14984
|
+
*/
|
|
14466
14985
|
async describeLimitation(request) {
|
|
14467
14986
|
let runtime = new $Util.RuntimeOptions({});
|
|
14468
14987
|
return await this.describeLimitationWithOptions(request, runtime);
|
|
14469
14988
|
}
|
|
14989
|
+
/**
|
|
14990
|
+
* @summary Queries event notifications.
|
|
14991
|
+
*
|
|
14992
|
+
* @param request DescribeNotificationConfigurationsRequest
|
|
14993
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
14994
|
+
* @return DescribeNotificationConfigurationsResponse
|
|
14995
|
+
*/
|
|
14470
14996
|
async describeNotificationConfigurationsWithOptions(request, runtime) {
|
|
14471
14997
|
tea_util_1.default.validateModel(request);
|
|
14472
14998
|
let query = {};
|
|
@@ -14498,10 +15024,23 @@ class Client extends openapi_client_1.default {
|
|
|
14498
15024
|
});
|
|
14499
15025
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeNotificationConfigurationsResponse({}));
|
|
14500
15026
|
}
|
|
15027
|
+
/**
|
|
15028
|
+
* @summary Queries event notifications.
|
|
15029
|
+
*
|
|
15030
|
+
* @param request DescribeNotificationConfigurationsRequest
|
|
15031
|
+
* @return DescribeNotificationConfigurationsResponse
|
|
15032
|
+
*/
|
|
14501
15033
|
async describeNotificationConfigurations(request) {
|
|
14502
15034
|
let runtime = new $Util.RuntimeOptions({});
|
|
14503
15035
|
return await this.describeNotificationConfigurationsWithOptions(request, runtime);
|
|
14504
15036
|
}
|
|
15037
|
+
/**
|
|
15038
|
+
* @summary Queries notification types.
|
|
15039
|
+
*
|
|
15040
|
+
* @param request DescribeNotificationTypesRequest
|
|
15041
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15042
|
+
* @return DescribeNotificationTypesResponse
|
|
15043
|
+
*/
|
|
14505
15044
|
async describeNotificationTypesWithOptions(request, runtime) {
|
|
14506
15045
|
tea_util_1.default.validateModel(request);
|
|
14507
15046
|
let query = {};
|
|
@@ -14527,10 +15066,59 @@ class Client extends openapi_client_1.default {
|
|
|
14527
15066
|
});
|
|
14528
15067
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeNotificationTypesResponse({}));
|
|
14529
15068
|
}
|
|
15069
|
+
/**
|
|
15070
|
+
* @summary Queries notification types.
|
|
15071
|
+
*
|
|
15072
|
+
* @param request DescribeNotificationTypesRequest
|
|
15073
|
+
* @return DescribeNotificationTypesResponse
|
|
15074
|
+
*/
|
|
14530
15075
|
async describeNotificationTypes(request) {
|
|
14531
15076
|
let runtime = new $Util.RuntimeOptions({});
|
|
14532
15077
|
return await this.describeNotificationTypesWithOptions(request, runtime);
|
|
14533
15078
|
}
|
|
15079
|
+
/**
|
|
15080
|
+
* @summary DescribePatternTypes
|
|
15081
|
+
*
|
|
15082
|
+
* @param request DescribePatternTypesRequest
|
|
15083
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15084
|
+
* @return DescribePatternTypesResponse
|
|
15085
|
+
*/
|
|
15086
|
+
async describePatternTypesWithOptions(request, runtime) {
|
|
15087
|
+
tea_util_1.default.validateModel(request);
|
|
15088
|
+
let query = openapi_util_1.default.query(tea_util_1.default.toMap(request));
|
|
15089
|
+
let req = new $OpenApi.OpenApiRequest({
|
|
15090
|
+
query: openapi_util_1.default.query(query),
|
|
15091
|
+
});
|
|
15092
|
+
let params = new $OpenApi.Params({
|
|
15093
|
+
action: "DescribePatternTypes",
|
|
15094
|
+
version: "2022-02-22",
|
|
15095
|
+
protocol: "HTTPS",
|
|
15096
|
+
pathname: "/",
|
|
15097
|
+
method: "GET",
|
|
15098
|
+
authType: "AK",
|
|
15099
|
+
style: "RPC",
|
|
15100
|
+
reqBodyType: "formData",
|
|
15101
|
+
bodyType: "json",
|
|
15102
|
+
});
|
|
15103
|
+
return $tea.cast(await this.callApi(params, req, runtime), new DescribePatternTypesResponse({}));
|
|
15104
|
+
}
|
|
15105
|
+
/**
|
|
15106
|
+
* @summary DescribePatternTypes
|
|
15107
|
+
*
|
|
15108
|
+
* @param request DescribePatternTypesRequest
|
|
15109
|
+
* @return DescribePatternTypesResponse
|
|
15110
|
+
*/
|
|
15111
|
+
async describePatternTypes(request) {
|
|
15112
|
+
let runtime = new $Util.RuntimeOptions({});
|
|
15113
|
+
return await this.describePatternTypesWithOptions(request, runtime);
|
|
15114
|
+
}
|
|
15115
|
+
/**
|
|
15116
|
+
* @summary Queries regions. Before you activate Auto Scaling, you can call the DescribeRegions operation to query the regions where Auto Scaling is officially launched. This preliminary step facilitates the strategic selection of both the optimal region and availability zones for activating Auto Scaling, thereby guaranteeing the finest access speeds and operational efficiency within your chosen geographical area.
|
|
15117
|
+
*
|
|
15118
|
+
* @param request DescribeRegionsRequest
|
|
15119
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15120
|
+
* @return DescribeRegionsResponse
|
|
15121
|
+
*/
|
|
14534
15122
|
async describeRegionsWithOptions(request, runtime) {
|
|
14535
15123
|
tea_util_1.default.validateModel(request);
|
|
14536
15124
|
let query = {};
|
|
@@ -14562,18 +15150,26 @@ class Client extends openapi_client_1.default {
|
|
|
14562
15150
|
});
|
|
14563
15151
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeRegionsResponse({}));
|
|
14564
15152
|
}
|
|
15153
|
+
/**
|
|
15154
|
+
* @summary Queries regions. Before you activate Auto Scaling, you can call the DescribeRegions operation to query the regions where Auto Scaling is officially launched. This preliminary step facilitates the strategic selection of both the optimal region and availability zones for activating Auto Scaling, thereby guaranteeing the finest access speeds and operational efficiency within your chosen geographical area.
|
|
15155
|
+
*
|
|
15156
|
+
* @param request DescribeRegionsRequest
|
|
15157
|
+
* @return DescribeRegionsResponse
|
|
15158
|
+
*/
|
|
14565
15159
|
async describeRegions(request) {
|
|
14566
15160
|
let runtime = new $Util.RuntimeOptions({});
|
|
14567
15161
|
return await this.describeRegionsWithOptions(request, runtime);
|
|
14568
15162
|
}
|
|
14569
15163
|
/**
|
|
14570
|
-
|
|
14571
|
-
|
|
14572
|
-
|
|
14573
|
-
|
|
14574
|
-
|
|
14575
|
-
|
|
14576
|
-
|
|
15164
|
+
* @summary Queries scaling activities.
|
|
15165
|
+
*
|
|
15166
|
+
* @description You can specify a scaling group ID to query all scaling activities in the scaling group.
|
|
15167
|
+
* You can filter query results based on the status of scaling activities.
|
|
15168
|
+
* You can query scaling activities that are executed in the previous 30 days.
|
|
15169
|
+
*
|
|
15170
|
+
* @param request DescribeScalingActivitiesRequest
|
|
15171
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15172
|
+
* @return DescribeScalingActivitiesResponse
|
|
14577
15173
|
*/
|
|
14578
15174
|
async describeScalingActivitiesWithOptions(request, runtime) {
|
|
14579
15175
|
tea_util_1.default.validateModel(request);
|
|
@@ -14625,17 +15221,26 @@ class Client extends openapi_client_1.default {
|
|
|
14625
15221
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingActivitiesResponse({}));
|
|
14626
15222
|
}
|
|
14627
15223
|
/**
|
|
14628
|
-
|
|
14629
|
-
|
|
14630
|
-
|
|
14631
|
-
|
|
14632
|
-
|
|
14633
|
-
|
|
15224
|
+
* @summary Queries scaling activities.
|
|
15225
|
+
*
|
|
15226
|
+
* @description You can specify a scaling group ID to query all scaling activities in the scaling group.
|
|
15227
|
+
* You can filter query results based on the status of scaling activities.
|
|
15228
|
+
* You can query scaling activities that are executed in the previous 30 days.
|
|
15229
|
+
*
|
|
15230
|
+
* @param request DescribeScalingActivitiesRequest
|
|
15231
|
+
* @return DescribeScalingActivitiesResponse
|
|
14634
15232
|
*/
|
|
14635
15233
|
async describeScalingActivities(request) {
|
|
14636
15234
|
let runtime = new $Util.RuntimeOptions({});
|
|
14637
15235
|
return await this.describeScalingActivitiesWithOptions(request, runtime);
|
|
14638
15236
|
}
|
|
15237
|
+
/**
|
|
15238
|
+
* @summary Queries the details about a scaling activity.
|
|
15239
|
+
*
|
|
15240
|
+
* @param request DescribeScalingActivityDetailRequest
|
|
15241
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15242
|
+
* @return DescribeScalingActivityDetailResponse
|
|
15243
|
+
*/
|
|
14639
15244
|
async describeScalingActivityDetailWithOptions(request, runtime) {
|
|
14640
15245
|
tea_util_1.default.validateModel(request);
|
|
14641
15246
|
let query = {};
|
|
@@ -14667,10 +15272,23 @@ class Client extends openapi_client_1.default {
|
|
|
14667
15272
|
});
|
|
14668
15273
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingActivityDetailResponse({}));
|
|
14669
15274
|
}
|
|
15275
|
+
/**
|
|
15276
|
+
* @summary Queries the details about a scaling activity.
|
|
15277
|
+
*
|
|
15278
|
+
* @param request DescribeScalingActivityDetailRequest
|
|
15279
|
+
* @return DescribeScalingActivityDetailResponse
|
|
15280
|
+
*/
|
|
14670
15281
|
async describeScalingActivityDetail(request) {
|
|
14671
15282
|
let runtime = new $Util.RuntimeOptions({});
|
|
14672
15283
|
return await this.describeScalingActivityDetailWithOptions(request, runtime);
|
|
14673
15284
|
}
|
|
15285
|
+
/**
|
|
15286
|
+
* @summary Queries scaling configurations.
|
|
15287
|
+
*
|
|
15288
|
+
* @param request DescribeScalingConfigurationsRequest
|
|
15289
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15290
|
+
* @return DescribeScalingConfigurationsResponse
|
|
15291
|
+
*/
|
|
14674
15292
|
async describeScalingConfigurationsWithOptions(request, runtime) {
|
|
14675
15293
|
tea_util_1.default.validateModel(request);
|
|
14676
15294
|
let query = {};
|
|
@@ -14720,10 +15338,23 @@ class Client extends openapi_client_1.default {
|
|
|
14720
15338
|
});
|
|
14721
15339
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingConfigurationsResponse({}));
|
|
14722
15340
|
}
|
|
15341
|
+
/**
|
|
15342
|
+
* @summary Queries scaling configurations.
|
|
15343
|
+
*
|
|
15344
|
+
* @param request DescribeScalingConfigurationsRequest
|
|
15345
|
+
* @return DescribeScalingConfigurationsResponse
|
|
15346
|
+
*/
|
|
14723
15347
|
async describeScalingConfigurations(request) {
|
|
14724
15348
|
let runtime = new $Util.RuntimeOptions({});
|
|
14725
15349
|
return await this.describeScalingConfigurationsWithOptions(request, runtime);
|
|
14726
15350
|
}
|
|
15351
|
+
/**
|
|
15352
|
+
* @summary Queries a scaling group. You can call the DescribeScalingGroupDetail operation to query the basic information, instances, and scaling configurations of a scaling group. If you set OutputFormat to yaml, a Kubernetes Deployment file that is in the YAML format is returned.
|
|
15353
|
+
*
|
|
15354
|
+
* @param request DescribeScalingGroupDetailRequest
|
|
15355
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15356
|
+
* @return DescribeScalingGroupDetailResponse
|
|
15357
|
+
*/
|
|
14727
15358
|
async describeScalingGroupDetailWithOptions(request, runtime) {
|
|
14728
15359
|
tea_util_1.default.validateModel(request);
|
|
14729
15360
|
let query = {};
|
|
@@ -14755,10 +15386,23 @@ class Client extends openapi_client_1.default {
|
|
|
14755
15386
|
});
|
|
14756
15387
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupDetailResponse({}));
|
|
14757
15388
|
}
|
|
15389
|
+
/**
|
|
15390
|
+
* @summary Queries a scaling group. You can call the DescribeScalingGroupDetail operation to query the basic information, instances, and scaling configurations of a scaling group. If you set OutputFormat to yaml, a Kubernetes Deployment file that is in the YAML format is returned.
|
|
15391
|
+
*
|
|
15392
|
+
* @param request DescribeScalingGroupDetailRequest
|
|
15393
|
+
* @return DescribeScalingGroupDetailResponse
|
|
15394
|
+
*/
|
|
14758
15395
|
async describeScalingGroupDetail(request) {
|
|
14759
15396
|
let runtime = new $Util.RuntimeOptions({});
|
|
14760
15397
|
return await this.describeScalingGroupDetailWithOptions(request, runtime);
|
|
14761
15398
|
}
|
|
15399
|
+
/**
|
|
15400
|
+
* @summary Queries scaling groups. If you want to query the basic information, instances, and scaling configurations of a scaling group, you can call the DescribeScalingGroups operation.
|
|
15401
|
+
*
|
|
15402
|
+
* @param request DescribeScalingGroupsRequest
|
|
15403
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15404
|
+
* @return DescribeScalingGroupsResponse
|
|
15405
|
+
*/
|
|
14762
15406
|
async describeScalingGroupsWithOptions(request, runtime) {
|
|
14763
15407
|
tea_util_1.default.validateModel(request);
|
|
14764
15408
|
let query = {};
|
|
@@ -14817,10 +15461,23 @@ class Client extends openapi_client_1.default {
|
|
|
14817
15461
|
});
|
|
14818
15462
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupsResponse({}));
|
|
14819
15463
|
}
|
|
15464
|
+
/**
|
|
15465
|
+
* @summary Queries scaling groups. If you want to query the basic information, instances, and scaling configurations of a scaling group, you can call the DescribeScalingGroups operation.
|
|
15466
|
+
*
|
|
15467
|
+
* @param request DescribeScalingGroupsRequest
|
|
15468
|
+
* @return DescribeScalingGroupsResponse
|
|
15469
|
+
*/
|
|
14820
15470
|
async describeScalingGroups(request) {
|
|
14821
15471
|
let runtime = new $Util.RuntimeOptions({});
|
|
14822
15472
|
return await this.describeScalingGroupsWithOptions(request, runtime);
|
|
14823
15473
|
}
|
|
15474
|
+
/**
|
|
15475
|
+
* @summary Queries the Elastic Compute Service (ECS) instances in a scaling group
|
|
15476
|
+
*
|
|
15477
|
+
* @param request DescribeScalingInstancesRequest
|
|
15478
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15479
|
+
* @return DescribeScalingInstancesResponse
|
|
15480
|
+
*/
|
|
14824
15481
|
async describeScalingInstancesWithOptions(request, runtime) {
|
|
14825
15482
|
tea_util_1.default.validateModel(request);
|
|
14826
15483
|
let query = {};
|
|
@@ -14888,16 +15545,24 @@ class Client extends openapi_client_1.default {
|
|
|
14888
15545
|
});
|
|
14889
15546
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingInstancesResponse({}));
|
|
14890
15547
|
}
|
|
15548
|
+
/**
|
|
15549
|
+
* @summary Queries the Elastic Compute Service (ECS) instances in a scaling group
|
|
15550
|
+
*
|
|
15551
|
+
* @param request DescribeScalingInstancesRequest
|
|
15552
|
+
* @return DescribeScalingInstancesResponse
|
|
15553
|
+
*/
|
|
14891
15554
|
async describeScalingInstances(request) {
|
|
14892
15555
|
let runtime = new $Util.RuntimeOptions({});
|
|
14893
15556
|
return await this.describeScalingInstancesWithOptions(request, runtime);
|
|
14894
15557
|
}
|
|
14895
15558
|
/**
|
|
14896
|
-
|
|
14897
|
-
|
|
14898
|
-
|
|
14899
|
-
|
|
14900
|
-
|
|
15559
|
+
* @summary Queries all scaling rules in a scaling group.
|
|
15560
|
+
*
|
|
15561
|
+
* @description You can specify a scaling group ID to query all scaling rules in the scaling group. You can also specify the scaling rule ID, name, unique identifier, and type in the request parameters as filter conditions.
|
|
15562
|
+
*
|
|
15563
|
+
* @param request DescribeScalingRulesRequest
|
|
15564
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15565
|
+
* @return DescribeScalingRulesResponse
|
|
14901
15566
|
*/
|
|
14902
15567
|
async describeScalingRulesWithOptions(request, runtime) {
|
|
14903
15568
|
tea_util_1.default.validateModel(request);
|
|
@@ -14958,15 +15623,26 @@ class Client extends openapi_client_1.default {
|
|
|
14958
15623
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingRulesResponse({}));
|
|
14959
15624
|
}
|
|
14960
15625
|
/**
|
|
14961
|
-
|
|
14962
|
-
|
|
14963
|
-
|
|
14964
|
-
|
|
15626
|
+
* @summary Queries all scaling rules in a scaling group.
|
|
15627
|
+
*
|
|
15628
|
+
* @description You can specify a scaling group ID to query all scaling rules in the scaling group. You can also specify the scaling rule ID, name, unique identifier, and type in the request parameters as filter conditions.
|
|
15629
|
+
*
|
|
15630
|
+
* @param request DescribeScalingRulesRequest
|
|
15631
|
+
* @return DescribeScalingRulesResponse
|
|
14965
15632
|
*/
|
|
14966
15633
|
async describeScalingRules(request) {
|
|
14967
15634
|
let runtime = new $Util.RuntimeOptions({});
|
|
14968
15635
|
return await this.describeScalingRulesWithOptions(request, runtime);
|
|
14969
15636
|
}
|
|
15637
|
+
/**
|
|
15638
|
+
* @summary Queries scheduled tasks.
|
|
15639
|
+
*
|
|
15640
|
+
* @description You can query scheduled tasks by scaling rule, task ID, or task name.
|
|
15641
|
+
*
|
|
15642
|
+
* @param request DescribeScheduledTasksRequest
|
|
15643
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15644
|
+
* @return DescribeScheduledTasksResponse
|
|
15645
|
+
*/
|
|
14970
15646
|
async describeScheduledTasksWithOptions(request, runtime) {
|
|
14971
15647
|
tea_util_1.default.validateModel(request);
|
|
14972
15648
|
let query = {};
|
|
@@ -15019,10 +15695,25 @@ class Client extends openapi_client_1.default {
|
|
|
15019
15695
|
});
|
|
15020
15696
|
return $tea.cast(await this.callApi(params, req, runtime), new DescribeScheduledTasksResponse({}));
|
|
15021
15697
|
}
|
|
15698
|
+
/**
|
|
15699
|
+
* @summary Queries scheduled tasks.
|
|
15700
|
+
*
|
|
15701
|
+
* @description You can query scheduled tasks by scaling rule, task ID, or task name.
|
|
15702
|
+
*
|
|
15703
|
+
* @param request DescribeScheduledTasksRequest
|
|
15704
|
+
* @return DescribeScheduledTasksResponse
|
|
15705
|
+
*/
|
|
15022
15706
|
async describeScheduledTasks(request) {
|
|
15023
15707
|
let runtime = new $Util.RuntimeOptions({});
|
|
15024
15708
|
return await this.describeScheduledTasksWithOptions(request, runtime);
|
|
15025
15709
|
}
|
|
15710
|
+
/**
|
|
15711
|
+
* @summary Disassociates one or more Application Load Balancer (ALB) server groups from a scaling group.
|
|
15712
|
+
*
|
|
15713
|
+
* @param request DetachAlbServerGroupsRequest
|
|
15714
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15715
|
+
* @return DetachAlbServerGroupsResponse
|
|
15716
|
+
*/
|
|
15026
15717
|
async detachAlbServerGroupsWithOptions(request, runtime) {
|
|
15027
15718
|
tea_util_1.default.validateModel(request);
|
|
15028
15719
|
let query = {};
|
|
@@ -15063,10 +15754,23 @@ class Client extends openapi_client_1.default {
|
|
|
15063
15754
|
});
|
|
15064
15755
|
return $tea.cast(await this.callApi(params, req, runtime), new DetachAlbServerGroupsResponse({}));
|
|
15065
15756
|
}
|
|
15757
|
+
/**
|
|
15758
|
+
* @summary Disassociates one or more Application Load Balancer (ALB) server groups from a scaling group.
|
|
15759
|
+
*
|
|
15760
|
+
* @param request DetachAlbServerGroupsRequest
|
|
15761
|
+
* @return DetachAlbServerGroupsResponse
|
|
15762
|
+
*/
|
|
15066
15763
|
async detachAlbServerGroups(request) {
|
|
15067
15764
|
let runtime = new $Util.RuntimeOptions({});
|
|
15068
15765
|
return await this.detachAlbServerGroupsWithOptions(request, runtime);
|
|
15069
15766
|
}
|
|
15767
|
+
/**
|
|
15768
|
+
* @summary Disassociates one or more ApsaraDB RDS instances from a scaling group.
|
|
15769
|
+
*
|
|
15770
|
+
* @param request DetachDBInstancesRequest
|
|
15771
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15772
|
+
* @return DetachDBInstancesResponse
|
|
15773
|
+
*/
|
|
15070
15774
|
async detachDBInstancesWithOptions(request, runtime) {
|
|
15071
15775
|
tea_util_1.default.validateModel(request);
|
|
15072
15776
|
let query = {};
|
|
@@ -15110,23 +15814,31 @@ class Client extends openapi_client_1.default {
|
|
|
15110
15814
|
});
|
|
15111
15815
|
return $tea.cast(await this.callApi(params, req, runtime), new DetachDBInstancesResponse({}));
|
|
15112
15816
|
}
|
|
15817
|
+
/**
|
|
15818
|
+
* @summary Disassociates one or more ApsaraDB RDS instances from a scaling group.
|
|
15819
|
+
*
|
|
15820
|
+
* @param request DetachDBInstancesRequest
|
|
15821
|
+
* @return DetachDBInstancesResponse
|
|
15822
|
+
*/
|
|
15113
15823
|
async detachDBInstances(request) {
|
|
15114
15824
|
let runtime = new $Util.RuntimeOptions({});
|
|
15115
15825
|
return await this.detachDBInstancesWithOptions(request, runtime);
|
|
15116
15826
|
}
|
|
15117
15827
|
/**
|
|
15118
|
-
|
|
15119
|
-
|
|
15120
|
-
|
|
15121
|
-
|
|
15122
|
-
|
|
15123
|
-
|
|
15124
|
-
|
|
15125
|
-
|
|
15126
|
-
|
|
15127
|
-
|
|
15128
|
-
|
|
15129
|
-
|
|
15828
|
+
* @summary Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
|
|
15829
|
+
*
|
|
15830
|
+
* @description After ECS instances or elastic container instances are removed from a scaling group, you can call the AttachInstances operation to add the ECS instances or elastic container instances that are removed from the scaling group to other scaling groups.
|
|
15831
|
+
* After you remove an ECS instance or elastic container instance by calling the DetachInstances operation, the instance is not stopped or released.
|
|
15832
|
+
* Before you call this operation, make sure that the following conditions are met:
|
|
15833
|
+
* * The specified scaling group is enabled.
|
|
15834
|
+
* * No scaling activities in the specified scaling group are in progress.
|
|
15835
|
+
* > If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
|
|
15836
|
+
* A successful call indicates only that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity based on the value of the ScalingActivityId parameter in the response.
|
|
15837
|
+
* The number of ECS instances or elastic container instances in a scaling group after you remove a specific number of instances from the scaling group must be equal to or greater than the value of the MinSize parameter. Otherwise, an error is reported when you call the DetachInstances operation.
|
|
15838
|
+
*
|
|
15839
|
+
* @param request DetachInstancesRequest
|
|
15840
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15841
|
+
* @return DetachInstancesResponse
|
|
15130
15842
|
*/
|
|
15131
15843
|
async detachInstancesWithOptions(request, runtime) {
|
|
15132
15844
|
tea_util_1.default.validateModel(request);
|
|
@@ -15140,6 +15852,9 @@ class Client extends openapi_client_1.default {
|
|
|
15140
15852
|
if (!tea_util_1.default.isUnset(request.detachOption)) {
|
|
15141
15853
|
query["DetachOption"] = request.detachOption;
|
|
15142
15854
|
}
|
|
15855
|
+
if (!tea_util_1.default.isUnset(request.ignoreInvalidInstance)) {
|
|
15856
|
+
query["IgnoreInvalidInstance"] = request.ignoreInvalidInstance;
|
|
15857
|
+
}
|
|
15143
15858
|
if (!tea_util_1.default.isUnset(request.instanceIds)) {
|
|
15144
15859
|
query["InstanceIds"] = request.instanceIds;
|
|
15145
15860
|
}
|
|
@@ -15178,22 +15893,31 @@ class Client extends openapi_client_1.default {
|
|
|
15178
15893
|
return $tea.cast(await this.callApi(params, req, runtime), new DetachInstancesResponse({}));
|
|
15179
15894
|
}
|
|
15180
15895
|
/**
|
|
15181
|
-
|
|
15182
|
-
|
|
15183
|
-
|
|
15184
|
-
|
|
15185
|
-
|
|
15186
|
-
|
|
15187
|
-
|
|
15188
|
-
|
|
15189
|
-
|
|
15190
|
-
|
|
15191
|
-
|
|
15896
|
+
* @summary Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
|
|
15897
|
+
*
|
|
15898
|
+
* @description After ECS instances or elastic container instances are removed from a scaling group, you can call the AttachInstances operation to add the ECS instances or elastic container instances that are removed from the scaling group to other scaling groups.
|
|
15899
|
+
* After you remove an ECS instance or elastic container instance by calling the DetachInstances operation, the instance is not stopped or released.
|
|
15900
|
+
* Before you call this operation, make sure that the following conditions are met:
|
|
15901
|
+
* * The specified scaling group is enabled.
|
|
15902
|
+
* * No scaling activities in the specified scaling group are in progress.
|
|
15903
|
+
* > If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
|
|
15904
|
+
* A successful call indicates only that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity based on the value of the ScalingActivityId parameter in the response.
|
|
15905
|
+
* The number of ECS instances or elastic container instances in a scaling group after you remove a specific number of instances from the scaling group must be equal to or greater than the value of the MinSize parameter. Otherwise, an error is reported when you call the DetachInstances operation.
|
|
15906
|
+
*
|
|
15907
|
+
* @param request DetachInstancesRequest
|
|
15908
|
+
* @return DetachInstancesResponse
|
|
15192
15909
|
*/
|
|
15193
15910
|
async detachInstances(request) {
|
|
15194
15911
|
let runtime = new $Util.RuntimeOptions({});
|
|
15195
15912
|
return await this.detachInstancesWithOptions(request, runtime);
|
|
15196
15913
|
}
|
|
15914
|
+
/**
|
|
15915
|
+
* @summary Detaches one or more Classic Load Balancer (CLB) instances from a scaling group.
|
|
15916
|
+
*
|
|
15917
|
+
* @param request DetachLoadBalancersRequest
|
|
15918
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15919
|
+
* @return DetachLoadBalancersResponse
|
|
15920
|
+
*/
|
|
15197
15921
|
async detachLoadBalancersWithOptions(request, runtime) {
|
|
15198
15922
|
tea_util_1.default.validateModel(request);
|
|
15199
15923
|
let query = {};
|
|
@@ -15237,10 +15961,23 @@ class Client extends openapi_client_1.default {
|
|
|
15237
15961
|
});
|
|
15238
15962
|
return $tea.cast(await this.callApi(params, req, runtime), new DetachLoadBalancersResponse({}));
|
|
15239
15963
|
}
|
|
15964
|
+
/**
|
|
15965
|
+
* @summary Detaches one or more Classic Load Balancer (CLB) instances from a scaling group.
|
|
15966
|
+
*
|
|
15967
|
+
* @param request DetachLoadBalancersRequest
|
|
15968
|
+
* @return DetachLoadBalancersResponse
|
|
15969
|
+
*/
|
|
15240
15970
|
async detachLoadBalancers(request) {
|
|
15241
15971
|
let runtime = new $Util.RuntimeOptions({});
|
|
15242
15972
|
return await this.detachLoadBalancersWithOptions(request, runtime);
|
|
15243
15973
|
}
|
|
15974
|
+
/**
|
|
15975
|
+
* @summary Detaches one or more server groups from a scaling group. You can attach and detach the following server groups from a scaling group: Application Load Balancer (ALB) and Network Load Balancer (NLB) server groups.
|
|
15976
|
+
*
|
|
15977
|
+
* @param request DetachServerGroupsRequest
|
|
15978
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
15979
|
+
* @return DetachServerGroupsResponse
|
|
15980
|
+
*/
|
|
15244
15981
|
async detachServerGroupsWithOptions(request, runtime) {
|
|
15245
15982
|
tea_util_1.default.validateModel(request);
|
|
15246
15983
|
let query = {};
|
|
@@ -15281,20 +16018,29 @@ class Client extends openapi_client_1.default {
|
|
|
15281
16018
|
});
|
|
15282
16019
|
return $tea.cast(await this.callApi(params, req, runtime), new DetachServerGroupsResponse({}));
|
|
15283
16020
|
}
|
|
16021
|
+
/**
|
|
16022
|
+
* @summary Detaches one or more server groups from a scaling group. You can attach and detach the following server groups from a scaling group: Application Load Balancer (ALB) and Network Load Balancer (NLB) server groups.
|
|
16023
|
+
*
|
|
16024
|
+
* @param request DetachServerGroupsRequest
|
|
16025
|
+
* @return DetachServerGroupsResponse
|
|
16026
|
+
*/
|
|
15284
16027
|
async detachServerGroups(request) {
|
|
15285
16028
|
let runtime = new $Util.RuntimeOptions({});
|
|
15286
16029
|
return await this.detachServerGroupsWithOptions(request, runtime);
|
|
15287
16030
|
}
|
|
15288
16031
|
/**
|
|
15289
|
-
|
|
15290
|
-
|
|
15291
|
-
|
|
15292
|
-
|
|
15293
|
-
|
|
15294
|
-
|
|
15295
|
-
|
|
15296
|
-
|
|
15297
|
-
|
|
16032
|
+
* @summary Detaches vServer groups from a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups to improve service performance. If the load balancer currently attached to your scaling group is no longer needed to distribute the access traffic to the instances in your scaling group, you can call the DetachVServerGroups operation to detach one or more vServer groups of this load balancer from the scaling group.
|
|
16033
|
+
*
|
|
16034
|
+
* @description * When you call the DetachVServerGroups operation, you must use the following parameters to specify the vServer groups that you want to detach from your scaling group:
|
|
16035
|
+
* * LoadBalancerId: the ID of the load balancer
|
|
16036
|
+
* * VServerGroupId: the ID of the vServer group
|
|
16037
|
+
* * Port: the port number of the vServer group
|
|
16038
|
+
* * When the vServer group specified by the request parameters matches that attached to your scaling group, this operation yields a favorable result. Otherwise, the request is ignored and no error is reported.
|
|
16039
|
+
* * Before you call this operation, you must make sure that the load balancer has ceased routing the access traffic to the instances in the scaling group. Failure to do so may lead to service requests being dropped or lost during the detachment process.
|
|
16040
|
+
*
|
|
16041
|
+
* @param request DetachVServerGroupsRequest
|
|
16042
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16043
|
+
* @return DetachVServerGroupsResponse
|
|
15298
16044
|
*/
|
|
15299
16045
|
async detachVServerGroupsWithOptions(request, runtime) {
|
|
15300
16046
|
tea_util_1.default.validateModel(request);
|
|
@@ -15337,19 +16083,31 @@ class Client extends openapi_client_1.default {
|
|
|
15337
16083
|
return $tea.cast(await this.callApi(params, req, runtime), new DetachVServerGroupsResponse({}));
|
|
15338
16084
|
}
|
|
15339
16085
|
/**
|
|
15340
|
-
|
|
15341
|
-
|
|
15342
|
-
|
|
15343
|
-
|
|
15344
|
-
|
|
15345
|
-
|
|
15346
|
-
|
|
15347
|
-
|
|
16086
|
+
* @summary Detaches vServer groups from a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups to improve service performance. If the load balancer currently attached to your scaling group is no longer needed to distribute the access traffic to the instances in your scaling group, you can call the DetachVServerGroups operation to detach one or more vServer groups of this load balancer from the scaling group.
|
|
16087
|
+
*
|
|
16088
|
+
* @description * When you call the DetachVServerGroups operation, you must use the following parameters to specify the vServer groups that you want to detach from your scaling group:
|
|
16089
|
+
* * LoadBalancerId: the ID of the load balancer
|
|
16090
|
+
* * VServerGroupId: the ID of the vServer group
|
|
16091
|
+
* * Port: the port number of the vServer group
|
|
16092
|
+
* * When the vServer group specified by the request parameters matches that attached to your scaling group, this operation yields a favorable result. Otherwise, the request is ignored and no error is reported.
|
|
16093
|
+
* * Before you call this operation, you must make sure that the load balancer has ceased routing the access traffic to the instances in the scaling group. Failure to do so may lead to service requests being dropped or lost during the detachment process.
|
|
16094
|
+
*
|
|
16095
|
+
* @param request DetachVServerGroupsRequest
|
|
16096
|
+
* @return DetachVServerGroupsResponse
|
|
15348
16097
|
*/
|
|
15349
16098
|
async detachVServerGroups(request) {
|
|
15350
16099
|
let runtime = new $Util.RuntimeOptions({});
|
|
15351
16100
|
return await this.detachVServerGroupsWithOptions(request, runtime);
|
|
15352
16101
|
}
|
|
16102
|
+
/**
|
|
16103
|
+
* @summary Disables an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you currently do not need an event-triggered task, you can call the DisableAlarm operation to disable it.
|
|
16104
|
+
*
|
|
16105
|
+
* @description Before you disable an event-triggered task, make sure that the task is in the `Normal`, `Alert`, or `Insufficient Data` state.
|
|
16106
|
+
*
|
|
16107
|
+
* @param request DisableAlarmRequest
|
|
16108
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16109
|
+
* @return DisableAlarmResponse
|
|
16110
|
+
*/
|
|
15353
16111
|
async disableAlarmWithOptions(request, runtime) {
|
|
15354
16112
|
tea_util_1.default.validateModel(request);
|
|
15355
16113
|
let query = {};
|
|
@@ -15381,10 +16139,29 @@ class Client extends openapi_client_1.default {
|
|
|
15381
16139
|
});
|
|
15382
16140
|
return $tea.cast(await this.callApi(params, req, runtime), new DisableAlarmResponse({}));
|
|
15383
16141
|
}
|
|
16142
|
+
/**
|
|
16143
|
+
* @summary Disables an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you currently do not need an event-triggered task, you can call the DisableAlarm operation to disable it.
|
|
16144
|
+
*
|
|
16145
|
+
* @description Before you disable an event-triggered task, make sure that the task is in the `Normal`, `Alert`, or `Insufficient Data` state.
|
|
16146
|
+
*
|
|
16147
|
+
* @param request DisableAlarmRequest
|
|
16148
|
+
* @return DisableAlarmResponse
|
|
16149
|
+
*/
|
|
15384
16150
|
async disableAlarm(request) {
|
|
15385
16151
|
let runtime = new $Util.RuntimeOptions({});
|
|
15386
16152
|
return await this.disableAlarmWithOptions(request, runtime);
|
|
15387
16153
|
}
|
|
16154
|
+
/**
|
|
16155
|
+
* @summary Disables a scaling group.
|
|
16156
|
+
*
|
|
16157
|
+
* @description Before you call this operation to disable a scaling group, take note of the following items:
|
|
16158
|
+
* * When you call this operation, ongoing scaling activities will continue until they are complete, but new activities will be rejected.
|
|
16159
|
+
* * You can disable only scaling groups that are in the Active state.
|
|
16160
|
+
*
|
|
16161
|
+
* @param request DisableScalingGroupRequest
|
|
16162
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16163
|
+
* @return DisableScalingGroupResponse
|
|
16164
|
+
*/
|
|
15388
16165
|
async disableScalingGroupWithOptions(request, runtime) {
|
|
15389
16166
|
tea_util_1.default.validateModel(request);
|
|
15390
16167
|
let query = {};
|
|
@@ -15419,10 +16196,27 @@ class Client extends openapi_client_1.default {
|
|
|
15419
16196
|
});
|
|
15420
16197
|
return $tea.cast(await this.callApi(params, req, runtime), new DisableScalingGroupResponse({}));
|
|
15421
16198
|
}
|
|
16199
|
+
/**
|
|
16200
|
+
* @summary Disables a scaling group.
|
|
16201
|
+
*
|
|
16202
|
+
* @description Before you call this operation to disable a scaling group, take note of the following items:
|
|
16203
|
+
* * When you call this operation, ongoing scaling activities will continue until they are complete, but new activities will be rejected.
|
|
16204
|
+
* * You can disable only scaling groups that are in the Active state.
|
|
16205
|
+
*
|
|
16206
|
+
* @param request DisableScalingGroupRequest
|
|
16207
|
+
* @return DisableScalingGroupResponse
|
|
16208
|
+
*/
|
|
15422
16209
|
async disableScalingGroup(request) {
|
|
15423
16210
|
let runtime = new $Util.RuntimeOptions({});
|
|
15424
16211
|
return await this.disableScalingGroupWithOptions(request, runtime);
|
|
15425
16212
|
}
|
|
16213
|
+
/**
|
|
16214
|
+
* @summary Enables an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you want to reuse an event-triggered task that is in the Disabled state, you can call the EnableAlarm operation to enable it.
|
|
16215
|
+
*
|
|
16216
|
+
* @param request EnableAlarmRequest
|
|
16217
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16218
|
+
* @return EnableAlarmResponse
|
|
16219
|
+
*/
|
|
15426
16220
|
async enableAlarmWithOptions(request, runtime) {
|
|
15427
16221
|
tea_util_1.default.validateModel(request);
|
|
15428
16222
|
let query = {};
|
|
@@ -15454,20 +16248,28 @@ class Client extends openapi_client_1.default {
|
|
|
15454
16248
|
});
|
|
15455
16249
|
return $tea.cast(await this.callApi(params, req, runtime), new EnableAlarmResponse({}));
|
|
15456
16250
|
}
|
|
16251
|
+
/**
|
|
16252
|
+
* @summary Enables an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you want to reuse an event-triggered task that is in the Disabled state, you can call the EnableAlarm operation to enable it.
|
|
16253
|
+
*
|
|
16254
|
+
* @param request EnableAlarmRequest
|
|
16255
|
+
* @return EnableAlarmResponse
|
|
16256
|
+
*/
|
|
15457
16257
|
async enableAlarm(request) {
|
|
15458
16258
|
let runtime = new $Util.RuntimeOptions({});
|
|
15459
16259
|
return await this.enableAlarmWithOptions(request, runtime);
|
|
15460
16260
|
}
|
|
15461
16261
|
/**
|
|
15462
|
-
|
|
15463
|
-
|
|
15464
|
-
|
|
15465
|
-
|
|
15466
|
-
|
|
15467
|
-
|
|
15468
|
-
|
|
15469
|
-
|
|
15470
|
-
|
|
16262
|
+
* @summary Enables a scaling group.
|
|
16263
|
+
*
|
|
16264
|
+
* @description You can call this operation to enable a scaling group that is in the Inactive state and has an instance configuration source. The instance configuration source can be a scaling configuration, a launch template, or an Elastic Compute Service (ECS) instance that you specified when you created the scaling group. If a scaling group is not in the Inactive state or does not have an active instance configuration source, you cannot call this operation to enable the scaling group.
|
|
16265
|
+
* > A scaling group can have only one active instance configuration source. When you call this operation to enable a scaling group, you can specify a scaling configuration or a launch template for the scaling group. If an instance configuration source has been configured for the scaling group before you call this operation, the scaling configuration or launch template that you specify in the request overwrites the original scaling configuration or launch template.
|
|
16266
|
+
* If you specify a value for the InstanceId parameter when you call the operation, Auto Scaling checks whether the total number of ECS instances is within the range allowed in the scaling group after you call the operation.
|
|
16267
|
+
* * If the total number of ECS instances is less than the minimum number of instances allowed in the scaling group after you call the operation, Auto Scaling automatically creates the required number of pay-as-you-go ECS instances and adds the instances to the scaling group to reach the minimum number. For example, if the minimum number of instances allowed in your scaling group is five, and you specify the InstanceId parameter to add two created ECS instances to the scaling group, Auto Scaling automatically creates three instances in the scaling group after the two instances are added.
|
|
16268
|
+
* * If the value of the TotalCapactiy parameter is greater than the value of the MaxSize parameter, the call fails.
|
|
16269
|
+
*
|
|
16270
|
+
* @param request EnableScalingGroupRequest
|
|
16271
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16272
|
+
* @return EnableScalingGroupResponse
|
|
15471
16273
|
*/
|
|
15472
16274
|
async enableScalingGroupWithOptions(request, runtime) {
|
|
15473
16275
|
tea_util_1.default.validateModel(request);
|
|
@@ -15525,19 +16327,34 @@ class Client extends openapi_client_1.default {
|
|
|
15525
16327
|
return $tea.cast(await this.callApi(params, req, runtime), new EnableScalingGroupResponse({}));
|
|
15526
16328
|
}
|
|
15527
16329
|
/**
|
|
15528
|
-
|
|
15529
|
-
|
|
15530
|
-
|
|
15531
|
-
|
|
15532
|
-
|
|
15533
|
-
|
|
15534
|
-
|
|
15535
|
-
|
|
16330
|
+
* @summary Enables a scaling group.
|
|
16331
|
+
*
|
|
16332
|
+
* @description You can call this operation to enable a scaling group that is in the Inactive state and has an instance configuration source. The instance configuration source can be a scaling configuration, a launch template, or an Elastic Compute Service (ECS) instance that you specified when you created the scaling group. If a scaling group is not in the Inactive state or does not have an active instance configuration source, you cannot call this operation to enable the scaling group.
|
|
16333
|
+
* > A scaling group can have only one active instance configuration source. When you call this operation to enable a scaling group, you can specify a scaling configuration or a launch template for the scaling group. If an instance configuration source has been configured for the scaling group before you call this operation, the scaling configuration or launch template that you specify in the request overwrites the original scaling configuration or launch template.
|
|
16334
|
+
* If you specify a value for the InstanceId parameter when you call the operation, Auto Scaling checks whether the total number of ECS instances is within the range allowed in the scaling group after you call the operation.
|
|
16335
|
+
* * If the total number of ECS instances is less than the minimum number of instances allowed in the scaling group after you call the operation, Auto Scaling automatically creates the required number of pay-as-you-go ECS instances and adds the instances to the scaling group to reach the minimum number. For example, if the minimum number of instances allowed in your scaling group is five, and you specify the InstanceId parameter to add two created ECS instances to the scaling group, Auto Scaling automatically creates three instances in the scaling group after the two instances are added.
|
|
16336
|
+
* * If the value of the TotalCapactiy parameter is greater than the value of the MaxSize parameter, the call fails.
|
|
16337
|
+
*
|
|
16338
|
+
* @param request EnableScalingGroupRequest
|
|
16339
|
+
* @return EnableScalingGroupResponse
|
|
15536
16340
|
*/
|
|
15537
16341
|
async enableScalingGroup(request) {
|
|
15538
16342
|
let runtime = new $Util.RuntimeOptions({});
|
|
15539
16343
|
return await this.enableScalingGroupWithOptions(request, runtime);
|
|
15540
16344
|
}
|
|
16345
|
+
/**
|
|
16346
|
+
* @summary Puts an Elastic Compute Service (ECS) instance into the Standby state.
|
|
16347
|
+
*
|
|
16348
|
+
* @description ## Description
|
|
16349
|
+
* * If you call the operation to put an ECS instance in a scaling group that is associated with a Classic Load Balancer (CLB) instance into the Standby state, the weight of the ECS instance as a backend server of the CLB instance is set to 0.
|
|
16350
|
+
* * You can remove an instance that is in the Standby state from a scaling group, and then release the instance.
|
|
16351
|
+
* * ECS instances that are in the Standby state are not removed from the scaling group during scale-in activities triggered by event-triggered tasks.
|
|
16352
|
+
* * If Auto Scaling considers an ECS instance that is in the Standby state unhealthy, for example, the ECS instance is being stopped or being restarted, Auto Scaling does not update the health status of the ECS instance or trigger scale-in activities to remove the ECS instance from the scaling group. Auto Scaling updates the health status of the ECS instance only when the ECS instance is no longer in the Standby state.
|
|
16353
|
+
*
|
|
16354
|
+
* @param request EnterStandbyRequest
|
|
16355
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16356
|
+
* @return EnterStandbyResponse
|
|
16357
|
+
*/
|
|
15541
16358
|
async enterStandbyWithOptions(request, runtime) {
|
|
15542
16359
|
tea_util_1.default.validateModel(request);
|
|
15543
16360
|
let query = {};
|
|
@@ -15575,23 +16392,37 @@ class Client extends openapi_client_1.default {
|
|
|
15575
16392
|
});
|
|
15576
16393
|
return $tea.cast(await this.callApi(params, req, runtime), new EnterStandbyResponse({}));
|
|
15577
16394
|
}
|
|
16395
|
+
/**
|
|
16396
|
+
* @summary Puts an Elastic Compute Service (ECS) instance into the Standby state.
|
|
16397
|
+
*
|
|
16398
|
+
* @description ## Description
|
|
16399
|
+
* * If you call the operation to put an ECS instance in a scaling group that is associated with a Classic Load Balancer (CLB) instance into the Standby state, the weight of the ECS instance as a backend server of the CLB instance is set to 0.
|
|
16400
|
+
* * You can remove an instance that is in the Standby state from a scaling group, and then release the instance.
|
|
16401
|
+
* * ECS instances that are in the Standby state are not removed from the scaling group during scale-in activities triggered by event-triggered tasks.
|
|
16402
|
+
* * If Auto Scaling considers an ECS instance that is in the Standby state unhealthy, for example, the ECS instance is being stopped or being restarted, Auto Scaling does not update the health status of the ECS instance or trigger scale-in activities to remove the ECS instance from the scaling group. Auto Scaling updates the health status of the ECS instance only when the ECS instance is no longer in the Standby state.
|
|
16403
|
+
*
|
|
16404
|
+
* @param request EnterStandbyRequest
|
|
16405
|
+
* @return EnterStandbyResponse
|
|
16406
|
+
*/
|
|
15578
16407
|
async enterStandby(request) {
|
|
15579
16408
|
let runtime = new $Util.RuntimeOptions({});
|
|
15580
16409
|
return await this.enterStandbyWithOptions(request, runtime);
|
|
15581
16410
|
}
|
|
15582
16411
|
/**
|
|
15583
|
-
|
|
15584
|
-
|
|
15585
|
-
|
|
15586
|
-
|
|
15587
|
-
|
|
15588
|
-
|
|
15589
|
-
|
|
15590
|
-
|
|
15591
|
-
|
|
15592
|
-
|
|
15593
|
-
|
|
15594
|
-
|
|
16412
|
+
* @summary Executes a scaling rule.
|
|
16413
|
+
*
|
|
16414
|
+
* @description Before you call this operation, take note of the following items:
|
|
16415
|
+
* * The scaling group is in the Active state.
|
|
16416
|
+
* * No scaling activities in the scaling group are in progress.
|
|
16417
|
+
* If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
|
|
16418
|
+
* A successful call indicates that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity by using the value of the ScalingActivityId parameter in the response.
|
|
16419
|
+
* If the addition of a specified number of Elastic Compute Service (ECS) instances to a scaling group causes the total number of ECS instances in the scaling group to exceed the maximum number of instances allowed, Auto Scaling adds only a specific number of ECS instances to ensure that the total number of instances is equal to the maximum number of instances.
|
|
16420
|
+
* If the removal of a specified number of ECS instances from a scaling group causes the total number of ECS instances in the scaling group to drop below the minimum number of instances allowed, Auto Scaling removes only a specific number of ECS instances to ensure that the total number of instances is equal to the minimum number of instances.
|
|
16421
|
+
* You can specify only a limited number of ECS instances in each adjustment. For more information, see the description of the AdjustmentValue parameter in the CreateScalingRule topic.
|
|
16422
|
+
*
|
|
16423
|
+
* @param request ExecuteScalingRuleRequest
|
|
16424
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16425
|
+
* @return ExecuteScalingRuleResponse
|
|
15595
16426
|
*/
|
|
15596
16427
|
async executeScalingRuleWithOptions(request, runtime) {
|
|
15597
16428
|
tea_util_1.default.validateModel(request);
|
|
@@ -15640,22 +16471,34 @@ class Client extends openapi_client_1.default {
|
|
|
15640
16471
|
return $tea.cast(await this.callApi(params, req, runtime), new ExecuteScalingRuleResponse({}));
|
|
15641
16472
|
}
|
|
15642
16473
|
/**
|
|
15643
|
-
|
|
15644
|
-
|
|
15645
|
-
|
|
15646
|
-
|
|
15647
|
-
|
|
15648
|
-
|
|
15649
|
-
|
|
15650
|
-
|
|
15651
|
-
|
|
15652
|
-
|
|
15653
|
-
|
|
16474
|
+
* @summary Executes a scaling rule.
|
|
16475
|
+
*
|
|
16476
|
+
* @description Before you call this operation, take note of the following items:
|
|
16477
|
+
* * The scaling group is in the Active state.
|
|
16478
|
+
* * No scaling activities in the scaling group are in progress.
|
|
16479
|
+
* If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
|
|
16480
|
+
* A successful call indicates that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity by using the value of the ScalingActivityId parameter in the response.
|
|
16481
|
+
* If the addition of a specified number of Elastic Compute Service (ECS) instances to a scaling group causes the total number of ECS instances in the scaling group to exceed the maximum number of instances allowed, Auto Scaling adds only a specific number of ECS instances to ensure that the total number of instances is equal to the maximum number of instances.
|
|
16482
|
+
* If the removal of a specified number of ECS instances from a scaling group causes the total number of ECS instances in the scaling group to drop below the minimum number of instances allowed, Auto Scaling removes only a specific number of ECS instances to ensure that the total number of instances is equal to the minimum number of instances.
|
|
16483
|
+
* You can specify only a limited number of ECS instances in each adjustment. For more information, see the description of the AdjustmentValue parameter in the CreateScalingRule topic.
|
|
16484
|
+
*
|
|
16485
|
+
* @param request ExecuteScalingRuleRequest
|
|
16486
|
+
* @return ExecuteScalingRuleResponse
|
|
15654
16487
|
*/
|
|
15655
16488
|
async executeScalingRule(request) {
|
|
15656
16489
|
let runtime = new $Util.RuntimeOptions({});
|
|
15657
16490
|
return await this.executeScalingRuleWithOptions(request, runtime);
|
|
15658
16491
|
}
|
|
16492
|
+
/**
|
|
16493
|
+
* @summary Moves an Elastic Compute Service (ECS) instance out of the Standby state.
|
|
16494
|
+
*
|
|
16495
|
+
* @description ## Description
|
|
16496
|
+
* If your scaling group is associated with a Classic Load Balancer (CLB) instance and you move an ECS instance in your scaling group out of the Standby state, the weight of the ECS instance is reset to the value that is specified in the scaling configuration of your scaling group.
|
|
16497
|
+
*
|
|
16498
|
+
* @param request ExitStandbyRequest
|
|
16499
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16500
|
+
* @return ExitStandbyResponse
|
|
16501
|
+
*/
|
|
15659
16502
|
async exitStandbyWithOptions(request, runtime) {
|
|
15660
16503
|
tea_util_1.default.validateModel(request);
|
|
15661
16504
|
let query = {};
|
|
@@ -15696,10 +16539,26 @@ class Client extends openapi_client_1.default {
|
|
|
15696
16539
|
});
|
|
15697
16540
|
return $tea.cast(await this.callApi(params, req, runtime), new ExitStandbyResponse({}));
|
|
15698
16541
|
}
|
|
16542
|
+
/**
|
|
16543
|
+
* @summary Moves an Elastic Compute Service (ECS) instance out of the Standby state.
|
|
16544
|
+
*
|
|
16545
|
+
* @description ## Description
|
|
16546
|
+
* If your scaling group is associated with a Classic Load Balancer (CLB) instance and you move an ECS instance in your scaling group out of the Standby state, the weight of the ECS instance is reset to the value that is specified in the scaling configuration of your scaling group.
|
|
16547
|
+
*
|
|
16548
|
+
* @param request ExitStandbyRequest
|
|
16549
|
+
* @return ExitStandbyResponse
|
|
16550
|
+
*/
|
|
15699
16551
|
async exitStandby(request) {
|
|
15700
16552
|
let runtime = new $Util.RuntimeOptions({});
|
|
15701
16553
|
return await this.exitStandbyWithOptions(request, runtime);
|
|
15702
16554
|
}
|
|
16555
|
+
/**
|
|
16556
|
+
* @summary Queries the tag keys added to Auto Scaling resources. Querying tag keys facilitates easier classification, identification, and monitoring of your Auto Scaling resources, thereby enhancing the flexibility and convenience of your resource management processes.
|
|
16557
|
+
*
|
|
16558
|
+
* @param request ListTagKeysRequest
|
|
16559
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16560
|
+
* @return ListTagKeysResponse
|
|
16561
|
+
*/
|
|
15703
16562
|
async listTagKeysWithOptions(request, runtime) {
|
|
15704
16563
|
tea_util_1.default.validateModel(request);
|
|
15705
16564
|
let query = {};
|
|
@@ -15737,10 +16596,23 @@ class Client extends openapi_client_1.default {
|
|
|
15737
16596
|
});
|
|
15738
16597
|
return $tea.cast(await this.callApi(params, req, runtime), new ListTagKeysResponse({}));
|
|
15739
16598
|
}
|
|
16599
|
+
/**
|
|
16600
|
+
* @summary Queries the tag keys added to Auto Scaling resources. Querying tag keys facilitates easier classification, identification, and monitoring of your Auto Scaling resources, thereby enhancing the flexibility and convenience of your resource management processes.
|
|
16601
|
+
*
|
|
16602
|
+
* @param request ListTagKeysRequest
|
|
16603
|
+
* @return ListTagKeysResponse
|
|
16604
|
+
*/
|
|
15740
16605
|
async listTagKeys(request) {
|
|
15741
16606
|
let runtime = new $Util.RuntimeOptions({});
|
|
15742
16607
|
return await this.listTagKeysWithOptions(request, runtime);
|
|
15743
16608
|
}
|
|
16609
|
+
/**
|
|
16610
|
+
* @summary Queries tags that are added to one or more Auto Scaling resources.
|
|
16611
|
+
*
|
|
16612
|
+
* @param request ListTagResourcesRequest
|
|
16613
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16614
|
+
* @return ListTagResourcesResponse
|
|
16615
|
+
*/
|
|
15744
16616
|
async listTagResourcesWithOptions(request, runtime) {
|
|
15745
16617
|
tea_util_1.default.validateModel(request);
|
|
15746
16618
|
let query = {};
|
|
@@ -15781,10 +16653,23 @@ class Client extends openapi_client_1.default {
|
|
|
15781
16653
|
});
|
|
15782
16654
|
return $tea.cast(await this.callApi(params, req, runtime), new ListTagResourcesResponse({}));
|
|
15783
16655
|
}
|
|
16656
|
+
/**
|
|
16657
|
+
* @summary Queries tags that are added to one or more Auto Scaling resources.
|
|
16658
|
+
*
|
|
16659
|
+
* @param request ListTagResourcesRequest
|
|
16660
|
+
* @return ListTagResourcesResponse
|
|
16661
|
+
*/
|
|
15784
16662
|
async listTagResources(request) {
|
|
15785
16663
|
let runtime = new $Util.RuntimeOptions({});
|
|
15786
16664
|
return await this.listTagResourcesWithOptions(request, runtime);
|
|
15787
16665
|
}
|
|
16666
|
+
/**
|
|
16667
|
+
* @summary Queries the tag keys associated with Auto Scaling resources to facilitate a deeper comprehension of those resources. By doing so, you can categorize and manage your Auto Scaling resources more efficiently.
|
|
16668
|
+
*
|
|
16669
|
+
* @param request ListTagValuesRequest
|
|
16670
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16671
|
+
* @return ListTagValuesResponse
|
|
16672
|
+
*/
|
|
15788
16673
|
async listTagValuesWithOptions(request, runtime) {
|
|
15789
16674
|
tea_util_1.default.validateModel(request);
|
|
15790
16675
|
let query = {};
|
|
@@ -15825,20 +16710,28 @@ class Client extends openapi_client_1.default {
|
|
|
15825
16710
|
});
|
|
15826
16711
|
return $tea.cast(await this.callApi(params, req, runtime), new ListTagValuesResponse({}));
|
|
15827
16712
|
}
|
|
16713
|
+
/**
|
|
16714
|
+
* @summary Queries the tag keys associated with Auto Scaling resources to facilitate a deeper comprehension of those resources. By doing so, you can categorize and manage your Auto Scaling resources more efficiently.
|
|
16715
|
+
*
|
|
16716
|
+
* @param request ListTagValuesRequest
|
|
16717
|
+
* @return ListTagValuesResponse
|
|
16718
|
+
*/
|
|
15828
16719
|
async listTagValues(request) {
|
|
15829
16720
|
let runtime = new $Util.RuntimeOptions({});
|
|
15830
16721
|
return await this.listTagValuesWithOptions(request, runtime);
|
|
15831
16722
|
}
|
|
15832
16723
|
/**
|
|
15833
|
-
|
|
15834
|
-
|
|
15835
|
-
|
|
15836
|
-
|
|
15837
|
-
|
|
15838
|
-
|
|
15839
|
-
|
|
15840
|
-
|
|
15841
|
-
|
|
16724
|
+
* @summary Modifies an event-triggered task.
|
|
16725
|
+
*
|
|
16726
|
+
* @description * If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using the custom metrics. For more information, see [Custom monitoring event-triggered tasks](https://help.aliyun.com/document_detail/74861.html).
|
|
16727
|
+
* * When you create an event-triggered task, you must specify the MetricName, DimensionKey, and DimensionValue parameters to determine the range of statistics that you want to aggregate for the metrics of the scaling group. For example, you can specify the user_id and scaling_group dimensions for an event-triggered task to aggregate monitoring data of all Elastic Compute Service (ECS) instances or elastic container instances in a scaling group within an Alibaba Cloud account.
|
|
16728
|
+
* * If you set the MetricType parameter to custom, the valid values are your custom metrics.
|
|
16729
|
+
* * For information about the metrics that are supported if you set the MetricType parameter to system, see[ Event-triggered task for system monitoring](https://help.aliyun.com/document_detail/74854.html).
|
|
16730
|
+
* > The user_id and scaling_group dimensions are automatically populated. You need to only specify the device and state dimensions. For more information, see the `DimensionKey` and `DimensionValue` parameters in the "Request parameters" section of this topic.
|
|
16731
|
+
*
|
|
16732
|
+
* @param request ModifyAlarmRequest
|
|
16733
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16734
|
+
* @return ModifyAlarmResponse
|
|
15842
16735
|
*/
|
|
15843
16736
|
async modifyAlarmWithOptions(request, runtime) {
|
|
15844
16737
|
tea_util_1.default.validateModel(request);
|
|
@@ -15917,25 +16810,29 @@ class Client extends openapi_client_1.default {
|
|
|
15917
16810
|
return $tea.cast(await this.callApi(params, req, runtime), new ModifyAlarmResponse({}));
|
|
15918
16811
|
}
|
|
15919
16812
|
/**
|
|
15920
|
-
|
|
15921
|
-
|
|
15922
|
-
|
|
15923
|
-
|
|
15924
|
-
|
|
15925
|
-
|
|
15926
|
-
|
|
15927
|
-
|
|
16813
|
+
* @summary Modifies an event-triggered task.
|
|
16814
|
+
*
|
|
16815
|
+
* @description * If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using the custom metrics. For more information, see [Custom monitoring event-triggered tasks](https://help.aliyun.com/document_detail/74861.html).
|
|
16816
|
+
* * When you create an event-triggered task, you must specify the MetricName, DimensionKey, and DimensionValue parameters to determine the range of statistics that you want to aggregate for the metrics of the scaling group. For example, you can specify the user_id and scaling_group dimensions for an event-triggered task to aggregate monitoring data of all Elastic Compute Service (ECS) instances or elastic container instances in a scaling group within an Alibaba Cloud account.
|
|
16817
|
+
* * If you set the MetricType parameter to custom, the valid values are your custom metrics.
|
|
16818
|
+
* * For information about the metrics that are supported if you set the MetricType parameter to system, see[ Event-triggered task for system monitoring](https://help.aliyun.com/document_detail/74854.html).
|
|
16819
|
+
* > The user_id and scaling_group dimensions are automatically populated. You need to only specify the device and state dimensions. For more information, see the `DimensionKey` and `DimensionValue` parameters in the "Request parameters" section of this topic.
|
|
16820
|
+
*
|
|
16821
|
+
* @param request ModifyAlarmRequest
|
|
16822
|
+
* @return ModifyAlarmResponse
|
|
15928
16823
|
*/
|
|
15929
16824
|
async modifyAlarm(request) {
|
|
15930
16825
|
let runtime = new $Util.RuntimeOptions({});
|
|
15931
16826
|
return await this.modifyAlarmWithOptions(request, runtime);
|
|
15932
16827
|
}
|
|
15933
16828
|
/**
|
|
15934
|
-
|
|
15935
|
-
|
|
15936
|
-
|
|
15937
|
-
|
|
15938
|
-
|
|
16829
|
+
* @summary Modifies a scaling configuration for a scaling group that contains elastic container instances.
|
|
16830
|
+
*
|
|
16831
|
+
* @description If you want to change the name of a scaling configuration in a scaling group, make sure that the new name is unique within the scaling group.
|
|
16832
|
+
*
|
|
16833
|
+
* @param request ModifyEciScalingConfigurationRequest
|
|
16834
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
16835
|
+
* @return ModifyEciScalingConfigurationResponse
|
|
15939
16836
|
*/
|
|
15940
16837
|
async modifyEciScalingConfigurationWithOptions(request, runtime) {
|
|
15941
16838
|
tea_util_1.default.validateModel(request);
|
|
@@ -16107,15 +17004,24 @@ class Client extends openapi_client_1.default {
|
|
|
16107
17004
|
return $tea.cast(await this.callApi(params, req, runtime), new ModifyEciScalingConfigurationResponse({}));
|
|
16108
17005
|
}
|
|
16109
17006
|
/**
|
|
16110
|
-
|
|
16111
|
-
|
|
16112
|
-
|
|
16113
|
-
|
|
17007
|
+
* @summary Modifies a scaling configuration for a scaling group that contains elastic container instances.
|
|
17008
|
+
*
|
|
17009
|
+
* @description If you want to change the name of a scaling configuration in a scaling group, make sure that the new name is unique within the scaling group.
|
|
17010
|
+
*
|
|
17011
|
+
* @param request ModifyEciScalingConfigurationRequest
|
|
17012
|
+
* @return ModifyEciScalingConfigurationResponse
|
|
16114
17013
|
*/
|
|
16115
17014
|
async modifyEciScalingConfiguration(request) {
|
|
16116
17015
|
let runtime = new $Util.RuntimeOptions({});
|
|
16117
17016
|
return await this.modifyEciScalingConfigurationWithOptions(request, runtime);
|
|
16118
17017
|
}
|
|
17018
|
+
/**
|
|
17019
|
+
* @summary Modifies the attributes of an Elastic Compute Service (ECS) instance in a scaling group. You can call the ModifyInstanceAttribute operation to modify the lifecycle management attribute of a manually added ECS instance in a scaling group.
|
|
17020
|
+
*
|
|
17021
|
+
* @param request ModifyInstanceAttributeRequest
|
|
17022
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
17023
|
+
* @return ModifyInstanceAttributeResponse
|
|
17024
|
+
*/
|
|
16119
17025
|
async modifyInstanceAttributeWithOptions(request, runtime) {
|
|
16120
17026
|
tea_util_1.default.validateModel(request);
|
|
16121
17027
|
let query = {};
|
|
@@ -16153,18 +17059,26 @@ class Client extends openapi_client_1.default {
|
|
|
16153
17059
|
});
|
|
16154
17060
|
return $tea.cast(await this.callApi(params, req, runtime), new ModifyInstanceAttributeResponse({}));
|
|
16155
17061
|
}
|
|
17062
|
+
/**
|
|
17063
|
+
* @summary Modifies the attributes of an Elastic Compute Service (ECS) instance in a scaling group. You can call the ModifyInstanceAttribute operation to modify the lifecycle management attribute of a manually added ECS instance in a scaling group.
|
|
17064
|
+
*
|
|
17065
|
+
* @param request ModifyInstanceAttributeRequest
|
|
17066
|
+
* @return ModifyInstanceAttributeResponse
|
|
17067
|
+
*/
|
|
16156
17068
|
async modifyInstanceAttribute(request) {
|
|
16157
17069
|
let runtime = new $Util.RuntimeOptions({});
|
|
16158
17070
|
return await this.modifyInstanceAttributeWithOptions(request, runtime);
|
|
16159
17071
|
}
|
|
16160
17072
|
/**
|
|
16161
|
-
|
|
16162
|
-
|
|
16163
|
-
|
|
16164
|
-
|
|
16165
|
-
|
|
16166
|
-
|
|
16167
|
-
|
|
17073
|
+
* @summary Modifies a lifecycle hook.
|
|
17074
|
+
*
|
|
17075
|
+
* @description You can use one of the following methods to specify the lifecycle hook that you want to modify:
|
|
17076
|
+
* * Specify the lifecycle hook ID by using the LifecycleHookId parameter. When you use this method, the ScalingGroupId and LifecycleHookName parameters are ignored.
|
|
17077
|
+
* * Specify the scaling group ID by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter.
|
|
17078
|
+
*
|
|
17079
|
+
* @param request ModifyLifecycleHookRequest
|
|
17080
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
17081
|
+
* @return ModifyLifecycleHookResponse
|
|
16168
17082
|
*/
|
|
16169
17083
|
async modifyLifecycleHookWithOptions(request, runtime) {
|
|
16170
17084
|
tea_util_1.default.validateModel(request);
|
|
@@ -16225,17 +17139,26 @@ class Client extends openapi_client_1.default {
|
|
|
16225
17139
|
return $tea.cast(await this.callApi(params, req, runtime), new ModifyLifecycleHookResponse({}));
|
|
16226
17140
|
}
|
|
16227
17141
|
/**
|
|
16228
|
-
|
|
16229
|
-
|
|
16230
|
-
|
|
16231
|
-
|
|
16232
|
-
|
|
16233
|
-
|
|
17142
|
+
* @summary Modifies a lifecycle hook.
|
|
17143
|
+
*
|
|
17144
|
+
* @description You can use one of the following methods to specify the lifecycle hook that you want to modify:
|
|
17145
|
+
* * Specify the lifecycle hook ID by using the LifecycleHookId parameter. When you use this method, the ScalingGroupId and LifecycleHookName parameters are ignored.
|
|
17146
|
+
* * Specify the scaling group ID by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter.
|
|
17147
|
+
*
|
|
17148
|
+
* @param request ModifyLifecycleHookRequest
|
|
17149
|
+
* @return ModifyLifecycleHookResponse
|
|
16234
17150
|
*/
|
|
16235
17151
|
async modifyLifecycleHook(request) {
|
|
16236
17152
|
let runtime = new $Util.RuntimeOptions({});
|
|
16237
17153
|
return await this.modifyLifecycleHookWithOptions(request, runtime);
|
|
16238
17154
|
}
|
|
17155
|
+
/**
|
|
17156
|
+
* @summary Modifies a notification.
|
|
17157
|
+
*
|
|
17158
|
+
* @param request ModifyNotificationConfigurationRequest
|
|
17159
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
17160
|
+
* @return ModifyNotificationConfigurationResponse
|
|
17161
|
+
*/
|
|
16239
17162
|
async modifyNotificationConfigurationWithOptions(request, runtime) {
|
|
16240
17163
|
tea_util_1.default.validateModel(request);
|
|
16241
17164
|
let query = {};
|
|
@@ -16273,16 +17196,24 @@ class Client extends openapi_client_1.default {
|
|
|
16273
17196
|
});
|
|
16274
17197
|
return $tea.cast(await this.callApi(params, req, runtime), new ModifyNotificationConfigurationResponse({}));
|
|
16275
17198
|
}
|
|
17199
|
+
/**
|
|
17200
|
+
* @summary Modifies a notification.
|
|
17201
|
+
*
|
|
17202
|
+
* @param request ModifyNotificationConfigurationRequest
|
|
17203
|
+
* @return ModifyNotificationConfigurationResponse
|
|
17204
|
+
*/
|
|
16276
17205
|
async modifyNotificationConfiguration(request) {
|
|
16277
17206
|
let runtime = new $Util.RuntimeOptions({});
|
|
16278
17207
|
return await this.modifyNotificationConfigurationWithOptions(request, runtime);
|
|
16279
17208
|
}
|
|
16280
17209
|
/**
|
|
16281
|
-
|
|
16282
|
-
|
|
16283
|
-
|
|
16284
|
-
|
|
16285
|
-
|
|
17210
|
+
* @summary Modifies a scaling configuration.
|
|
17211
|
+
*
|
|
17212
|
+
* @description You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
|
|
17213
|
+
*
|
|
17214
|
+
* @param tmpReq ModifyScalingConfigurationRequest
|
|
17215
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
17216
|
+
* @return ModifyScalingConfigurationResponse
|
|
16286
17217
|
*/
|
|
16287
17218
|
async modifyScalingConfigurationWithOptions(tmpReq, runtime) {
|
|
16288
17219
|
tea_util_1.default.validateModel(tmpReq);
|
|
@@ -16468,31 +17399,35 @@ class Client extends openapi_client_1.default {
|
|
|
16468
17399
|
return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingConfigurationResponse({}));
|
|
16469
17400
|
}
|
|
16470
17401
|
/**
|
|
16471
|
-
|
|
16472
|
-
|
|
16473
|
-
|
|
16474
|
-
|
|
17402
|
+
* @summary Modifies a scaling configuration.
|
|
17403
|
+
*
|
|
17404
|
+
* @description You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
|
|
17405
|
+
*
|
|
17406
|
+
* @param request ModifyScalingConfigurationRequest
|
|
17407
|
+
* @return ModifyScalingConfigurationResponse
|
|
16475
17408
|
*/
|
|
16476
17409
|
async modifyScalingConfiguration(request) {
|
|
16477
17410
|
let runtime = new $Util.RuntimeOptions({});
|
|
16478
17411
|
return await this.modifyScalingConfigurationWithOptions(request, runtime);
|
|
16479
17412
|
}
|
|
16480
17413
|
/**
|
|
16481
|
-
|
|
16482
|
-
|
|
16483
|
-
|
|
16484
|
-
|
|
16485
|
-
|
|
16486
|
-
|
|
16487
|
-
|
|
16488
|
-
|
|
16489
|
-
|
|
16490
|
-
|
|
16491
|
-
|
|
16492
|
-
|
|
16493
|
-
|
|
16494
|
-
|
|
16495
|
-
|
|
17414
|
+
* @summary Modifies a scaling group.
|
|
17415
|
+
*
|
|
17416
|
+
* @description * You cannot call this operation to modify the settings of the following parameters:
|
|
17417
|
+
* * RegionId
|
|
17418
|
+
* * LoadBalancerId
|
|
17419
|
+
* > If you want to change the CLB instances that are associated with your scaling group, call the AttachLoadBalancers and DetachLoadBalancers operations.
|
|
17420
|
+
* * DBInstanceId
|
|
17421
|
+
* > If you want to change the ApsaraDB RDS instances that are associated with your scaling group, call the AttachDBInstances and DetachDBInstances operations.
|
|
17422
|
+
* * You can modify only scaling groups that are in the Active or Inactive state.
|
|
17423
|
+
* * If you enable a new scaling configuration, Elastic Compute Service (ECS) instances that are created based on the previous scaling configuration still run as expected in the scaling group.
|
|
17424
|
+
* * If the total number of instances in the scaling group is greater than the allowed maximum number after you change the value of the MaxSize parameter, Auto Scaling automatically removes instances from the scaling group to ensure that the number of instances is within the new range.
|
|
17425
|
+
* * If the total number of instances in the scaling group is less than the allowed minimum number after you change the value of the MinSize parameter, Auto Scaling automatically adds instances to the scaling group to ensure that the number of instances is within the new range.
|
|
17426
|
+
* * If the total number of instances in the scaling group does not match the expected number of instances after you change the value of the DesiredCapacity parameter, Auto Scaling automatically adds instances to or removes instances from the scaling group to ensure that the number of instances matches the value of the DesiredCapacity parameter.
|
|
17427
|
+
*
|
|
17428
|
+
* @param request ModifyScalingGroupRequest
|
|
17429
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
17430
|
+
* @return ModifyScalingGroupResponse
|
|
16496
17431
|
*/
|
|
16497
17432
|
async modifyScalingGroupWithOptions(request, runtime) {
|
|
16498
17433
|
tea_util_1.default.validateModel(request);
|
|
@@ -16610,25 +17545,34 @@ class Client extends openapi_client_1.default {
|
|
|
16610
17545
|
return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingGroupResponse({}));
|
|
16611
17546
|
}
|
|
16612
17547
|
/**
|
|
16613
|
-
|
|
16614
|
-
|
|
16615
|
-
|
|
16616
|
-
|
|
16617
|
-
|
|
16618
|
-
|
|
16619
|
-
|
|
16620
|
-
|
|
16621
|
-
|
|
16622
|
-
|
|
16623
|
-
|
|
16624
|
-
|
|
16625
|
-
|
|
16626
|
-
|
|
17548
|
+
* @summary Modifies a scaling group.
|
|
17549
|
+
*
|
|
17550
|
+
* @description * You cannot call this operation to modify the settings of the following parameters:
|
|
17551
|
+
* * RegionId
|
|
17552
|
+
* * LoadBalancerId
|
|
17553
|
+
* > If you want to change the CLB instances that are associated with your scaling group, call the AttachLoadBalancers and DetachLoadBalancers operations.
|
|
17554
|
+
* * DBInstanceId
|
|
17555
|
+
* > If you want to change the ApsaraDB RDS instances that are associated with your scaling group, call the AttachDBInstances and DetachDBInstances operations.
|
|
17556
|
+
* * You can modify only scaling groups that are in the Active or Inactive state.
|
|
17557
|
+
* * If you enable a new scaling configuration, Elastic Compute Service (ECS) instances that are created based on the previous scaling configuration still run as expected in the scaling group.
|
|
17558
|
+
* * If the total number of instances in the scaling group is greater than the allowed maximum number after you change the value of the MaxSize parameter, Auto Scaling automatically removes instances from the scaling group to ensure that the number of instances is within the new range.
|
|
17559
|
+
* * If the total number of instances in the scaling group is less than the allowed minimum number after you change the value of the MinSize parameter, Auto Scaling automatically adds instances to the scaling group to ensure that the number of instances is within the new range.
|
|
17560
|
+
* * If the total number of instances in the scaling group does not match the expected number of instances after you change the value of the DesiredCapacity parameter, Auto Scaling automatically adds instances to or removes instances from the scaling group to ensure that the number of instances matches the value of the DesiredCapacity parameter.
|
|
17561
|
+
*
|
|
17562
|
+
* @param request ModifyScalingGroupRequest
|
|
17563
|
+
* @return ModifyScalingGroupResponse
|
|
16627
17564
|
*/
|
|
16628
17565
|
async modifyScalingGroup(request) {
|
|
16629
17566
|
let runtime = new $Util.RuntimeOptions({});
|
|
16630
17567
|
return await this.modifyScalingGroupWithOptions(request, runtime);
|
|
16631
17568
|
}
|
|
17569
|
+
/**
|
|
17570
|
+
* @summary Modifies a scaling rule.
|
|
17571
|
+
*
|
|
17572
|
+
* @param request ModifyScalingRuleRequest
|
|
17573
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
17574
|
+
* @return ModifyScalingRuleResponse
|
|
17575
|
+
*/
|
|
16632
17576
|
async modifyScalingRuleWithOptions(request, runtime) {
|
|
16633
17577
|
tea_util_1.default.validateModel(request);
|
|
16634
17578
|
let query = {};
|
|
@@ -16717,19 +17661,27 @@ class Client extends openapi_client_1.default {
|
|
|
16717
17661
|
});
|
|
16718
17662
|
return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingRuleResponse({}));
|
|
16719
17663
|
}
|
|
17664
|
+
/**
|
|
17665
|
+
* @summary Modifies a scaling rule.
|
|
17666
|
+
*
|
|
17667
|
+
* @param request ModifyScalingRuleRequest
|
|
17668
|
+
* @return ModifyScalingRuleResponse
|
|
17669
|
+
*/
|
|
16720
17670
|
async modifyScalingRule(request) {
|
|
16721
17671
|
let runtime = new $Util.RuntimeOptions({});
|
|
16722
17672
|
return await this.modifyScalingRuleWithOptions(request, runtime);
|
|
16723
17673
|
}
|
|
16724
17674
|
/**
|
|
16725
|
-
|
|
16726
|
-
|
|
16727
|
-
|
|
16728
|
-
|
|
16729
|
-
|
|
16730
|
-
|
|
16731
|
-
|
|
16732
|
-
|
|
17675
|
+
* @summary Modifies a scheduled task.
|
|
17676
|
+
*
|
|
17677
|
+
* @description You can use the following parameters to specify the scaling method of a scheduled task:
|
|
17678
|
+
* * If you use the `ScheduledAction` parameter, you must select an existing scaling rule for the scheduled task.
|
|
17679
|
+
* * If you use the `ScalingGroupId` parameter, you must specify the minimum number, maximum number, or expected number of instances in the scheduled task.
|
|
17680
|
+
* > You cannot specify the `ScheduledAction` and `ScalingGroupId` parameters at the same time.
|
|
17681
|
+
*
|
|
17682
|
+
* @param request ModifyScheduledTaskRequest
|
|
17683
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
17684
|
+
* @return ModifyScheduledTaskResponse
|
|
16733
17685
|
*/
|
|
16734
17686
|
async modifyScheduledTaskWithOptions(request, runtime) {
|
|
16735
17687
|
tea_util_1.default.validateModel(request);
|
|
@@ -16805,18 +17757,35 @@ class Client extends openapi_client_1.default {
|
|
|
16805
17757
|
return $tea.cast(await this.callApi(params, req, runtime), new ModifyScheduledTaskResponse({}));
|
|
16806
17758
|
}
|
|
16807
17759
|
/**
|
|
16808
|
-
|
|
16809
|
-
|
|
16810
|
-
|
|
16811
|
-
|
|
16812
|
-
|
|
16813
|
-
|
|
16814
|
-
|
|
17760
|
+
* @summary Modifies a scheduled task.
|
|
17761
|
+
*
|
|
17762
|
+
* @description You can use the following parameters to specify the scaling method of a scheduled task:
|
|
17763
|
+
* * If you use the `ScheduledAction` parameter, you must select an existing scaling rule for the scheduled task.
|
|
17764
|
+
* * If you use the `ScalingGroupId` parameter, you must specify the minimum number, maximum number, or expected number of instances in the scheduled task.
|
|
17765
|
+
* > You cannot specify the `ScheduledAction` and `ScalingGroupId` parameters at the same time.
|
|
17766
|
+
*
|
|
17767
|
+
* @param request ModifyScheduledTaskRequest
|
|
17768
|
+
* @return ModifyScheduledTaskResponse
|
|
16815
17769
|
*/
|
|
16816
17770
|
async modifyScheduledTask(request) {
|
|
16817
17771
|
let runtime = new $Util.RuntimeOptions({});
|
|
16818
17772
|
return await this.modifyScheduledTaskWithOptions(request, runtime);
|
|
16819
17773
|
}
|
|
17774
|
+
/**
|
|
17775
|
+
* @summary Rebalances the distribution of Elastic Compute Service (ECS) instances across zones. If ECS instances are unevenly distributed across multiple zones, you can call the RebalanceInstances operation to rebalance the distribution of the ECS instances across the zones.
|
|
17776
|
+
*
|
|
17777
|
+
* @description ## [](#)Usage notes
|
|
17778
|
+
* Auto Scaling creates new ECS instances to replace the existing ECS instances to fulfill the rebalancing purpose. Auto Scaling starts the new ECS instances before stopping the existing ECS instances. The rebalancing operation does not affect the performance or service availability of your application.
|
|
17779
|
+
* * This operation is supported by only multi-zone scaling groups whose `MultiAZPolicy` is set to `BALANCE`.
|
|
17780
|
+
* * A rebalancing operation is required only when the distribution of the instances of a multi-zone scaling group is significantly unbalanced. In a rebalancing activity, Auto Scaling replaces up to 20 ECS instances to rectify the unbalanced distribution.
|
|
17781
|
+
* * During the execution of a rebalancing operation, if the number of instances in the scaling group approaches or hits the value of MaxSize but the rebalancing operation needs to continue, Auto Scaling allows the total number of ECS instances to momentarily exceed the value of MaxSize by 10%. This temporary surplus condition persists for a duration until equilibrium in the distribution of ECS instances is achieved. Typically, it takes 1 to 6 minutes.
|
|
17782
|
+
* **
|
|
17783
|
+
* **Note** If the 10% increment of the maximum number of instances in a scaling group yield a non-integer value, the decimal portion is always rounded up to ensure an additional instance is accounted for. For example, you have a scaling group that holds a maximum of 15 ECS instances. During a rebalancing operation, Auto Scaling would permit the total number of instances to momentarily surpass this limit by 2, instead of the calculated 10% (which is 1.5).
|
|
17784
|
+
*
|
|
17785
|
+
* @param request RebalanceInstancesRequest
|
|
17786
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
17787
|
+
* @return RebalanceInstancesResponse
|
|
17788
|
+
*/
|
|
16820
17789
|
async rebalanceInstancesWithOptions(request, runtime) {
|
|
16821
17790
|
tea_util_1.default.validateModel(request);
|
|
16822
17791
|
let query = {};
|
|
@@ -16854,16 +17823,32 @@ class Client extends openapi_client_1.default {
|
|
|
16854
17823
|
});
|
|
16855
17824
|
return $tea.cast(await this.callApi(params, req, runtime), new RebalanceInstancesResponse({}));
|
|
16856
17825
|
}
|
|
17826
|
+
/**
|
|
17827
|
+
* @summary Rebalances the distribution of Elastic Compute Service (ECS) instances across zones. If ECS instances are unevenly distributed across multiple zones, you can call the RebalanceInstances operation to rebalance the distribution of the ECS instances across the zones.
|
|
17828
|
+
*
|
|
17829
|
+
* @description ## [](#)Usage notes
|
|
17830
|
+
* Auto Scaling creates new ECS instances to replace the existing ECS instances to fulfill the rebalancing purpose. Auto Scaling starts the new ECS instances before stopping the existing ECS instances. The rebalancing operation does not affect the performance or service availability of your application.
|
|
17831
|
+
* * This operation is supported by only multi-zone scaling groups whose `MultiAZPolicy` is set to `BALANCE`.
|
|
17832
|
+
* * A rebalancing operation is required only when the distribution of the instances of a multi-zone scaling group is significantly unbalanced. In a rebalancing activity, Auto Scaling replaces up to 20 ECS instances to rectify the unbalanced distribution.
|
|
17833
|
+
* * During the execution of a rebalancing operation, if the number of instances in the scaling group approaches or hits the value of MaxSize but the rebalancing operation needs to continue, Auto Scaling allows the total number of ECS instances to momentarily exceed the value of MaxSize by 10%. This temporary surplus condition persists for a duration until equilibrium in the distribution of ECS instances is achieved. Typically, it takes 1 to 6 minutes.
|
|
17834
|
+
* **
|
|
17835
|
+
* **Note** If the 10% increment of the maximum number of instances in a scaling group yield a non-integer value, the decimal portion is always rounded up to ensure an additional instance is accounted for. For example, you have a scaling group that holds a maximum of 15 ECS instances. During a rebalancing operation, Auto Scaling would permit the total number of instances to momentarily surpass this limit by 2, instead of the calculated 10% (which is 1.5).
|
|
17836
|
+
*
|
|
17837
|
+
* @param request RebalanceInstancesRequest
|
|
17838
|
+
* @return RebalanceInstancesResponse
|
|
17839
|
+
*/
|
|
16857
17840
|
async rebalanceInstances(request) {
|
|
16858
17841
|
let runtime = new $Util.RuntimeOptions({});
|
|
16859
17842
|
return await this.rebalanceInstancesWithOptions(request, runtime);
|
|
16860
17843
|
}
|
|
16861
17844
|
/**
|
|
16862
|
-
|
|
16863
|
-
|
|
16864
|
-
|
|
16865
|
-
|
|
16866
|
-
|
|
17845
|
+
* @summary Prolongs a lifecycle hook for Elastic Compute Service (ECS) instances.
|
|
17846
|
+
*
|
|
17847
|
+
* @description You can call this operation to prolong the length of a lifecycle hook up to 20 times. Take note that the total length of a lifecycle hook cannot exceed 6 hours.
|
|
17848
|
+
*
|
|
17849
|
+
* @param request RecordLifecycleActionHeartbeatRequest
|
|
17850
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
17851
|
+
* @return RecordLifecycleActionHeartbeatResponse
|
|
16867
17852
|
*/
|
|
16868
17853
|
async recordLifecycleActionHeartbeatWithOptions(request, runtime) {
|
|
16869
17854
|
tea_util_1.default.validateModel(request);
|
|
@@ -16906,28 +17891,32 @@ class Client extends openapi_client_1.default {
|
|
|
16906
17891
|
return $tea.cast(await this.callApi(params, req, runtime), new RecordLifecycleActionHeartbeatResponse({}));
|
|
16907
17892
|
}
|
|
16908
17893
|
/**
|
|
16909
|
-
|
|
16910
|
-
|
|
16911
|
-
|
|
16912
|
-
|
|
17894
|
+
* @summary Prolongs a lifecycle hook for Elastic Compute Service (ECS) instances.
|
|
17895
|
+
*
|
|
17896
|
+
* @description You can call this operation to prolong the length of a lifecycle hook up to 20 times. Take note that the total length of a lifecycle hook cannot exceed 6 hours.
|
|
17897
|
+
*
|
|
17898
|
+
* @param request RecordLifecycleActionHeartbeatRequest
|
|
17899
|
+
* @return RecordLifecycleActionHeartbeatResponse
|
|
16913
17900
|
*/
|
|
16914
17901
|
async recordLifecycleActionHeartbeat(request) {
|
|
16915
17902
|
let runtime = new $Util.RuntimeOptions({});
|
|
16916
17903
|
return await this.recordLifecycleActionHeartbeatWithOptions(request, runtime);
|
|
16917
17904
|
}
|
|
16918
17905
|
/**
|
|
16919
|
-
|
|
16920
|
-
|
|
16921
|
-
|
|
16922
|
-
|
|
16923
|
-
|
|
16924
|
-
|
|
16925
|
-
|
|
16926
|
-
|
|
16927
|
-
|
|
16928
|
-
|
|
16929
|
-
|
|
16930
|
-
|
|
17906
|
+
* @summary Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
|
|
17907
|
+
*
|
|
17908
|
+
* @description * Before you call this operation, make sure that the following requirements are met:
|
|
17909
|
+
* * The scaling group is in the Active state.
|
|
17910
|
+
* * No scaling activity is in progress within the scaling group.
|
|
17911
|
+
* > If no scaling activity is in progress within the scaling group, you can call the operation even within the cooldown period.
|
|
17912
|
+
* * If an ECS instance is automatically created by Auto Scaling, or if an ECS instance is manually added to a scaling group and managed by the scaling group, the ECS instance is stopped in economical mode or is released after the instance is removed from the scaling group.
|
|
17913
|
+
* * If an ECS instance is manually added to a scaling group and is not managed by the scaling group, the ECS instance is not stopped or released after the instance is removed from the scaling group.
|
|
17914
|
+
* * If the difference between the number of existing ECS instances specified by the TotalCapacity parameter and the number of ECS instances that you call this operation to remove is less than the value of the MinSize parameter, the call fails.
|
|
17915
|
+
* A successful call only means that Auto Scaling accepts the request. The scaling activity may still fail. You can obtain the status of a scaling activity based on the value of the ScalingActivityId parameter in the response.
|
|
17916
|
+
*
|
|
17917
|
+
* @param request RemoveInstancesRequest
|
|
17918
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
17919
|
+
* @return RemoveInstancesResponse
|
|
16931
17920
|
*/
|
|
16932
17921
|
async removeInstancesWithOptions(request, runtime) {
|
|
16933
17922
|
tea_util_1.default.validateModel(request);
|
|
@@ -16938,6 +17927,9 @@ class Client extends openapi_client_1.default {
|
|
|
16938
17927
|
if (!tea_util_1.default.isUnset(request.decreaseDesiredCapacity)) {
|
|
16939
17928
|
query["DecreaseDesiredCapacity"] = request.decreaseDesiredCapacity;
|
|
16940
17929
|
}
|
|
17930
|
+
if (!tea_util_1.default.isUnset(request.ignoreInvalidInstance)) {
|
|
17931
|
+
query["IgnoreInvalidInstance"] = request.ignoreInvalidInstance;
|
|
17932
|
+
}
|
|
16941
17933
|
if (!tea_util_1.default.isUnset(request.instanceIds)) {
|
|
16942
17934
|
query["InstanceIds"] = request.instanceIds;
|
|
16943
17935
|
}
|
|
@@ -16979,22 +17971,31 @@ class Client extends openapi_client_1.default {
|
|
|
16979
17971
|
return $tea.cast(await this.callApi(params, req, runtime), new RemoveInstancesResponse({}));
|
|
16980
17972
|
}
|
|
16981
17973
|
/**
|
|
16982
|
-
|
|
16983
|
-
|
|
16984
|
-
|
|
16985
|
-
|
|
16986
|
-
|
|
16987
|
-
|
|
16988
|
-
|
|
16989
|
-
|
|
16990
|
-
|
|
16991
|
-
|
|
16992
|
-
|
|
17974
|
+
* @summary Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
|
|
17975
|
+
*
|
|
17976
|
+
* @description * Before you call this operation, make sure that the following requirements are met:
|
|
17977
|
+
* * The scaling group is in the Active state.
|
|
17978
|
+
* * No scaling activity is in progress within the scaling group.
|
|
17979
|
+
* > If no scaling activity is in progress within the scaling group, you can call the operation even within the cooldown period.
|
|
17980
|
+
* * If an ECS instance is automatically created by Auto Scaling, or if an ECS instance is manually added to a scaling group and managed by the scaling group, the ECS instance is stopped in economical mode or is released after the instance is removed from the scaling group.
|
|
17981
|
+
* * If an ECS instance is manually added to a scaling group and is not managed by the scaling group, the ECS instance is not stopped or released after the instance is removed from the scaling group.
|
|
17982
|
+
* * If the difference between the number of existing ECS instances specified by the TotalCapacity parameter and the number of ECS instances that you call this operation to remove is less than the value of the MinSize parameter, the call fails.
|
|
17983
|
+
* A successful call only means that Auto Scaling accepts the request. The scaling activity may still fail. You can obtain the status of a scaling activity based on the value of the ScalingActivityId parameter in the response.
|
|
17984
|
+
*
|
|
17985
|
+
* @param request RemoveInstancesRequest
|
|
17986
|
+
* @return RemoveInstancesResponse
|
|
16993
17987
|
*/
|
|
16994
17988
|
async removeInstances(request) {
|
|
16995
17989
|
let runtime = new $Util.RuntimeOptions({});
|
|
16996
17990
|
return await this.removeInstancesWithOptions(request, runtime);
|
|
16997
17991
|
}
|
|
17992
|
+
/**
|
|
17993
|
+
* @summary Resumes suspended processes in a scaling group.
|
|
17994
|
+
*
|
|
17995
|
+
* @param request ResumeProcessesRequest
|
|
17996
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
17997
|
+
* @return ResumeProcessesResponse
|
|
17998
|
+
*/
|
|
16998
17999
|
async resumeProcessesWithOptions(request, runtime) {
|
|
16999
18000
|
tea_util_1.default.validateModel(request);
|
|
17000
18001
|
let query = {};
|
|
@@ -17032,23 +18033,31 @@ class Client extends openapi_client_1.default {
|
|
|
17032
18033
|
});
|
|
17033
18034
|
return $tea.cast(await this.callApi(params, req, runtime), new ResumeProcessesResponse({}));
|
|
17034
18035
|
}
|
|
18036
|
+
/**
|
|
18037
|
+
* @summary Resumes suspended processes in a scaling group.
|
|
18038
|
+
*
|
|
18039
|
+
* @param request ResumeProcessesRequest
|
|
18040
|
+
* @return ResumeProcessesResponse
|
|
18041
|
+
*/
|
|
17035
18042
|
async resumeProcesses(request) {
|
|
17036
18043
|
let runtime = new $Util.RuntimeOptions({});
|
|
17037
18044
|
return await this.resumeProcessesWithOptions(request, runtime);
|
|
17038
18045
|
}
|
|
17039
18046
|
/**
|
|
17040
|
-
|
|
17041
|
-
|
|
17042
|
-
|
|
17043
|
-
|
|
17044
|
-
|
|
17045
|
-
|
|
17046
|
-
|
|
17047
|
-
|
|
17048
|
-
|
|
17049
|
-
|
|
17050
|
-
|
|
17051
|
-
|
|
18047
|
+
* @summary Scales instances in a scaling group based on the specified scaling policy.
|
|
18048
|
+
*
|
|
18049
|
+
* @description Compared with the ExecuteScalingRule operation, the ScaleWithAdjustment operation does not require a scaling rule to be created in advance. Before you call the ScaleWithAdjustment operation, take note of the following items:
|
|
18050
|
+
* * The following conditions must be met:
|
|
18051
|
+
* * The scaling group is in the Active state.
|
|
18052
|
+
* * No scaling activities in the scaling group are in progress.
|
|
18053
|
+
* * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
|
|
18054
|
+
* * If the addition of a specified number of Elastic Compute Service (ECS) instances to a scaling group causes the total number of ECS instances in the scaling group to exceed the maximum number of instances allowed, Auto Scaling adds only a specific number of ECS instances to ensure that the total number of instances is equal to the maximum number of instances.
|
|
18055
|
+
* * If the removal of a specified number of ECS instances from a scaling group causes the total number of ECS instances in the scaling group to drop below the minimum number of instances allowed, Auto Scaling removes only a specific number of ECS instances to ensure that the total number of instances is equal to the minimum number of instances.
|
|
18056
|
+
* A successful call indicates that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity by using the value of the `ScalingActivityId` parameter in the response.
|
|
18057
|
+
*
|
|
18058
|
+
* @param tmpReq ScaleWithAdjustmentRequest
|
|
18059
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
18060
|
+
* @return ScaleWithAdjustmentResponse
|
|
17052
18061
|
*/
|
|
17053
18062
|
async scaleWithAdjustmentWithOptions(tmpReq, runtime) {
|
|
17054
18063
|
tea_util_1.default.validateModel(tmpReq);
|
|
@@ -17111,22 +18120,31 @@ class Client extends openapi_client_1.default {
|
|
|
17111
18120
|
return $tea.cast(await this.callApi(params, req, runtime), new ScaleWithAdjustmentResponse({}));
|
|
17112
18121
|
}
|
|
17113
18122
|
/**
|
|
17114
|
-
|
|
17115
|
-
|
|
17116
|
-
|
|
17117
|
-
|
|
17118
|
-
|
|
17119
|
-
|
|
17120
|
-
|
|
17121
|
-
|
|
17122
|
-
|
|
17123
|
-
|
|
17124
|
-
|
|
18123
|
+
* @summary Scales instances in a scaling group based on the specified scaling policy.
|
|
18124
|
+
*
|
|
18125
|
+
* @description Compared with the ExecuteScalingRule operation, the ScaleWithAdjustment operation does not require a scaling rule to be created in advance. Before you call the ScaleWithAdjustment operation, take note of the following items:
|
|
18126
|
+
* * The following conditions must be met:
|
|
18127
|
+
* * The scaling group is in the Active state.
|
|
18128
|
+
* * No scaling activities in the scaling group are in progress.
|
|
18129
|
+
* * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
|
|
18130
|
+
* * If the addition of a specified number of Elastic Compute Service (ECS) instances to a scaling group causes the total number of ECS instances in the scaling group to exceed the maximum number of instances allowed, Auto Scaling adds only a specific number of ECS instances to ensure that the total number of instances is equal to the maximum number of instances.
|
|
18131
|
+
* * If the removal of a specified number of ECS instances from a scaling group causes the total number of ECS instances in the scaling group to drop below the minimum number of instances allowed, Auto Scaling removes only a specific number of ECS instances to ensure that the total number of instances is equal to the minimum number of instances.
|
|
18132
|
+
* A successful call indicates that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity by using the value of the `ScalingActivityId` parameter in the response.
|
|
18133
|
+
*
|
|
18134
|
+
* @param request ScaleWithAdjustmentRequest
|
|
18135
|
+
* @return ScaleWithAdjustmentResponse
|
|
17125
18136
|
*/
|
|
17126
18137
|
async scaleWithAdjustment(request) {
|
|
17127
18138
|
let runtime = new $Util.RuntimeOptions({});
|
|
17128
18139
|
return await this.scaleWithAdjustmentWithOptions(request, runtime);
|
|
17129
18140
|
}
|
|
18141
|
+
/**
|
|
18142
|
+
* @summary Sets deletion protection for a scaling group. If you enable deletion protection for a scaling group, you cannot delete the scaling group. If you disable deletion protection for a scaling group, you can directly delete the scaling group. You can call the SetGroupDeletionProtection operation to enable or disable deletion protection.
|
|
18143
|
+
*
|
|
18144
|
+
* @param request SetGroupDeletionProtectionRequest
|
|
18145
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
18146
|
+
* @return SetGroupDeletionProtectionResponse
|
|
18147
|
+
*/
|
|
17130
18148
|
async setGroupDeletionProtectionWithOptions(request, runtime) {
|
|
17131
18149
|
tea_util_1.default.validateModel(request);
|
|
17132
18150
|
let query = {};
|
|
@@ -17161,16 +18179,24 @@ class Client extends openapi_client_1.default {
|
|
|
17161
18179
|
});
|
|
17162
18180
|
return $tea.cast(await this.callApi(params, req, runtime), new SetGroupDeletionProtectionResponse({}));
|
|
17163
18181
|
}
|
|
18182
|
+
/**
|
|
18183
|
+
* @summary Sets deletion protection for a scaling group. If you enable deletion protection for a scaling group, you cannot delete the scaling group. If you disable deletion protection for a scaling group, you can directly delete the scaling group. You can call the SetGroupDeletionProtection operation to enable or disable deletion protection.
|
|
18184
|
+
*
|
|
18185
|
+
* @param request SetGroupDeletionProtectionRequest
|
|
18186
|
+
* @return SetGroupDeletionProtectionResponse
|
|
18187
|
+
*/
|
|
17164
18188
|
async setGroupDeletionProtection(request) {
|
|
17165
18189
|
let runtime = new $Util.RuntimeOptions({});
|
|
17166
18190
|
return await this.setGroupDeletionProtectionWithOptions(request, runtime);
|
|
17167
18191
|
}
|
|
17168
18192
|
/**
|
|
17169
|
-
|
|
17170
|
-
|
|
17171
|
-
|
|
17172
|
-
|
|
17173
|
-
|
|
18193
|
+
* @summary Sets instance health. At times, the automatic health check system might not sufficiently determine the precise health status of your Elastic Compute Service (ECS) instances or elastic container instances. To overcome this, you can call the SetInstanceHealth operation to swiftly pinpoint problematic instances and resolve issues. This operation is designed to more precisely align with real-world business requirements and tackle O\\&M hurdles efficiently.
|
|
18194
|
+
*
|
|
18195
|
+
* @description Auto Scaling detects and removes unhealthy ECS instances or elastic container instances from the corresponding scaling groups. If you want to retain a specific instance in the corresponding scaling group, you can put the instance into the Standby or Protected state. For more information, see [EnterStandby](~~EnterStandby~~) and [SetInstancesProtection](~~SetInstancesProtection~~).
|
|
18196
|
+
*
|
|
18197
|
+
* @param request SetInstanceHealthRequest
|
|
18198
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
18199
|
+
* @return SetInstanceHealthResponse
|
|
17174
18200
|
*/
|
|
17175
18201
|
async setInstanceHealthWithOptions(request, runtime) {
|
|
17176
18202
|
tea_util_1.default.validateModel(request);
|
|
@@ -17204,21 +18230,28 @@ class Client extends openapi_client_1.default {
|
|
|
17204
18230
|
return $tea.cast(await this.callApi(params, req, runtime), new SetInstanceHealthResponse({}));
|
|
17205
18231
|
}
|
|
17206
18232
|
/**
|
|
17207
|
-
|
|
17208
|
-
|
|
17209
|
-
|
|
17210
|
-
|
|
18233
|
+
* @summary Sets instance health. At times, the automatic health check system might not sufficiently determine the precise health status of your Elastic Compute Service (ECS) instances or elastic container instances. To overcome this, you can call the SetInstanceHealth operation to swiftly pinpoint problematic instances and resolve issues. This operation is designed to more precisely align with real-world business requirements and tackle O\\&M hurdles efficiently.
|
|
18234
|
+
*
|
|
18235
|
+
* @description Auto Scaling detects and removes unhealthy ECS instances or elastic container instances from the corresponding scaling groups. If you want to retain a specific instance in the corresponding scaling group, you can put the instance into the Standby or Protected state. For more information, see [EnterStandby](~~EnterStandby~~) and [SetInstancesProtection](~~SetInstancesProtection~~).
|
|
18236
|
+
*
|
|
18237
|
+
* @param request SetInstanceHealthRequest
|
|
18238
|
+
* @return SetInstanceHealthResponse
|
|
17211
18239
|
*/
|
|
17212
18240
|
async setInstanceHealth(request) {
|
|
17213
18241
|
let runtime = new $Util.RuntimeOptions({});
|
|
17214
18242
|
return await this.setInstanceHealthWithOptions(request, runtime);
|
|
17215
18243
|
}
|
|
17216
18244
|
/**
|
|
17217
|
-
|
|
17218
|
-
|
|
17219
|
-
|
|
17220
|
-
|
|
17221
|
-
|
|
18245
|
+
* @summary Puts Elastic Compute Service (ECS) instances into the Protected state. When ECS instances are put into the Protected state, they become immune to manual deletion attempts by using the Auto Scaling console or API operations. This operation serves as a robust safeguard, efficiently preventing any inadvertent instance release that could lead to irreversible consequences.
|
|
18246
|
+
*
|
|
18247
|
+
* @description Once ECS instances enter the Protected state, they become subject to the following restrictions:
|
|
18248
|
+
* * ECS instances will persist in the Protected state, unless you deliberately remove them from this state.
|
|
18249
|
+
* * Even in scenarios where automatic scale-in actions are initiated due to fluctuations in the number of ECS instances or the execution of event-triggered tasks, Auto Scaling does not remove ECS instances that are in the Protected state from their respective scaling groups. Only after being manually removed from their respective scaling groups can ECS instances that are in the Protected state be released. For more information, see [Remove an ECS instance](https://help.aliyun.com/document_detail/25955.html).
|
|
18250
|
+
* * ECS instances in the Protected state maintain their existing health status even when they undergo stopping or restarting processes.
|
|
18251
|
+
*
|
|
18252
|
+
* @param request SetInstancesProtectionRequest
|
|
18253
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
18254
|
+
* @return SetInstancesProtectionResponse
|
|
17222
18255
|
*/
|
|
17223
18256
|
async setInstancesProtectionWithOptions(request, runtime) {
|
|
17224
18257
|
tea_util_1.default.validateModel(request);
|
|
@@ -17255,15 +18288,27 @@ class Client extends openapi_client_1.default {
|
|
|
17255
18288
|
return $tea.cast(await this.callApi(params, req, runtime), new SetInstancesProtectionResponse({}));
|
|
17256
18289
|
}
|
|
17257
18290
|
/**
|
|
17258
|
-
|
|
17259
|
-
|
|
17260
|
-
|
|
17261
|
-
|
|
18291
|
+
* @summary Puts Elastic Compute Service (ECS) instances into the Protected state. When ECS instances are put into the Protected state, they become immune to manual deletion attempts by using the Auto Scaling console or API operations. This operation serves as a robust safeguard, efficiently preventing any inadvertent instance release that could lead to irreversible consequences.
|
|
18292
|
+
*
|
|
18293
|
+
* @description Once ECS instances enter the Protected state, they become subject to the following restrictions:
|
|
18294
|
+
* * ECS instances will persist in the Protected state, unless you deliberately remove them from this state.
|
|
18295
|
+
* * Even in scenarios where automatic scale-in actions are initiated due to fluctuations in the number of ECS instances or the execution of event-triggered tasks, Auto Scaling does not remove ECS instances that are in the Protected state from their respective scaling groups. Only after being manually removed from their respective scaling groups can ECS instances that are in the Protected state be released. For more information, see [Remove an ECS instance](https://help.aliyun.com/document_detail/25955.html).
|
|
18296
|
+
* * ECS instances in the Protected state maintain their existing health status even when they undergo stopping or restarting processes.
|
|
18297
|
+
*
|
|
18298
|
+
* @param request SetInstancesProtectionRequest
|
|
18299
|
+
* @return SetInstancesProtectionResponse
|
|
17262
18300
|
*/
|
|
17263
18301
|
async setInstancesProtection(request) {
|
|
17264
18302
|
let runtime = new $Util.RuntimeOptions({});
|
|
17265
18303
|
return await this.setInstancesProtectionWithOptions(request, runtime);
|
|
17266
18304
|
}
|
|
18305
|
+
/**
|
|
18306
|
+
* @summary Suspends scaling processes. This operation empowers you to selectively pause distinct scaling processes within a particular scaling group, enabling you to carry out alternative tasks and achieve more granular management over your scaling operations.
|
|
18307
|
+
*
|
|
18308
|
+
* @param request SuspendProcessesRequest
|
|
18309
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
18310
|
+
* @return SuspendProcessesResponse
|
|
18311
|
+
*/
|
|
17267
18312
|
async suspendProcessesWithOptions(request, runtime) {
|
|
17268
18313
|
tea_util_1.default.validateModel(request);
|
|
17269
18314
|
let query = {};
|
|
@@ -17301,10 +18346,23 @@ class Client extends openapi_client_1.default {
|
|
|
17301
18346
|
});
|
|
17302
18347
|
return $tea.cast(await this.callApi(params, req, runtime), new SuspendProcessesResponse({}));
|
|
17303
18348
|
}
|
|
18349
|
+
/**
|
|
18350
|
+
* @summary Suspends scaling processes. This operation empowers you to selectively pause distinct scaling processes within a particular scaling group, enabling you to carry out alternative tasks and achieve more granular management over your scaling operations.
|
|
18351
|
+
*
|
|
18352
|
+
* @param request SuspendProcessesRequest
|
|
18353
|
+
* @return SuspendProcessesResponse
|
|
18354
|
+
*/
|
|
17304
18355
|
async suspendProcesses(request) {
|
|
17305
18356
|
let runtime = new $Util.RuntimeOptions({});
|
|
17306
18357
|
return await this.suspendProcessesWithOptions(request, runtime);
|
|
17307
18358
|
}
|
|
18359
|
+
/**
|
|
18360
|
+
* @summary Adds tags to specified Auto Scaling resources.
|
|
18361
|
+
*
|
|
18362
|
+
* @param request TagResourcesRequest
|
|
18363
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
18364
|
+
* @return TagResourcesResponse
|
|
18365
|
+
*/
|
|
17308
18366
|
async tagResourcesWithOptions(request, runtime) {
|
|
17309
18367
|
tea_util_1.default.validateModel(request);
|
|
17310
18368
|
let query = {};
|
|
@@ -17342,10 +18400,23 @@ class Client extends openapi_client_1.default {
|
|
|
17342
18400
|
});
|
|
17343
18401
|
return $tea.cast(await this.callApi(params, req, runtime), new TagResourcesResponse({}));
|
|
17344
18402
|
}
|
|
18403
|
+
/**
|
|
18404
|
+
* @summary Adds tags to specified Auto Scaling resources.
|
|
18405
|
+
*
|
|
18406
|
+
* @param request TagResourcesRequest
|
|
18407
|
+
* @return TagResourcesResponse
|
|
18408
|
+
*/
|
|
17345
18409
|
async tagResources(request) {
|
|
17346
18410
|
let runtime = new $Util.RuntimeOptions({});
|
|
17347
18411
|
return await this.tagResourcesWithOptions(request, runtime);
|
|
17348
18412
|
}
|
|
18413
|
+
/**
|
|
18414
|
+
* @summary Removes tags from Auto Scaling resources simultaneously. This operation streamlines resource management activities, enhances system efficiency, and mitigates potential security vulnerabilities. Once a tag is removed from a particular resource, and if it is not re-added to any other resource, the system will automatically delete the unused tag.
|
|
18415
|
+
*
|
|
18416
|
+
* @param request UntagResourcesRequest
|
|
18417
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
18418
|
+
* @return UntagResourcesResponse
|
|
18419
|
+
*/
|
|
17349
18420
|
async untagResourcesWithOptions(request, runtime) {
|
|
17350
18421
|
tea_util_1.default.validateModel(request);
|
|
17351
18422
|
let query = {};
|
|
@@ -17386,10 +18457,23 @@ class Client extends openapi_client_1.default {
|
|
|
17386
18457
|
});
|
|
17387
18458
|
return $tea.cast(await this.callApi(params, req, runtime), new UntagResourcesResponse({}));
|
|
17388
18459
|
}
|
|
18460
|
+
/**
|
|
18461
|
+
* @summary Removes tags from Auto Scaling resources simultaneously. This operation streamlines resource management activities, enhances system efficiency, and mitigates potential security vulnerabilities. Once a tag is removed from a particular resource, and if it is not re-added to any other resource, the system will automatically delete the unused tag.
|
|
18462
|
+
*
|
|
18463
|
+
* @param request UntagResourcesRequest
|
|
18464
|
+
* @return UntagResourcesResponse
|
|
18465
|
+
*/
|
|
17389
18466
|
async untagResources(request) {
|
|
17390
18467
|
let runtime = new $Util.RuntimeOptions({});
|
|
17391
18468
|
return await this.untagResourcesWithOptions(request, runtime);
|
|
17392
18469
|
}
|
|
18470
|
+
/**
|
|
18471
|
+
* @summary Checks whether Auto Scaling is authorized to access Elastic Compute Service (ECS) and Elastic Container Instance resources.
|
|
18472
|
+
*
|
|
18473
|
+
* @param request VerifyAuthenticationRequest
|
|
18474
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
18475
|
+
* @return VerifyAuthenticationResponse
|
|
18476
|
+
*/
|
|
17393
18477
|
async verifyAuthenticationWithOptions(request, runtime) {
|
|
17394
18478
|
tea_util_1.default.validateModel(request);
|
|
17395
18479
|
let query = {};
|
|
@@ -17424,10 +18508,23 @@ class Client extends openapi_client_1.default {
|
|
|
17424
18508
|
});
|
|
17425
18509
|
return $tea.cast(await this.callApi(params, req, runtime), new VerifyAuthenticationResponse({}));
|
|
17426
18510
|
}
|
|
18511
|
+
/**
|
|
18512
|
+
* @summary Checks whether Auto Scaling is authorized to access Elastic Compute Service (ECS) and Elastic Container Instance resources.
|
|
18513
|
+
*
|
|
18514
|
+
* @param request VerifyAuthenticationRequest
|
|
18515
|
+
* @return VerifyAuthenticationResponse
|
|
18516
|
+
*/
|
|
17427
18517
|
async verifyAuthentication(request) {
|
|
17428
18518
|
let runtime = new $Util.RuntimeOptions({});
|
|
17429
18519
|
return await this.verifyAuthenticationWithOptions(request, runtime);
|
|
17430
18520
|
}
|
|
18521
|
+
/**
|
|
18522
|
+
* @summary Verifies whether Auto Scaling is activated. This operation guarantees that in response to shifts in business workloads or variations in incoming traffic, the system will automatically adjust resource provisioning. This auto-scaling capability enhances the overall system performance, ensuring high availability and improved flexibility to accommodate dynamic demands.
|
|
18523
|
+
*
|
|
18524
|
+
* @param request VerifyUserRequest
|
|
18525
|
+
* @param runtime runtime options for this request RuntimeOptions
|
|
18526
|
+
* @return VerifyUserResponse
|
|
18527
|
+
*/
|
|
17431
18528
|
async verifyUserWithOptions(request, runtime) {
|
|
17432
18529
|
tea_util_1.default.validateModel(request);
|
|
17433
18530
|
let query = {};
|
|
@@ -17459,6 +18556,12 @@ class Client extends openapi_client_1.default {
|
|
|
17459
18556
|
});
|
|
17460
18557
|
return $tea.cast(await this.callApi(params, req, runtime), new VerifyUserResponse({}));
|
|
17461
18558
|
}
|
|
18559
|
+
/**
|
|
18560
|
+
* @summary Verifies whether Auto Scaling is activated. This operation guarantees that in response to shifts in business workloads or variations in incoming traffic, the system will automatically adjust resource provisioning. This auto-scaling capability enhances the overall system performance, ensuring high availability and improved flexibility to accommodate dynamic demands.
|
|
18561
|
+
*
|
|
18562
|
+
* @param request VerifyUserRequest
|
|
18563
|
+
* @return VerifyUserResponse
|
|
18564
|
+
*/
|
|
17462
18565
|
async verifyUser(request) {
|
|
17463
18566
|
let runtime = new $Util.RuntimeOptions({});
|
|
17464
18567
|
return await this.verifyUserWithOptions(request, runtime);
|