MigrateBandwidthClusterResources

1. API Description

This API is used to migrate resources between bandwidth clusters.

Note

  • Resources already in the target bandwidth cluster ill be ignored.

  • If any resource is not eligible for the target bandwidth cluster, the entire migration will fail. No resources will be migrated.

  • Traffic before the change will be counted under the original bandwidth cluster; traffic after the change will be counted under the new cluster.

2. Input Parameters

The following request parameter list only provides API request parameters.

Parameter Name
Required
Type
Description

targetBandwidthClusterId

Yes

String

Target bandwidth cluster ID.

resourceIdList

Yes

Array of String

IDs of resources to migrate.

Resources must belong to a different bandwidth cluster, and networkType and areaCode of the original bandwidth cluster must match those of the target cluster.

3. Output Parameters

Parameter Name
Type
Description

requestId

String

The unique request ID, which is returned for each request. RequestId is required for locating a problem.

4. Code Example

Migrate resources to a specified target bandwidth cluster.

POST /api/v2/traffic HTTP/1.1
Host: console.zenlayer.com
Content-Type: application/json
X-ZC-Action: MigrateBandwidthClusterResources
<Common Request Params>

Request:
{
    "resourceIdList": ["<id1>","<id2>"],
    "targetBandwidthClusterId": "<targetBandwidthClusterId>"
}

Response:
{
  "requestId": "T05992D0C-7E8B-4047-B0C0-780F2CD549D3",
  "response": {
    "requestId": "T05992D0C-7E8B-4047-B0C0-780F2CD549D3"
  }
}

5. Developer Resources

Zenlayer Cloud API 2.0 integrates SDKs to make it easier for you to call APIs. More programming languages will be supported.

6. Error Codes

The following only lists the error codes related to the API business logic. For other error codes, see Common Error Codes.​​

HTTP Status Code
Error Code
Description

404

INVALID_CLUSTER_NOT_FOUND

Bandwidth cluster does not exist.

404

INVALID_CLUSTER_RESOURCE_NOT_FOUND

Resources must belong to a bandwidth cluster.

409

INVALID_CLUSTER_MISMATCH_RESOURCE

networkType and areaCode of the original bandwidth cluster must match those of the target cluster.

Last updated