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.

Managing the OpenStack service offerings

This topic describes how to create and manage OpenStack service offerings that cloud users can request from the BMC Cloud Lifecycle Management – My Cloud Services Console.

A service offering describes a function or capability that a cloud administrator makes available to users in the cloud. Application stacks, single servers, and adding a new account to a Microsoft Exchange server are all examples of services. For more general information about services, see Services-overview.

After you have mapped tenants to Logical Data Centers or network containers, you then can define your service blueprint for the OpenStack Provider. Service blueprints define the software, hardware, and deployment options for a service in the Service Catalog. A service blueprint is required before you can create a service. For more information, see Service blueprints overview.

You can group requestable offerings into packages, to which different tenants can be entitled. This grouping makes it easier for service providers to partition and manage services created specifically for particular tenants.

The following topics provide information and instructions for creating and managing an OpenStack service using BMC Cloud Lifecycle Management:

Task

Description

Create service blueprints according to the guidelines that are specific for the OpenStack Provider.

Note: 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. For instructions, see Creating-a-BLPackage-for-adding-local-users-in-the-OpenStack-Provider.

Create an OpenStack service offering instance. See the following procedures:

Note: 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 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 any other options.

Ensure that you have defined the OpenStack Flavor service offering option and option choices in the Service Catalog for the OpenStack Provider. For more information, see Creating-options-and-option-choices-in-the-OpenStack-Provider.

An end user or a Cloud Administrator can request OpenStack cloud service offerings from the BMC Cloud Lifecycle Management – My Cloud Services Console. A Cloud Administrator determines the services for end users in the service catalog, hence an end user can request those services only.

Note: While requesting a cloud service, in the Quota details area, the available quota for the selected user is displayed (click here to see figure). If the available quota is less than the required quota, the service request fails. The end users are assigned quota by the BMC Cloud Lifecycle Management Administrators or Tenant Administrators based on the tenant quota allocated for the OpenStack Provider user accounts.

For OpenStack Provider 4.1.1 only, click here for information about requesting a service on behalf of another user.

A cloud administrator or a tenant administrator can also request an OpenStack cloud service on behalf of another user of the same tenant. See Requesting-cloud-services-on-behalf-of-another-user for details.

Note: A cloud administrator or a tenant administrator can request an OpenStack cloud service on behalf of another user of a different tenant, only if both the source and target user's tenant is mapped to the same Logical Data Center.

Note

To diagnose issues related to the OpenStack Provider, see OpenStack-Provider-issues.

Where to go from here

 

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