Connecting the blueprint design server to the SoftLayer cloud

To connect the blueprint design server to the SoftLayer® cloud system, map the SoftLayer account information to a functional ID. Then, assign that functional ID to a team.

Before you begin

About this task

The following diagram shows a typical topology for this scenario. The blueprint design server and engine connect to the SoftLayer cloud. For authentication information, the blueprint design server connects to the Keystone identity service and optionally to an LDAP server.
A topology that includes the blueprint design server, the engine, SoftLayer, a Keystone server, and an optional LDAP server

Procedure

  1. Log in to the blueprint designer as a user with the following System permissions:
    • Configure Security
    • Manage Users & Groups
  2. Create a connection to the cloud:
    1. Click Settings > Clouds.
    2. Click Add New Cloud.
    3. Specify a name for the cloud connection.
    4. In the Type list, select SoftLayer.
    5. In the Endpoint Type list, select the type of URL for the Heat engine. You can determine the type of Heat URL by examining the Keystone endpoint list. To view the Keystone endpoint list, run the following command:
      openstack endpoint list
      • If you connect through a private URL, select Internal.
      • If you connect through a public URL, select Public.
    6. In the Identity URL field, specify the location of the identity service, such as http://example.com:5000/v2.0 or http://example.com:5000/v3. Do not include a trailing slash.
    7. In the Timeout in Mins field, specify the amount of time in minutes to wait for a provision request to be completed. If you deploy IBM UrbanCode Deploy components, allow sufficient time for the cloud to provision your instance, the agent to come online, and all processes to run. See Creating a IBM UrbanCode Deploy timeout configuration file. If you apply Chef roles to environments, allow sufficient time for the Chef roles to be completed.
    8. Clear the Use default orchestration engine check box and then in the Orchestration Engine URL field, specify the location of the engine that you installed in Installing engines, such as http://engine.example.com:8004.
      Note: Do not use the localhost variable in this field, even if the engine is on the same system as the blueprint design server.
    9. Optional: Select the cost center to use to estimate the cost of environments on this cloud.
    10. Click Save.
  3. Create one or more cloud projects that tie the functional ID on the Keystone server to the SoftLayer account information. See Creating cloud projects for the blueprint designer.
  4. Add the cloud project to a team. See Configuring blueprint design server teams.
  5. Add users to the team and to one or more roles on the team. These users can come from any authentication realm, including LDAP servers, Keystone identity services, or from the internal authentication realm.
  6. Make sure that the team roles include the appropriate permissions for those users, such as creating and editing blueprints.

Results

Users can log in to the blueprint designer and use the cloud connection. At the top of the page, users can select the SoftLayer cloud connection, cloud project, and region. When they edit blueprints, the palette shows resources that are available to the SoftLayer account, and they can provision blueprints to the selected SoftLayer region. The palette shows all custom images that you upload to the SoftLayer cloud. To use a public image or a default image on the SoftLayer cloud, provision a VM from the image, and configure it for use with the blueprint designer. See Configuring private SoftLayer images.

What to do next


Feedback