Querying Details of a DDM Instance
Function
This API is used to query details about a DDM instance.
Constraints
None
URI
GET /v1/{project_id}/instances/{instance_id}
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| project_id | Yes | String | Project ID of a tenant in a region To obtain this value, see Obtaining a Project ID. |
| instance_id | Yes | String | DDM instance ID |
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| X-Auth-Token | Yes | String | User token. You can obtain the token by calling the IAM API used to obtain a user token. |
Response Parameters
Status code: 200
| Parameter | Type | Description |
|---|---|---|
| id | String | DDM instance ID |
| status | String | DDM instance status. For details about this parameter value, see Status Description. |
| name | String | DDM instance name |
| created | String | Time when the DDM instance is created. The time must be in the format of yyyy-mm-dd Thh:mm:ssZ. |
| updated | String | Time when the DDM instance is last updated |
| available_zone | String | Name of the AZ where the DDM instance is located |
| vpc_id | String | VPC ID |
| subnet_id | String | Subnet ID |
| security_group_id | String | Security group ID |
| node_count | Integer | Number of nodes |
| access_ip | String | Address for accessing the DDM instance |
| access_port | String | Port for accessing the DDM instance |
| node_status | String | Node status |
| core_count | String | Number of vCPUs |
| ram_capacity | String | Memory size in GB |
| error_msg | String | Response message. This parameter is not returned if no abnormality occurs. |
| project_id | String | Project ID |
| order_id | String | Order ID. No value is returned when a pay-per-use instance is created. |
| enterprise_project_id | String | Enterprise project ID |
| engine_version | String | Engine version |
| nodes | Array of GetDetailfNodesInfo objects | Node information |
| admin_user_name | String | Username of the administrator. The username: |
| enable_ssl | Boolean | Whether SSL is enabled. The value can be:
|
| flavor_ref | String | Specification code |
| Parameter | Type | Description |
|---|---|---|
| status | String | Status of the DDM instance node |
| port | String | Port of the DDM instance node |
| ip | String | IP address of the DDM instance node. If load balancing is enabled, the value is the ELB IP address of the group that the node belongs to. |
Status code: 400
| Parameter | Type | Description |
|---|---|---|
| errCode | String | Service error code |
| externalMessage | String | Error message |
Status code: 500
| Parameter | Type | Description |
|---|---|---|
| errCode | String | Service error code |
| externalMessage | String | Error message |
Example Request
Querying details of a DDM instance
GET https://{endpoint}/v1/{project_id}/instances/{instance_id} Example Response
Status code: 200
OK
{
"nodes" : [ {
"status" : "RUNNING",
"port" : 5066,
"ip" : "192.168.0.160"
} ],
"id" : "1f5c9fd6cd984056ba89c8c87cc03278in09",
"status" : "RUNNING",
"name" : "ddm2-test",
"created" : "2021-11-09T03:30:01+0000",
"updated" : "2021-12-15T09:12:58+0000",
"available_zone" : "az1",
"vpc_id" : "cfaa4024-0603-4aba-81d4-2203b4ad26fb",
"subnet_id" : "48f270ef-af70-4ad9-bb1c-c28dd5b37f93",
"security_group_id" : "bc28ef93-0083-4652-bce6-381e14284db6",
"node_count" : 1,
"access_ip" : "192.168.0.160",
"access_port" : "5066",
"core_count" : "2",
"ram_capacity" : "8",
"node_status" : "RUNNING",
"enterprise_project_id" : "0",
"project_id" : "070c071d8e80d58c2f42c0121b10cf9f",
"engine_version" : "3.0.6",
"admin_user_name" : "root",
"enable_ssl" : false,
"flavor_ref" : "ddm.c6.large.2"
} Status code: 400
Bad request
{
"externalMessage" : "Parameter error.",
"errCode" : "DBS.280001"
} Status code: 500
Server error
{
"externalMessage" : "Server failure.",
"errCode" : "DBS.200412"
} Status Codes
| Status Code | Description |
|---|---|
| 200 | OK |
| 400 | Bad request |
| 500 | Server error |
Error Codes
For details, see Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.