Overview of the OpenStack Provider

OpenStack is a global collaboration of developers and cloud computing technologists that produces the open source cloud computing platform for public and private clouds.

This topic contains the following sections:

Product overview

The OpenStack integration with BMC Cloud Lifecycle Management enables you to leverage the cloud computing services of the OpenStack Provider from the BMC Cloud Lifecycle Management Administration Console. You can use BMC Cloud Lifecycle Management to provision infrastructure from OpenStack.

With OpenStack Provider integration with BMC Cloud Lifecycle Management, you can perform the following actions:

  • Onboard and offboard a Logical Data Center.
  • Register an OpenStack Provider instance.
  • Provision new VMs that are based on OpenStack templates or a customized template.
  • Place VMs on specific subnets.
  • Start, stop, shut down, suspend, and resume provisioned VMs.
  • Modify memory and CPU values of provisioned VMs.
  • Add disks for provisioned VMs.
  • Decommission provisioned machines.
  • Extend the commission length of provisioned VMs.
  • Install software on provisioned VMs (both pre- and postprovisioning).
  • Add a local user on provisioned VMs (both pre- and postprovisioning).
  • Manage tenant or user quota in BMC Cloud Lifecycle Management.
  • Create multiple OpenStack accounts.
  • Use the OpenStack public cloud (Cloudwatt).


    You must first configure the public cloud account details by using Managing multiple OpenStack accounts before configuring the cloud resources, managing the cloud service offerings, and requesting a cloud service in an OpenStack public cloud.

  • Allow SSH Keypair during provisioning.


    You must define the Openstack Keypair service blueprint definition-level parameter to enable access to a VM provisioned in the OpenStack cloud (for example: Cloudwatt) using BMC Cloud Lifecycle Management. Keypairs in OpenStack cloud are used to secure access to your Linux instance (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 to which you want to connect, and a private key specified by you.

    See Building service blueprints for OpenStack service for details.

  • Use the Self Service feature. See Managing the OpenStack service offerings and Managing OpenStack services for details.
  • Monitor server and tenant details of the OpenStack Provider by using the Value Dashboard. See Monitoring server and tenant usage for details.
  • Request and manage OpenStack services and servers using either the legacy or the new My Cloud Services Console. See Managing the OpenStack service offeringsManaging OpenStack services and Managing OpenStack servers for details.

Back to top

Supported releases of OpenStack

The following components of the OpenStack releases (along with the respective API details) are supported in BMC Cloud Lifecycle Management 4.5.00 and its service packs and patches: 

API versionSupported
in 4.5
Keystone  Kilo



You must install the OpenStack Provider Hotfix to get support for OpenStack Juno and Kilo. For more information about the OpenStack CLM ZipKit, see https://communities.bmc.com/docs/DOC-25271.

Back to top

High-level tasks for setting up an OpenStack Provider

The following sections lists the high-level tasks that you must complete to set up an OpenStack Provider for a private and public cloud and initiate an OpenStack service instance.

Process stageRoleTask

Installing the OpenStack Provider


Upgrading the OpenStack Provider

Cloud Administrator

You must install or upgrade the OpenStack Provider first before using it.

Note: Before installing or upgrading an OpenStack Provider ensure that the prerequisites are met. See Prerequisites for installing the OpenStack Provider for details.

Configuring the OpenStack ProviderCloud Administrator

Typically you perform the activities of the setup phase of your OpenStack Provider only once. These activities include configuring the OpenStack Provider and setting up the OpenStack private or public cloud account credentials details in the BMC Cloud Lifecycle Management to auto-onboard the OpenStack Snapshots and Images as DML entries in the BMC Cloud Lifecycle Management application.

Note: For the custom Glance images, you must connect to the OpenStack server and set a property name os_name in the Glance image. See Note for setting os_name property.

Configuring resources for the OpenStack Provider servicesCloud Administrator

After you have configured the OpenStack account, you must configure the following resources in BMC Cloud Lifecycle Management to provision an OpenStack service:

Managing the OpenStack service offeringsCloud Administrator

In this final phase, you prepare and initiate the service offering request, as described in the following topics:

Request an OpenStack cloud service in the new My Cloud Services Console 


Request an OpenStack cloud service in the legacy My Cloud Services Console

Cloud Administrator, Tenant Administrator, End User

You can request an OpenStack cloud service from the BMC Cloud Lifecycle Management –  by using the new My Cloud Services Console or the legacy My Cloud Services Console

See also Considerations for requesting an OpenStack service on behalf of another user.

Managing OpenStack servicesCloud Administrator, End User

You can perform several operations on your OpenStack services (start, stop, shut down, decommission, restart, share, and transfer ownership).

Note: You can only start, stop, shut down, decommission and restart the OpenStack services by using the new My Cloud Services Console. See Managing cloud services for details of these operations.

Managing OpenStack servers Cloud Administrator, End User

You manage your OpenStack servers by using the new My Cloud Services console and the legacy My Cloud Services Console. For details, see the following sections in Managing OpenStack servers :

  • "To start or stop a server"
  • "To shut down a server"
  • "To manage system disk of a server"
  • "To modify CPU count and memory size for a server"
  • "To install software on a server"
  • "To add local OS users on a server"
  • "To suspend or resume a server"


Removing a disk, and suspending and resuming an OpenStack server are not supported by the new My Cloud Services Console. As a best practice, perform these operations by using the legacy My Cloud Services Console.

Back to top

OpenStack construct mappings

The following table lists BMC Cloud Lifecycle Management objects and describes how they correspond to OpenStack constructs:

BMC Cloud Lifecycle Management object mappings for the OpenStack Provider

BMC Cloud Lifecycle Management object

OpenStack construct


Logical Data Center

Tenant, project

This object is represented by a project in the OpenStack Provider.



This object is represented by the network/subnet defined in the OpenStack environment.

Logical network


This object is represented by the network defined in the OpenStack Provider.

Virtual guest

OpenStack virtual machine (VM)


IP address

IP address


System disk

Root disk, Ephemeral disk, Volume

System disk is created with the combination of Root disk and Ephemeral disk defined as part of Flavor. Volumes attached to VMs in the OpenStack Provider are also created as System disk in BMC Cloud Lifecycle Management.

Operating system

Operating system

The OpenStack Provider creates VMs through available Images. The operating system properties must be defined as metadata of the Image.

Server network interface

Network Interface Cards (NICs)


Back to top


  • BMC Cloud Lifecycle Management does not synchronize modified or deleted OpenStack templates.
  • When you deregister an OpenStack Provider instance, the OpenStack installable resources are not removed automatically.
  • Registering an OpenStack Provider instance with an incorrect OpenStack user name and password does not produce an error.
  • Any operation that exceeds the poll time that is specified during provider registration fails in BMC Cloud Lifecycle Management, but is updated in the OpenStack Provider. In this situation, resources are not synchronized.


To view the known issues details of the OpenStack Provider, see Known and corrected issues for BMC ZipKits for Cloud.

Back to top

Was this page helpful? Yes No Submitting... Thank you