Configuring end-user Option Choices in service blueprints
Based on the type of option that you choose, cloud administrators can configure options to be processed at different stages of the service offering.
For example, if you select the Request Definition type, end-users can specify the amount of RAM to deploy in the Apache Server (0 GB, 4 GB, or 8 GB) when the offering is provisioned.
Note
Services in the cloud are implemented in three stages, or "days" (as they are commonly described):
- Day 0 — Set up the service offering in the the cloud environment.
- Day 1 — While the cloud environment is running, end-users make their initial request of services in the cloud environment. At request time, the service is provisioned.
- Day 2 — End-users make additional requests of the service in the future.
This topic includes the following sections:
The following BMC Communities video (5:26) describes how to configure option choices, use tag groups and tags, and configure policies in BMC Cloud Lifecycle Management to ensure that network containers are placed correctly in an environment.
The following video (4:50) describes how options work with change approval using BMC Change Management in BMC Cloud Lifecycle Management.
Option types
The following option types are available:
- Request Definition (Delivery Requestable Offering or DRO) — You can specify which options that end-users can change during the provisioning of the offering. For example, the cloud administrator configures the service offering so that end-users can add 0 GB, 4 GB, or 8GB of memory to their Apache Server when they first provision the system.
With a Request Definition, you have a wide choice of possible options on Day 1 of a deployment (for example, during the initial request when a VM is initially provisioned).
Post-Deploy Action (Transaction Requestable Offering or TRO) — You can specify which options that end-users can change on Day 2 of a deployment (to existing services). You configure the service offering so that end-users can only add memory to their Apache Server after the system is provisioned.
With a Post-Deploy Action, your options are somewhat limited. You only have eight options you can select, for example, Software Packages or Parameters on Day 2 of a deployment (for example, after the VM is provisioned).
After you provision a server, open the BMC My Cloud Services console, and open the Configuration page for your server, and make the necessary change. For more information, see Managing servers in a service.Note
End users have the ability to add multiple post-deployment options at once. Post-deployment actions that modify a server configuration, such as adding CPU and memory, can be combined in a single transaction only if hotswap is enabled on the VM to be modified. Otherwise, at least one option will fail to complete because the server will restart after the first option has completed.
- Any Request — You can specify which options that end-users can change on Day 1 or Day 2 of deployment. For example, you configure the service offering so that end-users can add 4 GB of memory to their Apache Server when they first provision the system at request time. But if they change their minds later, they can open the service request and then decrease or increase the memory.
For a complete list of option types and when they are available, see Option Choices available when extending service blueprints.
Before you begin
- Review creating service blueprints.
- Review creating service offerings.
- Review Service Catalog options and option choices.
Comments
Log in or register to comment.