Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Building service blueprints for OpenStack service

This topic provides the caveats and considerations you need to review when creating a service blueprint for OpenStack services. It also provides links to the applicable service blueprint documentation. This topic contains the following sections:


Roadmap for service blueprint documentation

The following table provides links to the applicable service blueprint documentation.

Topic

Description

Provides an overview of the service blueprint blueprint workspace.

Describes how to add several of the various types of service blueprint objects, and how to define network connections between those objects.

Considerations for creating a service blueprint for OpenStack Provider

Create service blueprints as described in Building service blueprints. The following table identifies the items to consider when creating a service blueprint for the OpenStack Provider.

 

Note

The following constructs do not apply to OpenStack:

  • PaaS Resource
  • Load balancer pools
  • IP Endpoints/VLAN

Service blueprint construct

Notes specific to OpenStack

Service blueprint parameters

You have defined the following definition-level parameters so that they are applicable on the deployment packages during VM provisioning:

 BmcSecurityGroups 

  • This definition parameter enables an OpenStack instance to be placed within a security group (firewall).
  • This security group allows RSCD agent traffic through port 4750 and remote access through an SSH or RDP port.
  • All comma-separated values should match the security group IDs that you specified in the Access & Security Console of the OpenStack eCloud. 
  • The data type is string.
  • If you select the Enabled option, BMC Cloud Lifecycle Management end users can control firewall policies for a server.
OpenStack Flavor
  • This definition parameter enables VM provisioning. 
  • The data type is string.

In this implementation of the OpenStack Provider, you cannot add new OS users after the VM has been provisioned. However, you can add users by using BMC Server Automation and you must add the following service blueprint definition parameter to enable addition of local users in a provisioned VM:

 UNIX_USER or WINDOWS_USER

  • This definition parameter enables user provisioning.
  • The value name must exactly match the key user name you specified in BMC BladeLogic Server Automation. 
  • The data type is string.
UNIX_USER_PASSWORD or WINDOWS_USER_PASSWORD
  • This definition parameter enables user provisioning. 
  • The value name must exactly match the corresponding password name for the key user name that you specified in BMC BladeLogic Server Automation. 
  • The data type is string.

Note: For instructions, see Creating-a-BLPackage-for-adding-local-users-in-the-OpenStack-Provider.

(OpenStack Provider 4.1.1 only) Openstack Keypair

  • The Openstack Keypair definition parameter enables access to a VM provisioned in the OpenStack cloud (for example: Cloudwatt) using the BMC Cloud Lifecycle Management. Keypairs in OpenStack cloud are used to secure access to your Linux (and retrieve password for Windows instances in Cloudwatt). They allow you to authenticate virtual instances created by you without using a password. A Keypair consists of a public key installed on the server you want to connect, and a private key specified by you.

    Note: You must first create a Keypair in the OpenStack cloud (for example: Cloudwatt console. See the Cloudwatt documentation for details about creating a Keypair in Cloudwatt.) and download the <Keypair>.pem file containing your private key details.
  • The data type is string.
  • The Default Value of the parameter (as shown in the figure below) must contain the Keypair name created in the OpenStack cloud.
    KeyPair.png

Application

The VM must be assigned a security group that ensures TCP port 4750 is open in the VM.

You must first create a BMC Server Automation Deploy Job or an application component template and ensure that the RSCD Agent is installed in a VM that was provisioned in the OpenStack Provider before installation. You can then enable a software installation as a part of an OpenStack service offering.

See the OpenStack Virtual Machine Image Guide for information about creating snapshots and images.

Server

  1. Add or select a server in the blueprint and expand the Compute Resources detail panel.
  2. Select the Cloud Platform as OpenStack, and ensure that the auto-onboarded Definitive Media Library (DML) entry is defined as an Installable Resource in the service blueprint.

Networks

When you enable VM placement in single or multiple subnets for a Virtual Network, you must define single or multiple subnets for a Virtual Network in a service blueprint and tag them appropriately (as shown in the figure below).
SBNetTag.png

For more information, see Tagging-recommendations-and-examples. To create or manage tag groups and tags from the Service Designer workspace, see Managing-blueprint-tags.

Where to go from here

Proceed to Managing-the-OpenStack-service-offerings.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*