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.

Defining Service Catalog entries for Amazon Web Services


This topic describes how to create a new service in the Service Catalog for Amazon Web Services (AWS). You must define a service offering that end users can choose in a service catalog when they are provisioning Amazon instances. This topic contains the following sections:

Overview

A service is the utility that an organization provides and is defined by its service offerings, requestable offerings, and service level targets. For example, you could create an AWS service which includes service offerings for Amazon Machine Images (AMIs) of varying sizes (small, medium, large, for example). The customer could choose the size of the instance when requesting the service.

In the Service Catalog, a service must have at least one service offering and can have one or more requestable offerings. When you create a service, it is saved to BMC.ASSET dataset.

You can also create options and option choices that you can use to build your service offerings. 

To create a service

  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. In the Service Catalog, click Create a New Service servicecatalog_newservice_button.png. The New Service panel is displayed.
    New_service_AWS.gif
  3. Enter the service name.
  4. For Type, select a service type.
    • Business service - Shows the customer view of services, such as email or an online store.
    • Technical service - Supporting IT and infrastructure resources required to support business services that are not visible to customers, such as servers, applications, and network CIs.
  5. Enter a description of the service.
  6. Do one of the following:

    • To create the service offering, click Apply.
    • To create the service offering later, click Save to save your selections and close the window.

To configure options for service offerings

The following sections discuss creating options for service offerings, in an AWS environment.

Default options and option choices for AWS

BMC Cloud Lifecycle Management provides some default options and option choices that you can use when creating your service offering for AWS. The default options are:

Option

Option choices

Notes

Add Disk

5 GB

Available only as a post-deploy action.

Note

When adding option choices for additional system disks, specify only whole numbers as values. Decimal values are rounded off to the nearest whole number. For example, a value of 1.5 GB is converted to 2.0 GB.

Add Server

  • 1 server
  • 2 server

Available only as a post-deploy action.

AMI Instance Type

  • Micro
  • Small
  • Medium
  • Large

Available for any request type.

CPU

  • 1 CPU
  • 2 CPU
  • 4 CPU

Available for any request type.

Memory

  • 1 GB RAM
  • 2 GB RAM
  • 4 GB RAM
  • 8 GB RAM

Available for any request type.

You can edit any of the above options and option choices, add more choices to the options, or create your own, as described below.

Note

For detailed information about creating options and option choices in BMC Cloud Lifecycle Management, see Configuring-end-user-Option-Choices-in-service-blueprints.

Creating and configuring custom options for service offerings

  1. Open the Options Editor from one of the following locations:
    • On the Service Catalog page, click Options Editor OptionsEditorIcon2.gif.
    • On the Options tab if you are creating or modifying a service offering, click Options Editor
  2. In the Options area, click New Option .
  3. In the New Option window, enter a name and description for the option. 
  4. From the Option Type list, select one of the following:
    • Select Request Definition (a Deployment Requestable Offering or DRO). 
      This feature enables end users to change the options on Day 1 of a deployment (when they request the service). For example, you could create a Request Definition that would install a specific software package as part of the deployment.
    • Select Post-Deploy Action (Transaction Requestable Offering or TRO). 
      This feature enables end users to change the options on Day 2 of a deployment (after provisioning). For example, you could create a memory option with three different options choices - 4GB as the pre-selected default and two other choices (8GB or 16GB). The end-user could then increase or decrease the amount of allocated CPU after the service is provisioned. In this example, we chose Post-Deploy Action, which makes the option available to end-users after the instance is provisioned.
    • The following example creates an option for an additional system disk as a post-deploy action.
      New option Additional Disk.gif
  5. (Optional) Click Set Icon to upload an image (.jpeg, .png, or .gif format) that represents the option.
  6. Click OK
    The new option is listed in the Options Editor. 
  7. In the Option Choices area, click New Option Choice servicecatalog_newservice_button.png
  8. In the New Option Choice window, enter a name and description for the option choice. 
    In this example, the option is Additional disk and the option choice is 100 GB.
     

    Note

    When adding option choices for additional system disks, specify only whole numbers as values. Decimal values are rounded off to the nearest whole number. For example, a value of 1.5 GB is converted to 2.0 GB.

  9. Click OK.
    The new option choice is listed. If required, you can add more option choices.
    New option choice 100 GB.gif
  10. Click OK to save your changes, and then close the Options Editor. 
  11. The Service Catalog workspace is displayed.

For more information about options and option choices see, Service Catalog options and option choices.

Where to go from here

After creating a service and defining options, define a service offering for Amazon Web Services.

 

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