Creating the service offering for OpenStack

This topic describes how to create an OpenStack service offering instance. It includes the following sections:

• • Before you begin
  • To create the OpenStack service offering
  • To create a requestable offering definition
  • To create a post-deploy action
  • To associate options with a service offering
  • Where to go from here
  • Related topics

Before you begin

• Create services in the Service Catalog, as described in Creating-cloud-services.
• Optionally, define the options and choices that you can associate with a requestable offering.

To create the OpenStack service offering

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window, and click Service Catalog.
2. From the Service Catalog, select the service you previously created and click the Edit icon .
3. In the General Information tab, edit the default service offering:
   • Default Service Offering - Enable this option to make the selected service offering the default for the service. 
     Unless users select a different service offering, the default service offering is used. 
   • Name - A short, descriptive name for the service offering. 
   • Description - A more detailed description of the service offering. 
   • Service Blueprint  - Specify the software and hardware to associate with the service offering by selecting one of the service blueprints you created previously. 
   • Reference Definition - Specify the version of the selected service blueprint you want to use. 

1. • Definition - Specify how to deploy the selected service blueprint. 
     From the list, select a service definition that is available for the chosen service blueprint.
2. Add a Base Customer Price to define the amount charged to the customer for the service offering. 
   You can enter multiple customer prices per service. For more information, see Adding-a-customer-price-or-delivery-cost-to-an-option-service-or-request-action.
3. Add a Base Deployment Cost to define the amount that it costs to provide the service offering. 
   You can enter one deployment cost per service. For more information, see Adding-a-customer-price-or-delivery-cost-to-an-option-service-or-request-action.
4. Click Apply, which activates the Options tab.
5. Click the Options tab to add options to the service offering. 
   You can only select options whose Type is set to Any request or Request Definition. The choices for the selected option appear in the Option Choice table.
6. Click Apply to save the current settings. You can now create the requestable offering definition.

To create a requestable offering definition

The request definition describes the details of the service offering, including the name, description, and one-time delivery price (which is different from the service offering price that describes the ongoing maintenance price). The cloud administrator can define only one request definition for a particular service offering, and a request definition must be created for the service offering to be available in the BMC My Services Cloud Console. Request definitions can also be added to packages.

1. From the Service Catalog, select the service to which you want to create the request definition.
2. Click the Edit icon .
3. In the Service Offerings section, select a service offering from the left side of the section.
   
4. Click Create request definition.
   (If the service offering has an existing request definition, this option is not available because only one request definition is allowed for each service offering.)
   
   

5. In the Request Definition dialog box, complete the following fields:

   Field	Description
   Title	Enter a descriptive title for the requestable offering. This example uses Oracle Service Offering instance as the title. The customer will use this offering to request the provisioning of a OpenStack instance which is based on a general purpose OpenStack instance type.
   Description	Enter a detailed description of the requestable offering. Note Only 255 characters can be shown in the Request Entry console. Any text greater than 255 character is indicated by ellipsis points (...), although you cannot access this text in the Console.
   Keywords	Enter aliases (keywords) used to search for requestable offering in the My Cloud Services Console. Requesters can enter these keywords when they search for services in the My Cloud Services Console.
   One-time Price	Enter the actual price of this requestable service.
   Start Date	Enter the date that this requestable offering goes online. After the requestable offering is approved and deployed, it becomes available online after the date you enter here.
   Change Policy	Specify the type of Change Policy to be used, if your BMC Cloud Lifecycle Management environment has been integrated with BMC Change Management. In this example, we choose No change required, as change management is not enabled in this environment.
   Type	Select OpenStack.
   Image	Specify which image appears to users in the My Cloud Services Console.
   Approval Type	Specify the type of approval required for the service request, if your BMC Cloud Lifecycle Management environment has been integrated with BMC Change Management. This example uses None as the approval type, as change management is not enabled in this environment, and no approval chain record is associated with the service request when it is submitted.

   

    

6. Click Next.
   

1. Specify the category type that applies to the requestable offering (in this example, Cloud Services).
2. Associate one or more packages with the requestable offering. 
   Note that at least one package needs to be associated with the requestable offering
   1. To associate a package, select it from the Available Packages table, and click Add.
   2. You can also drag and drop packages from the Available Packages table to the Associated Packages table. 
      Packages that are related to the Company for this requestable offering are listed in the Available Packages table.
   3. To filter the packages listed in the Available Packages table, enter a word or string in the Search field, and press Enter.
3. Click Finish.

You can now create a post-deploy action, or associate end-user options with the requestable service offering.

To create a post-deploy action

A post-deploy action is an action an end-user can take on a service instance after it has been provisioned. For example, after an OpenStack instance has been provisioned, the user might request a different amount of memory or CPU. Post-deploy actions are not required, and the cloud administrator can create any number of post-deploy actions per service offering. 

1. From the Service Catalog, select the service to which you want to add a post-deploy action.
2. Click the Edit icon .
3. In the Service Offerings section, select a service offering from the left side of the section.
4. Click Create post-deploy action. 
   
   The Request Definition window appears.
5. Complete the steps described in To create a requestable offering definition.
6. After creating a post-deploy action, you can associate options with it, as described in the following section.
7. Click Save.

To associate options with a service offering

To enable the options to be presented to end-users, you must associate the options with a service offering request definition or post-deploy action.

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Service Catalog.
2. In the Service Catalog workspace, select the OpenStack service to which you want to associate an option. 
   This example uses the OpenStack service offering created in the previous procedure.
3. Click Edit . The Edit Service window is displayed. 
   
4. Click the Options tab. 
   The Options panel is displayed. 
5. Click the Options editor icon . 
   The Options editor is displayed

6. Select the Option and the related Option choices you want to associate with the service offering. 

   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.  

7. Click OK. 
   The options are added to the list of available options for the service offering request definition.
8. From the list under Available Options, select the options to add to this service offering and click Add. 
   Note that because you are editing the request definition for the service offering, only options whose Type is set to Any request or Request Definition. If you are editing a post-deploy action, you can only select options whose Type is set to Any or Post-Deploy Action.
9. The options that you selected appear in the list under Selected Options, and the associated option choices appear in the table at the bottom of the window. 
10. Click Apply and then click Save.

Where to go from here

Now that the service offering has been created, an administrator or end user can request an OpenStack cloud service.

Related topics

For overview information and detailed procedures related to this topic, refer to Creating-cloud-services and related subtopics.