Configure a vCD Cloud

Be aware that these screen captures may change based on the vCD changes. They are provided in this section as a point of reference.


Before mapping a vCD cloud on the CloudCenter platform, verify the following requirements:

  • A valid vCD cloud account.

  • Launch the CCO in the same cloud region as the vCD cloud.

  • Follow this procedure to enable the vCD cloud provider in the CCO server – If you use the vCD cloud, you must configure the CCO servers.  

    To enable the vCD cloud provider in the CCO server, follow this procedure.

    1. Copy the rest-api-schemas-8.10.0.jar  and vcloud-java-sdk-8.10.0.jar files to the /usr/local/cliqr/lib directory.

      Customers must use their copy of these libraries as these copies are not redistributable by Cisco. The 8.10.0 version is required.

    2. Change the permission and owner for both jar files.

      chmod 755 rest-api-schemas-8.10.0.jar vcloud-java-sdk-8.10.0.jar
      chown cliqruser:cliqruser rest-api-schemas-8.10.0.jar vcloud-java-sdk-8.10.0.jar
    3. Restart the Gateway service so the CCO server automatically uses the vcloud-java-sdk and rest-api-schemas jar files.

      systemctl restart gateway

Configuration Process

To configure the logical mapping for a vCD cloud, follow this procedure.

  1. Access the CCM UI > Admin > Clouds > Add Cloud in the CCM UI main menu.

  2. Select the VMware vCloud Director option, provide a Name and Description for this cloud, and click Save.

  3. Locate the newly-added cloud and click Add Cloud Account to add an account for this cloud family. The Add Cloud Account popup displays.

    1. Assign a new cloud account Name.

    2. Select the check box to Track Cloud Costs.

    3. Provide the vCD user details.

      Cloud Account DetailsDescription
      vCloud Organization NameThe vCloud organization to which this account belongs.
      vCenter Username/PasswordThe vCloud user name that you determined when you performed the site assessment.

      The vCloud Director user requires the App Author permissions for the desired organization in the vCD cloud in order to deploy applications using the CloudCenter platform.

    4. Click Save and verify that the newly added cloud is displayed in the Cloud Configurations page.

  4. Click the Regions tab to add a cloud region.

    1. Click Add Region.

    2. Select the required regions for this cloud.

    1. Add the Region Name and an optional Display Name for this cloud region.

      The Region Name must be the same as the Region Name provided in the vcdconfig file (referenced in the Prerequisites section above).

  5. Caution

    If you Edit Cloud Settings, you must save the changes to the CCO to ensure that these changes are also propagated to CCOs inside a firewall configuration.

    If your CCO is already configured, you must re-register the CCO for these Cloud Settings to take effect.

    vCloud Endpoint URL

    The base vCD URL.
    For example:

    The URL for org suffix is automatically added by the CloudCenter platform.

    Instance Naming StrategySee Region-Level Cloud Settings for additional context.
    Node Name ConfigSee Region-Level Cloud Settings for additional context.
    Instance IPAM StrategySee Region-Level Cloud Settings for additional context.
  6. To complete the cloud configuration, you must register the CCO with the CCM.

     Register the CCO with the CCM

    Register the CCO with the CCM

    Cloud Region Nuances

    Once you register a CCO with the CCM, the CCO only works for the registered cloud region.


    Once you register a CCO with the CCM, the CloudCenter platform considers this cloud region to be active and you can only delete the cloud region from the CloudCenter platform under specific conditions. See Cloud Region Configuration > Delete Cloud Region for additional details.

    While the example provided references the AWS cloud, be aware that the screen captures may differ for each cloud.

    Registration Process

    To register the CCO with the CCM, follow this procedure:

    1. In the Configure Orchestrator popup, provide the CCO IP address that is accessible by CCM and select the cloud account that is used to host the CCO:

    2. If you are not already at this page, verify that you are in the Configure Regions page (Admin > Clouds > Configure Regions for the required cloud).

      1. Click Configure Orchestrator in the Regions tab.

      2. Orchestrator IP or DNS: Provide the IP or DNS address for the CCO server.

      3. Remote Desktop Gateway DNS or IP: The IP address of the Guacamole server (enables browser-based access to the VMs). If the Guacamole component resides in the AMQP server, provide the IP address of the AMQP server.

      4. Cloud Account: Select the cloud account that you want to use with this CCO.

        Amazon Cloud Nuance

        This setting is important if you have configured an IAM Role. Be sure to select the cloud account that contains this role.

    3. Click Save. The CCM and CCO have now established a mutual trust relationship. The CloudCenter platform now manages the cloud region with the deployed CCO.

      If in HA mode while registering, provide the IP or DNS of the CCO_LB server in the Orchestrator IP or DNS field and the AMQP_LB server IP or DNS in the Remote Desktop Gateway DNS or IP field.

    You have registered the CCO VM and completed your configuration.

    Next Steps

    You have the following options at this point:

Return to: Configure Cloud(s)

Terms & Conditions Privacy Statement Cookies Trademarks