forked from docs/doc-exports
Reviewed-by: Pristromskaia, Margarita <margarita.pristromskaia@t-systems.com> Co-authored-by: Zaoxu, Li <lizaoxu@huawei.com> Co-committed-by: Zaoxu, Li <lizaoxu@huawei.com>
10 KiB
10 KiB
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.
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.
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.
Parent topic: Status Management