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.
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
Parameter |
Mandatory |
Description |
---|---|---|
project_id |
Yes |
Specifies the project ID. For details about how to obtain the ID, see Obtaining a Project ID. |
server_id |
Yes |
Specifies the ECS ID. |
Request
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.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot