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.

Determining how requestable offerings appear in My Cloud Services console

The way a requestable offering appears in the My Cloud Services console is determined by how you create the offering. The following sections show examples of different configurations:

 For complete details about creating options, see Service Catalog options and option choices.

Listing options for a specific tier

When Day-1 options are created as a combination of multiple single options that use the same Object Identifier Name or tag, they are displayed as a generic option associated with a particular server group. 

For example, an Object Identifier (in this case, the Resource Set) is called Database Tier to represent a server group in the blueprint:

All of the choices for the option relate to the Database Tier object identifier (as shown in the Option Choice Blueprint Configuration Editor, which you can open through the Options Editor).

Then, the option is displayed under the “Database Tier” section in the requestable service in the My Cloud Services console.

Note that “None Selected” appears as the subheading for the section. If a user selects Large Deployment, “Large Deployment” becomes the subheading.

Listing options for multiple tiers

When Day-1 options are created as a combination of multiple single options that use different Object Identifier Names or tags, they are displayed as a generic option on a top level and are not associated with any particular server tier.

For example, a blueprint might have two Object Identifiers (in this case, the Resource Set): Server Group 1 and Server Group2.

The choices for the option relate to both object identifiers:

The options are listed above the “Server Group 1” and “Server Group 2” sections.

Sliders

Sliders appear for the following types of options that users can customize (if the options have the same object identifier) when they submit a request:

    • Server
    • CPU
    • RAM

For example, if a blueprint includes 2 servers, you might want to include options for 1 server and 3 servers.

To create this slider, you would create two option choices: 1 Server and 3 Servers.

Each option choice is mapped to the blueprint through Compute Resources > Number of Instances.

For the Server 1 option choice, the configuration appears as shown below:

If you have created Day-2 (TRO) options, users can customize these options after a service is provisioned:

  • CPU
  • RAM
  • Resize Disk

Drop-down lists

Drop-down lists appear in a dialog box for network interface cards (NICs) and disks. For example, the following “Hardware” section allows the user to add disks.

When the user clicks Add Disk, the Add Disk dialog box appears.

In this example, the administrator created two option choices in the Options Editor: 10 GB and 5 GB. (Note that the order of the option choices shown in the drop-down list might not follow the order defined in the Options Editor.)

Each option choice is mapped to the blueprint through Compute Resources > Additional System Disk.

For the 5 GB choice, the configuration appears as shown below:

Filters

The filters for resources listed in the My Cloud Services console are determined by the Keywords field and the Navigational Category in the requestable offering.  For example, the following request definition includes the keyword Windows.

The Navigational Category is Cloud Services:

Both of these filter options appear under the Filter section of the catalog in the My Cloud Services console. When the filters are selected, the filter names also appear in the Search field.

For more information about navigational categories, see the Completing the Description section, which describes using the Service Request Designer to create requestable offerings.

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.

Comments