Deploying IBM UrbanCode Deploy Blueprint Designer Cloud Applications Part 1 – Connecting to the AWS Cloud

This blog series is about deploying your first IBM UrbanCode Deploy Cloud application using UCD, the Blueprint Designer, and Amazon Cloud Services. IBM used to refer to the Blueprint Designer extension with UCD as UrbanCode Deploy With Patterns (UCDP) but seems to have dropped that distinction after bundling the applications post version 6.1.1.  It is now simply referred to as the Blueprint Design (BPD). To begin, we assume that you already have the BPD product components installed and you have an AWS account.  With those in place, the first part of our journey is to connect UCDP with the AWS Cloud. 

Understanding the OpenStack Components

UCDP comes with a set of packaged Openstack services – Orchestration (HEAT) and Identity (Keystone). The HEAT engine is how BPD communicates with Openstack based clouds like AWS, Azure, and SoftLayer. Keystone is a requirement of the Orchestration Service and is needed for BPD and HEAT to authenticate with AWS. The installation preconfigures a couple of Keystone projects (tenants), roles, and users that are necessary for BPD to connect to the AWS cloud.  The same values can be used over and over again to configure additional cloud connections.   The Identity service objects are only used for the cloud connections, whereas the identity, and authentication of BPD users, is typically managed through an enterprise directory.  Authorization for users is then managed in the Blueprint Designer.

The Cloud Agents

UCD also comes with Cloud agents. These are UCD agents for the various supported platforms.  If you are familiar with UCD and how to manually extract and deploy agents, the cloud agents provided here are added as components to UCD.  So these are now deployable components and their deployment is automated at provisioning time. The cloud agent package also adds an example component and application to UCD.

Integrating UCD and BPD

The first step is to login to BPD and create a UCD security realm.  This will allow you to import users from UCD into the Blueprint Designer. In UCD create a token and then create a Blueprint integration using that token.

Creating an AWS Cloud Connection

In order to see UCD components in the Blueprint Designer you first need a cloud connection. This is a bug that will be corrected in the next release of UCD. In BPD, under Administration, select Clouds and create a cloud connection.  In the Edit tab give the connection a name and select AWS cloud type. Uncheck “Use default orchestration engine” and enter the Identity and Orchestration end points.  Replace {hostname} with the fully qualified name of the server hosting the Openstack Identity and HEAT services.  Click Save.

Figure 1 – Creating an AWS Cloud Connection

DArnone pt 1 fig 1

Next, the projects and users created in the Identity service will be used to authenticate BPD and HEAT to AWS. In the Authorization tab, supply the Identity project, user and password.  You will also need your AWS Access Id and Secret Key.  Click Test Connection and then Save.

Figure 2 – AWS Cloud Authentication

DArnone pt 1 fig 2

Navigate to Blueprints on the left side of the web page. From the palette on the right, open the various drawers to view UCD components and cloud resources.  If you don’t see components, go back into UCD and make sure you are in a team that is mapped to components and have appropriate rights.  To build a blueprint you simply drag resources from the palette onto the canvas.  That is all there is to it!

David J. Arnone is an ALM and DevOps Architect specializing in IBM CLM and UrbanCode Deploy solutions and services. As a certified Rational CLM Architect, David joined Zilker Technology in January, 2017 and is part of the growing Zilker DevOps practice team.David Arnone. David Arnone

TAGS

NEWSLETTER

Don't miss out! Get updates on new webcasts, events, and blogs.