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

  1. Create services, service offerings in the Service Catalog, as described in Creating-cloud-services.

    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. 
  2. Define your OpenStack requestable offering as you would any other offering in the Service Catalog. For instructions, see Creating-a-requestable-offering-definition.

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

Create packages of requestable offerings that tenant users can access, as described in Creating-entitlement-packages.

Assign packages to tenants, as described in Selecting-tenant-entitlement-packages.

A Cloud Administrator or an end user can request OpenStack cloud service offerings from the BMC Cloud Lifecycle Management – My Cloud Services Console, based on the services available to you in the service catalog.

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.

This topic describes how to start, stop, shutdown a cloud service.

This topic describes how you can decommission a cloud service.

Note

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

Where to go from here

Managing-OpenStack-servers

 

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