Overview of the OpenStack Provider

Installing-the-OpenStack-Provider

or/-

Upgrading-the-OpenStack-Provider

Cloud Administrator

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

Configuring-the-OpenStack-Provider

Cloud Administrator

Typically you perform the activities of the setup phase of your OpenStack Provider only once. These activities include configuring the OpenStack Provider, 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 BMC Cloud Lifecycle Management application.

Note: For the custom Glance images, ensure that 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.

• Adding-suspend-and-resume-operator-actions
• Registering-the-OpenStack-Provider-instance
• Managing-multiple-OpenStack-accounts

Configuring-resources-for-the-OpenStack-Provider-services

Cloud 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-tenant-and-user-quota-for-the-OpenStack-Provider
• Managing-the-OpenStack-Logical-Data-Centers
  
  Note: To enable VM placement in specific subnets of an OpenStack Virtual Network, you must tag the subnet individually and also define the same Network Type tags in the OpenStack service blueprint. See To edit a Logical Data Center for details.

Managing-the-OpenStack-service-offerings

Cloud Administrator

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

• Creating-options-and-option-choices-in-the-OpenStack-Provider
• Creating-a-BLPackage-for-adding-local-users-in-the-OpenStack-Provider
• Building-service-blueprints-for-OpenStack-service
• Creating-the-service-offering-for-OpenStack

Request an OpenStack cloud service

Cloud Administrator, End User

You can request an OpenStack cloud service from the BMC Cloud Lifecycle Management – My Cloud Services Console.

Managing-OpenStack-services

Cloud Administrator, End User

Allows you to manage your OpenStack services (start, stop, decommission, share, and transfer ownership).

Managing-OpenStack-servers 

Cloud Administrator, End User

Allows you to manage your OpenStack servers (start, stop, shutdown, suspend, resume, add disk, modify CPU RAM and install software).

Logical Data Center

Tenant, project

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

Network/Subnet

Network

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

Logical network

Network

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

Virtual guest

OpenStack virtual machine (VM)

None.

IP address

IP address

None.

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)

None.

Support for OpenStack public cloud (Cloudwatt)

You must first configure the public cloud account details 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.

Support for Self Service

You can perform the following self service actions using the OpenStack Provider:

• Request an OpenStack cloud service (See Managing-the-OpenStack-service-offerings for details.)
• Share services with other users (See Managing-OpenStack-services for details.)
• Transfer ownership of service offering instances (See Managing-OpenStack-services for details.)

Support for allowing 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 you want to connect, and a private key specified by you.

See Building-service-blueprints-for-OpenStack-service for details.