Migrates an elastic compute unit (ECU) to the default cluster in a specified namespace.

Limits

We recommend that you do not call this operation. Instead, we recommend that you call the TransformClusterMember operation. For more information, see TransformClusterMember.

When you call this operation to import an Elastic Compute Service (ECS) instance, the operating system of the ECS instance will be reinstalled. After the operating system is reinstalled, all data on the ECS instance will be deleted and you must set a logon password for the ECS instance again. Make sure that no important data exists or data has been backed up on the ECS instance that you want to import.

Basic concepts

  • 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.
  • ECU: After an ECS instance is imported to a cluster, the instance becomes an ECU.
  • ECC: After you deploy an application to an ECU in a cluster, the ECU becomes an elastic compute container (ECC).

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request headers

This operation uses only the common request header. For more information, see Common request parameters.

Request syntax

POST /pop/v5/resource/migrate_ecu HTTPS|HTTP

Request parameters

Parameter Type Required Example Description
InstanceIds String Yes i-2zej4i2jdf3ntwhj****

The ID of the ECS instance. Separate multiple IDs with commas (,).

LogicalRegionId String No cn-hangzhou:test_region

The ID of the namespace.

  • The ID of a custom namespace is in the format of Region ID:Namespace identifier. For example, cn-beijing:tdy218 is the ID of a custom namespace.
  • The ID of the default namespace is in the format of region ID. For example, cn-beijing is the ID of the default namespace.

Response parameters

Parameter Type Example Description
Code Integer 200

The HTTP status code.

Data String true

The returned data.

Message String success

The returned message that indicates whether the request is successful.

RequestId String 04B0ABAF-95F2-42B6-A7B1****

The ID of the request.

Examples

Sample requests

POST /pop/v5/resource/migrate_ecu HTTP/1.1
Common request header
{
  "InstanceIds": ""
}

Sample success responses

XML format

<Message>success</Message>
<RequestId>04B0ABAF-95F2-42B6-A7B1-8A832E863C92</RequestId>
<Data>true</Data>
<Code>200</Code>

JSON format

{
	"Message": "success",
	"RequestId": "04B0ABAF-95F2-42B6-A7B1-8A832E863C92",
	"Data": true,
	"Code": 200
}

Error codes

For a list of error codes, visit the API Error Center.