Queries elastic compute units (ECUs) available for scaling out an application in a specified cluster or the cluster where the application is deployed. This operation is applicable to Elastic Compute Service (ECS) clusters.
Operation description
Terms
- Namespace: the logical concept that is used to isolate resources such as clusters, ECS instances, and applications, and microservices published in EDAS. This concept involves the default namespace and custom namespaces. Each region has a default namespace and supports multiple custom namespaces. By default, only the default namespace is available. You do not need to create a custom namespace if you do not want to isolate resources and microservices.
- Elastic compute unit (ECU): After an ECS instance is imported to a cluster, the instance becomes an ECU.
- Elastic compute container (ECC): After you deploy an application to an ECU in a cluster, the ECU becomes an ECC.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
edas:ReadCluster | Read |
|
| none |
Request syntax
POST /pop/v5/resource/scale_out_ecu_list
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
LogicalRegionId | string | No | The ID of the namespace.
| cn-beijing:test |
ClusterId | string | No | The ID of the cluster. Specify this parameter if you want to query the available ECUs in the cluster. Note
Specify at least one of the ClusterId and AppId parameters as the query parameter.
| 52984524-6d48-4bbd-****************** |
AppId | string | No | The ID of the application. Specify this parameter if you want to query the available ECUs in the cluster where the application is deployed. Note
Specify at least one of the ClusterId and AppId parameters as the query parameter.
| b93024fd-8a9d-4ef7-99f1-5f0d65cc**** |
GroupId | string | No | The ID of the instance group. Specify this parameter if you want to query the available ECUs in the cluster where the instance group resides. | 8123db90-880f-486f-****-**** |
Cpu | integer | No | The number of CPU cores based on which you want to query the available ECUs in the cluster. | 1 |
Mem | integer | No | The size of available memory based on which you want to query the available ECUs in the cluster. Unit: MB. | 200 |
InstanceNum | integer | No | The number of ECUs that you want to query. If this parameter is not specified, all the ECUs that meet the query conditions are returned. | 1 |
Response parameters
Examples
Sample success responses
JSON
format
{
"Code": 200,
"Message": "success",
"RequestId": "AF860D6C-ACE3-4429-9D54-3BD15A******",
"EcuInfoList": {
"EcuInfo": [
{
"VpcId": "vpc-2zef6ob8**********",
"UpdateTime": 1573281040827,
"IpAddr": "192.168.XX.XX",
"AvailableCpu": 2,
"CreateTime": 1573281040819,
"UserId": "1172****6608****",
"InstanceId": "i-2zej4i2jdf*********",
"RegionId": "cn-beijing",
"EcuId": "0de2ebdb-9490-4fc4-be41***************",
"Online": true,
"DockerEnv": false,
"AvailableMem": 111,
"ZoneId": "cn-beijing-h",
"Name": "test",
"HeartbeatTime": 1573281040819
}
]
}
}
Error codes
For a list of error codes, visit the Service error codes.