// removed jquery ui css and js

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.

CloudCenter

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:


  • No labels
© 2017-2018 Cisco Systems, Inc. All rights reserved