Creating a requestable offering

A requestable offering is the part of a service that end users can see and request. Like a service offering, it combines a service (utility) and a service level target (warranty). But unlike with a service offering, end users can select a requestable offering. BMC Cloud Lifecycle Management includes the following types of requestable offerings:

• 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 be added to packages.
• Post-deploy action — Represents an action an end user can take on a service instance after it has been provisioned. For example, after a LAMP stack 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. Certain restrictions apply to post-deploy actions depending on your operating system.

You can create the request definition and post-deploy action with the Service Request Designer. The SR Designer options are available if you click Show Advanced Features. (The functionality under Show Advanced Features might not always work as expected. Be sure to test any changes you make.) Customers familiar with Service Request Management might prefer to use SR Designer.

However, the SR Designer does not support change policy. To implement change management, you cannot use SR Designer, and you must use the Requestable Offering Definition window.

Before you begin

• Create a service with at least one service offering.
• (Optional) Define the options and option choices.

To create a request definition

1. From the Service Catalog, edit or create a service.
2. Select a service offering.
3. To use the Requestable Offering Definition window, follow these steps:
   1. 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.
      The Requestable Offering Definition window appears.
      
   2. Complete the steps described in Creating-a-requestable-offering-definition.
4. To use the Service Request Designer, follow these steps:
   1. If needed, click Show Advanced Features. (The functionality under Show Advanced Features might not always work as expected. Be sure to test any changes you make.)
   2. Click Create Request Definition with SR Designer.
       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.
      
   3. Complete the steps described in Using-the-Service-Request-Designer.
5. Click Save.
    After you create a request definition, its status is Online.

To modify a request definition

1. Select a service offering.
2. Click Edit the Request Definition Action.
3. For advanced editing, select the post-deploy action, and click Edit Request Definition with SR Designer.
   The Service Request Designer appears.
4. In the Requestable Offering Definition or Service Request Designer window, click Online to change it to Offline.
5. Modify the request definition.
6. Click Offline to change it to Online.
7. Click Save.

To create a post-deploy action

1. From the Service Catalog, edit or create a service.
2. Select a service offering.
3. To use the Requestable Offering Definition window, follow these steps:
   1. Click Create Post-Deploy Action.
      The Requestable Offering Definition window appears.
      
   2. Complete the steps described in Creating-a-requestable-offering-definition.
4. To use the Service Request Designer, follow these steps:
   1. If needed, click Show Advanced Features. (The functionality under Show Advanced Features might not always work as expected. Be sure to test any changes you make.)
   2. Click Create Post-Deploy Action with SR Designer.
      
   3. Complete the steps described in Using-the-Service-Request-Designer.
5. After creating a post-deploy action, you can associate options with it.
   1. Within a service offering, select a post-deploy action.
       The General Information and Options tabs display information for the post-deploy action.
   2. In the Options tab, add options to the service offering.
      • You can only select options whose Type is set to Any or Transactional.
      • The choices for the selected option appear in the Option Choice table.
      • The new category is listed with the selected option. If you delete a category, the option is not removed.
      • If a category is empty, it is deleted.
6. Click Save.

To modify a post-deploy action

1. If updating CPU or memory and the impacted operating system does not have hotplug capability, power down the system.
2. Select a service offering.
3. Select a post-deploy action.
4. Click Edit the Post-Deploy Action.
5. For advanced editing, select the post-deploy action, and click Edit Post-Deploy Action with SR Designer.
   The Service Request Designer appears.
6. In the Requestable Offering Definition or Service Request Designer window, click Online to change it to Offline.
7. Modify the post-deploy action.
8. Click Offline to change it to Online.
9. Click Save.
10. Reboot the operating system if you shut it down in step 1.

Related topics

Creating-new-services-for-the-Service-Catalog
Creating-a-service-offering
Defining-options-for-the-Service-Catalog
Configuring-Change-Management-integration