Creating OpenStack blueprints

After you have mapped the tenants to the network containers, you then can define your service blueprint, add application parameters to your service deployment definition, prepare the service offering instance, and define your service offering options in the Service Catalog. These tasks follow the typical BMC Cloud Lifecyle Management workflow.

The following topics provide information and instructions for creating OpenStack blueprints:

Service blueprint guidelines for the OpenStack Provider

Be aware of the following guidelines that are specific to the OpenStack Provider service offering:

The DML entry in the service blueprint must have the placeholder OS entry associated with it.
The auto-onboarded DML entry is defined as an installable resource in the service blueprint.
Three unique application parameters are available: BmcSecurityGroups, UNIX_USER, and UNIX_USER_PASSWORD.
You add OpenStack Flavor as service offering option in the Service Catalog.

To verify available operating systems

The OpenStack implementation relies on BMC Server Automation's Publish Product Catalog Job to create a placeholder catalog entry in BMC Atrium CMDB. This placeholder catalog entry enables an OS package to be associated with the OpenStack Flavor component entry in the service blueprint. The placeholder OS entry is of the type BladeLogic.

Note

This placeholder entry is required for creating the blueprint, not for provisioning OpenStack instances.

From the BMC Cloud Lifecycle Management Administration Console, choose the Service Blueprint workspace.
Click New to open the Service Blueprint Definition window.
Under the Components section, click New to display the Component Details - Operating System tab. The available OS or systems are displayed. In this example, the selected placeholder OS entry is DummyOS which is associated with the type BladeLogic.
If no OS packages are available, launch a Publish Product Catalog Job in BMC Server Automation to make a package available to BMC Cloud Lifecycle Management.
For instructions, see Publishing the Product Catalog Job. The OS package, even if it is a placeholder, must be present before you can create a service blueprint.

To create a service blueprint

To create a service blueprint for an OpenStack instance, you can follow the general service blueprint creation procedure. However, you should also follow the guidelines that describe the distinctions for service blueprints that are created for OpenStack instances.

In the Service Blueprint window, click New to open the Service Blueprint Definition window.
Follow the steps for creating a service blueprint. See Building a Service Blueprint and related procedures.

To select a software package for deployment

To select a software package for deployment, see Installing-software-as-a-part-of-the-service-offering-in-the-OpenStack-Provider .

Note

This implementation of the OpenStack Provider does not support adding new OS users after the virtual machine (VM) has been provisioned. However, you can incorporate this feature by using BMC Server Automation. For instructions, see Creating-a-BLPackage-for-adding-local-users-in-the-OpenStack-Provider.
For details on defining OpenStack service deployment definitions and resource sets, see Creating-OpenStack-service-deployment-definitions-and-resource-sets.

To prepare the service offering instance

Create and test an OpenStack instance as you would any service offering. For detailed procedures, see Creating-cloud-services.

To set service offering options

In the OpenStack Provider, a Flavor defines a set of virtual resources. Through BMC Cloud Lifecycle Management, Flavors are provided as service offering options. If this mandatory requirement requirements is not met, instance creation for the OpenStack Provider will not succeed. You set the service offering options for OpenStack instances as you would for other options.

For background information and instructions for defining options, see Service-Catalog-options-and-option-choices. For information and instructions for preparing service offering instances, see Creating-cloud-services.

An OpenStack Flavor distinguishes the options that are available for OpenStack offering instances. Like other service options, you add these options to the service offering definition in the Service Catalog.

The following example shows the Options Editor listing the choices for an OpenStack Flavor option.

The following example shows an OpenStack Flavor that is attached to an offering as an option:

To create the requestable offering definition

Define your OpenStack requestable offering as you would any other offering. For instructions, see Creating-a-requestable-offering-definition.

For the OpenStack definition, you select OpenStack for the Type value: