Upload On-premises VMware Cloud Director Resources to Your Cloud Environment

To migrate an on-premises VMware Cloud Director instance to VMware Cloud Director service, you must first upload its resources to your cloud environment.

Prerequisites

  • Verify that you downloaded the database dump and the responses.properties file from your on-premises VMware Cloud Director instance in a single resourses.zip file and that you obtained the checksum for the resources.zip file..
  • Exchange the API token that you generated for an access bearer token. Use the bearer token in the Authorization header for the API call. See How Do I Generate an API Token.
  • Obtain the ID (URN) for the environment that is nearest to your on-premises SDDC. See How Do I Retrieve the List of Environments in My Organization.

Procedure

  1. To upload the resources file to the environment where you want to migrate your VMware Cloud Director instance, run a multipart POST request that includes the resourses.zip file.
    POST https://operatorUrl/environment/environmentUrn/migration/upload-resources
    Table 1. Headers
    Name Value
    Authorization Bearer your-bearer-token
    Content-Type application/octet-stream
    Transfer-Encoding chunked
    Accept application/json
    X-MD5-Checksum md5_checksum_of_resources.zip_file

    Here operatorUrl is the operator URL, for example vcdc-operator-prod-us-west-2.vdp.vmware.com.

    The resource file uploads to the cloud.
  2. Make note of the task ID (URN) in the first line of the API response body.

Example: Upload On-premises VMware Cloud Director Resources to the Cloud

This cURL example uploads the resourses.zip file to the cloud environment where you want to migrate your VMware Cloud Director environment.
  1. Run a cURL POST request with the following parameters.
    POST -X https://vcdc-operator-prod-us-west-2.vdp.vmware.com/environment/urn:vcdc:environment:12345678-1234-1234-1234-123456789abc/migration/upload-resources     
        -H 'accept: application/json' 
        -H 'Content-Type: application/octet-stream' 
        -H 'x-md5-checksum: md5_checksum_of_resources.zip'
        -T resources.zip -H "Transfer-Encoding: chunked" 
        --progress-bar  -v | tee response.out
    Use the bearer token in the Authorization header of the request.
    Authorization: 
    Bearer eyJh…I1NiIs
    The request returns a 200 OK response such as:
    Response: HTTP/1.1 200
    Body:
    {
      "id": "urn:vcdc:task:22222222-2222-2222-2222-22222222222",
      "name": "UPLOAD_RESOURCES_TO_S3",
      "entityId": null,
      "entityName": null,
      "ownerId": "urn:vcdc:organization:12345678-1234-1234-1234-123456789abc",
      "userId": "vmware.com:12a1234b-1234-5678-abcd-12a1aa0123a4",
      "cspUserId": "vmware.com:12a1234b-1234-5678-abcd-12a1aa0123a4",
      "steps": null,
      "status": "SUCCESS",
      "startTime": "2022-07-19T10:05:49.890773Z",
      "endTime": "2022-07-19T10:06:31.008071Z",
      "queuedTime": "2022-07-19T10:05:49.890744Z",
      "message": "UPLOAD_RESOURCES_TO_S3",
      "isolation": "ENTITY_EXCLUSIVE",
      "output": null,
      "activity": ""
    }
    If the task status in the response is Failed, analyze the information provided in the error message for the reason. After fixing it, retry uploading the resources.zip file.

What to do next

Run the /cell-management-tool cell -m true -u command to put the on-premises VMware Cloud Director cells in maintenance mode. For more details, see Managing a Cell.