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 Service Request 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 Service Request Designer.

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

This topic consists of the following sections:

The following BMC Communities video (9:14) discusses end-to-end configurations and the implementation of a common requestable offering using a single service offering and single service blueprint for hybrid cloud scenarios.

https://youtu.be/71-6n-S6VSs

See also the following BMC Communities video:

 Creating a New Service Offering Quickly (7:02): https://youtu.be/-scSI896UJU

Before you begin

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

Note

Request definitions and post-deploy actions must have unique names across all service offerings.

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 SRD 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 automatically Online.

To edit a request definition

  1. Select a service offering.
  2. Click Edit the request definition.

    Tip

    For advanced editing, you can select the request definition, and then click Edit request definition with SRD Designer.

  3. Take the SRD offline to edit the request definition, or online so that it is visible to end-users.
    • Offline disables the SRD so that it is no longer deployed and end-users cannot access it from the Service Catalog.
    • Online redeploys the SRD and users can once again access it.

      Note

      The Offline and Online options do not appear when you create a request definition; they are only available in edit mode.

  4. Click Next.
  5. Modify the navigational category or packages that are associated with the request definition.
  6. Click Finish.
  7. To take the SRD back online, edit the request definition and click Online.

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-deployment action with SRD 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 edit a post-deploy action

Important

BMC Cloud Lifecycle Management allows you to change the CPU or memory values only if your operating system supports the hotplug capability. That is, you can change components such as CPU and memory without shutting down and rebooting the operating system.

If your operating system does not support the hotplug capability, you receive an error message. For example, the message "CPU hot plug not supported for this virtual machine" results from an attempt to change the CPU. The message "The operation is not supported on the object" results from an attempt to change the memory. The workaround is to manually shut down the impacted system before attempting to update the CPU or memory.

  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 a post-deployment 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

Service Catalog options and option choices

Determining how requestable offerings appear in My Cloud Services console

Integrating with BMC Change Management

Was this page helpful? Yes No Submitting... Thank you

Comments