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

Configure a SoftLayer Cloud

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

Prerequisites

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

  • A valid SoftLayer PORTAL account.

  • SoftLayer Account Name: The exact name displayed in the Username column in the SoftLayer Portal's Users page. Copy the required Username and paste it in the CloudCenter CCM UI as specified during the Configuration Process identified below.
  • SoftLayer Account API Key: This is the API key for this user's account: If you do not have an API key for this account, retrieve the API key at this point.

    Copy this API key and paste it in the CloudCenter CCM UI as specified during the Configuration Process identified below.

    • Already Generated API Key: Access the SoftLayer Portal's Users page. Click View (in API Key column corresponding to the required user).
    • Not Generated an API Key: Access the SoftLayer Portal's Users page. Click Generate (in API Key column corresponding to the required user).

  • Device Name: This is the exact name displayed in the Device Name column in the SoftLayer Portal's Device List page. Copy the required Device name and paste it in the CloudCenter CCM UI as specified during the Configuration Process identified below.

    You MUST launch the CCO in the same cloud region as this SoftLayer device – you cannot select different regions for the CCO and this device.

  • Images: This is the exact name displayed in the Image Template Details section in the SoftLayer Portal's Images page.

    Copy the required Image Name and paste it in the CloudCenter CCM UI as specified during the Configuration Process identified below.

Configuration Process

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

  1. Access the CCM UI > Admin > Clouds > Add Cloud in the CCM UI main menu.
     
  2. Select the SoftLayer an IBM Company option, provide a Name and Description for this cloud, and click Save.
  3. Locate the newly-added cloud and click the Add Cloud Account link. The Add Cloud Account pop-up displays:

    1. Assign a new cloud name.

      Tip

      The name should not contain any space, dash, or special characters.

    2. Add the following Cloud Credentials associated with your SoftLayer account and click Save.

      1. SoftLayer Account Name: The SoftLayer Username identified in Prerequisites section above.

      2. SoftLayerAccount API Key: The SoftLayer API Key identified in Prerequisites section above.

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

      The Instance Types, the Storage Types, and the Image Maps sections are automatically populated with as soon as you add the region.

  5. Click Edit Cloud Settings to update the SoftLayer cloud settings for each region.

    1. DefaultprivateVlanNumber: Specifies the default SoftLayer private cloud network to which this CloudCenter instance must be launched.

    2. Default publicVlanNumber: Specifies the default SoftLayer public cloud network to which this CloudCenter instance must be launched..

    3. Click Save.

      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

  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.

    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