/*Here i feel is the placement of version dropdown*/

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

Icon

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.

Icon

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

Non-HA Mode

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

  1. In the Configure Orchestrator popup, provide the CCO's 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 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

      Icon

      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.

  4. Repeat Step 2 and Step 3 to establish a mutual trust between the CCM and other CCOs.

You have registered the CCO VM and completed your configuration. You have two options at this point:

HA Mode

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

  1. Ensure that the Tomcat service is running on the Primary CCO.
  2. Login to the Secondary CCO and Tertiary CCO servers and stop the Tomcat service on both servers.

  3. Access the CCM UI and register the CCO using the CCO LB IP address.
    1. If you are not already at this page, verify that you are in the Admin > Clouds > Configure Regions for the required cloud)
    2. Click Configure Orchestrator in the Regions tab.
    3. Provide the CCO's IP address that is accessible by CCM and select the cloud account that is used to host the CCO:

      1. Orchestrator IP or DNS: Provide the IP or DNS address for the CCO server.
      2. 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.

      3. Cloud Account: Select the cloud account that you want to use with this CCO. Be sure to select the cloud account that contains this role.

      4. 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.
  4. After a successful registration, log into the Primary CCO server.
  5. Copy the gateway_config.properties file from the Primary CCO's /usr/local/osmosix/etc/ folder to the same location on both the Secondary CCO and the Tertiary CCO servers.
  6. Verify that the ownership and permissions for the copied file in all servers is as follows:
    • Owner = cliqruser
    • Group Permission = read and write
  7. Run the following commands to change settings – if required:

  8. Start the Tomcat on the Secondary CCO and the Tertiary CCO servers by issuing the following command on each server:

  9. Repeat this procedure for other CCOs in HA mode to establish a mutual trust between the CCM and other CCOs.

You have registered the CCO VM and completed your configuration. You have two options at this point:

  • No labels