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

Configure a IBM Bluemix (SoftLayer) Cloud

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

Prerequisites

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

  • A valid IBM Bluemix PORTAL account.

  • IBM Bluemix Account Name: The exact name displayed in the Username column in the IBM Bluemix Portal's Users page. Copy the required Username and paste it in the CloudCenter CCM UI as specified during the Configuration Process identified below.

  • IBM Bluemix 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 IBM Bluemix Portal's Users page. Click View (in API Key column corresponding to the required user).

    • Not Generated an API Key: Access the IBM Bluemix 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 IBM Bluemix 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 IBM Bluemix device – you cannot select different regions for the CCO and this device.

  • Images: CloudCenter 4.9.0 supports both Image ID and Image Template Name:

    • Image ID: This is the preferred option as it resolves image name conflicts caused by multiple images having the same name. To find the Image ID, navigate to the Bluemix Portal's Template page and copy the Image ID that similar to the ID highlighted in this URL example: 
      https://control.softlayer.com/devices/images/1838253?imageType=public

    • Image Template Name: This is the exact name displayed in the Image Template Details section in the IBM Bluemix 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 IBM Bluemix cloud, follow this procedure.

  1. Access the CCM UI > Admin > Clouds > Add Cloud in the CCM UI main menu.
     
  2. Select the IBM Bluemix 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 account name.

      Tip

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

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

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

      2. IBM Bluemix Account API Key: The IBM Bluemix 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. (CloudCenter 4.8.2x and earlier) Click Edit Cloud Settings to update the IBM Bluemix cloud settings for each region.

    This selection is not available in CloudCenter 4.9.0 and later. You can configure these VLAN and subnet settings on a per-deployment basis as listed in Environments and Deployment Environment Defaults.


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

    2. Default publicVlanNumber: Specifies the default IBM Bluemix 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. (Optional effective CloudCenter 4.9.0 and later) Click Edit Cloud Settings to update the Domain Name. In the IBM cloud console, the domain name is displayed next to the device name.

  7. (Optional effective CloudCenter 4.9.0 and later) Update the Instance Naming Strategy, 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.

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

    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)

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