Cold Migrating an ECS¶
Function¶
An ECS deployed on a DeH can be migrated to another DeH.
An ECS deployed on a DeH can be migrated to a public resource pool.
An ECS deployed in a public resource pool can be migrated to a DeH.
This API is an asynchronous API. After the cold migration request is successfully delivered, a job ID is returned. This does not mean the cold migration is complete. You need to call the API by referring to Querying Task Execution Status to query the job status. The SUCCESS status indicates that the cold migration is successful.
Note
If the migration does not cross NUMA nodes, the migration may fail due to insufficient resources on a single NUMA node.
Constraints¶
Currently, this API applies only to dedicated hosts.
Only a stopped ECS can be cold migrated.
Existing constraints of the native cold migration API are inherited.
URI¶
POST /v1/{project_id}/cloudservers/{server_id}/migrate
Table 1 describes the parameters in the URI.
Parameter | Mandatory | Description |
---|---|---|
project_id | Yes | Specifies the project ID. |
server_id | Yes | Specifies the ECS ID. |
Request¶
Table 2 describes the request parameters.
Parameter | Mandatory | Type | Description |
---|---|---|---|
migrate | Yes | Object | Specifies the ECS to be migrated. For details, see Table 3. This parameter is null when you migrate an ECS from a dedicated host to a public resource pool. |
Parameter | Mandatory | Type | Description |
---|---|---|---|
dedicated_host_id | No | String | Specifies the DeH ID. This parameter takes effect when an ECS is migrated from a public resource pool to a DeH or between DeHs. |
Response¶
See Responses (Task).
Example Request¶
Migrate the ECS from the public resource pool to the DeH whose ID is 459a2b9d-804a-4745-ab19-a113bb1b4ddc.
POST https://{endpoint}/v1/{project_id}/cloudservers/{server_id}/migrate
{
"migrate": {
"dedicated_host_id": "459a2b9d-804a-4745-ab19-a113bb1b4ddc"
}
}
Example Response¶
{
"job_id": "ff80808288d41e1b018990260955686a"
}
Returned Values¶
Error Codes¶
See Error Codes.