CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

Configure an OpenStack Cloud

To configure the logical mapping for an OpenStack cloud, follow this procedure.

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

  2. Select OpenStack, 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.
  4. Click Add Cloud Account to add an account for this cloud family. The Add Cloud Account popup displays.

    If OpenStack users do not have full administrator rights, verify that each user (using CloudCenter) has access credentials at a minimum.

    Cloud Account DetailsDescription
    OpenStack User Name/PasswordThe credentials to access this cloud account.
    Default Domain Name (V3)Optional. When you add an OpenStack cloud account, you can choose V2 or V3 OpenStack endpoints: 
    • Not required if you use V2

    • If you use V3, provide either the default Domain ID or Default Domain Name.

    • The cloud region setting validates the region.

    Default Domain ID (V3)
    Default Tenant Name (V3 Project Name)

    Optional. The OpenStack project name.

    Default Domain ID (V3 Project ID)Optional. If set, the Default Tenant ID (OpenStack setting in CloudCenter) has precedence over the Default Tenant Name.
    1. Assign a new cloud Name.

    2. Select the check box to Track Cloud Costs.

    3. Provide the OpenStack user credentials.

    4. Optional. You can add the Domain ID and Domain Name to configure an OpenStack domain that uses their V3 APIs. If you select a V3 API domain, provide the Domain ID or the Domain Name.

    5. Click Save and verify that the newly added cloud account (see Cloud for additional context on terminology) is displayed in the Clouds page.

    6. Click the Configure Cloud link. The Accounts tab in the Cloud Accounts page displays all configured cloud accounts.

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

    1. Click Add Cloud Regions.

    2. Select the required regions for this cloud.

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

    2. Click Save.

  6. Click the Edit Cloud Settings link to update the settings for each cloud region.

    • Required settings:

      • Region (the region must be a valid OpenStack region)

      • OpenStack Keystone API Version (the dropdown list includes both v2 and v3 options – select one of these options)
      • OpenStack Keystone Authentication Endpoint (this setting is not available in the Cloud Account popup, it is only available in the Cloud Region popup)

    • Optional settings: The Instance Naming Strategy, the Instance IPAM Strategy, or the Node Name Config fields. The Region-Level Cloud Settings section provides more details on configuring these values.

      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.

    • To update the Use Config Drive and Nodes Per Batch fields, see Cloud Configuration. 

  7. 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.

    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.

    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

        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.

      /etc/init.d/tomcat stop
    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:

      chown 
      cliqruser:cliqruser /usr/local/osmosix/etc/gateway_config.properties
      chmod 644 /usr/local/osmosix/etc/gateway_config.properties
    8. Start the Tomcat on the Secondary CCO and the Tertiary CCO servers by issuing the following command on each server:

       /etc/init.d/tomcat start
    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:

Return to: Configure Cloud(s)

© 2017-2019 Cisco Systems, Inc. All rights reserved