All Products
Search
Document Center

Enterprise Distributed Application Service:MigrateEcu

Last Updated:Mar 01, 2024

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

Operation description

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 is reinstalled. After the operating system is reinstalled, all data of the ECS instance is deleted. You must set a logon password for the ECS instance. Make sure that no important data exists on or data has been backed up for the ECS instance that you want to import.

Terms

  • Namespace: the logical concept that is used to isolate resources and microservices in Enterprise Distributed Application Service (EDAS). The resources include clusters, ECS instances, and applications. You can use a default or custom namespace. 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 or microservices.
  • 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

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Authorization information

There is currently no authorization information disclosed in the API.

Request syntax

POST /pop/v5/resource/migrate_ecu

Request parameters

ParameterTypeRequiredDescriptionExample
InstanceIdsstringYes

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

i-2zej4i2jdf3ntwhj****
LogicalRegionIdstringNo

The ID of the custom namespace.

  • The ID of a custom namespace is in the region ID:custom namespace ID format. Example: cn-beijing:tdy218.
  • The ID of the default namespace is in the region ID format. Example: cn-beijing.
cn-hangzhou:test_region

Response parameters

ParameterTypeDescriptionExample
object

The content that is returned.

Codeinteger

The HTTP status code that is returned.

200
Messagestring

The additional information that is returned.

success
Datastring

Indicates whether the request is successful. Valid values:

  • true: The request is successful.
  • false: The request fails.
true
RequestIdstring

The ID of the request.

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

Examples

Sample success responses

JSONformat

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

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
No change history