Option Choices available when extending service blueprints
The Option Choices functionality is the same as the various sections in the service blueprint UI. For example, the Additional System Diskoption is exactly the same as configuring one or more virtual system disks (VSD) when configuring a compute resource as part of a service blueprint. (See Creating-copying-or-editing-a-service-blueprint for more information.)
The difference is that, instead of the cloud administrator specifying 100 GB of disk in the service blueprint, you use Option Choices in the Service Catalog to create end-user options for the space requirements. You now let the end-user choose how much memory they want when the Apache Server is being provisioned. With Option Choices, you do not need to edit the individual service blueprint configurations because each option can modify blueprints in a different way.
The following tables describe the available Option Choices.
This topic contains the following information:
Service Definition option choices
Function | Fulfillment type | When available? | Description |
|---|---|---|---|
Component | Software Packages |
| Modify a software package, pre-install and post-install actions, and its operations. You can enter the Component Identifier by name or select its tag group and tags. For more information, see the instructions on defining Software Packages and Operations. |
Component | Tags | Request Definition | Modify a system tag group and system tag that associates with a functional component in a service blueprint. You can enter the Component Identifier by component name, or you can select its tag group and tags, and then select the tag group and tag that the user wants to replace runtime. For example, a cloud administrator has configured a Day 2 (transaction requestable offering, TRO) action that is identified by a tag, but that tag is not part of the service blueprint. The cloud admin can provide users with a change option for a runtime component tag, and that option will change functional component tags at runtime. Then, the user can successfully deploy respective Day 2 actions without changing the service blueprint. For more information, see the instructions on defining component tags. |
Connection | Tags | Request Definition | Modify a system tag group and system tag that associates metadata with a connection in a service blueprint. You can enter the Component Identifier by name or select its tag group and tags. Modify a system tag group and system tag that associates with a connection to a functional component in a service blueprint. You can enter the Connection Identifier by connection name, or you can select its tag group and tags, and then select the tag group and tag that the user wants to replace runtime. For more information about defining connections, see Creating-copying-or-editing-a-service-blueprint. |
Service Definition | Tags | Request Definition | Modify a system tag and system tag group during runtime for a request definition that associates with a service blueprint. You can define the modified tag group and tag to apply. For more information, see the instructions on creating or modifying service blueprints. |
Service Definition | Parameters |
| Modify the functional model parameters (configurable options or settings, user names, passwords, or other information) specified by the package in the Service Definition. For more information, see the Configuring-service-blueprint-parameters instructions. |
Service Deployment Definition option choices
Function | Fulfillment type | When available? | Description |
|---|---|---|---|
Service Definition | Parameters |
| Modify the functional model parameters (configurable options or settings, user names, passwords, or other information) specified by the package in the Service Definition. For more information, see the Configuring-service-blueprint-parameters instructions. |
Compute Resources | CPU Count |
| Modify the number of processors associated with the Service Deployment Definition. This option modifies the CPU Count defined in the Compute Resources tab of the Blueprint Definition Editor. You can enter the Resource Set by name or select its tag group and tags. For a description of other fields used with CPU count, see Creating-copying-or-editing-a-service-blueprint. |
Compute Resources | Memory Size |
| Modify the memory size (in MB) associated with a service. This option modifies the Memory Size (MB) defined in the Compute Resources section of the Service Designer. You can enter the Resource Set by name or select its tag group and tags. For a description of other fields used with Memory Size, see Creating-copying-or-editing-a-service-blueprint. |
Not applicable | Add Server | Post-Deploy Action | Service-level modification that modifies the number of server instances. You can also modify the server username and password parameters. For more information, see Configuring-service-blueprint-parameters. |
Compute Resources | Additional System Disk |
| Add an additional disk to a compute resource with disk size (in GB). You can enter the Resource Set by name or select its tag group and tags. For a description of other fields used with additional VSDs, see Creating-copying-or-editing-a-service-blueprint. |
Compute Resources | Installable Resource | Request Definition | Modify the installable package in a service blueprint. The installable resource is a virtual machine image or template, and it can be a Virtual Guest Package (VGP) from BMC Server Automation or Amazon Machine Image (AMI) from Amazon EC2. For more information, see Creating-copying-or-editing-a-service-blueprint. |
Additional System Disk | Tags | Request Definition | Modify the tag groups and tags for a compute resource virtual system disk in a service blueprint to place virtual system disks at runtime. Disk placement is identified by the disk number or tags associated to that disk, and the user can specify the tag group and tag that the disk should associate to for final placement. You can enter the Resource Set Identifier by name or select its tag group and tags. |
Compute Resources | Tags | Request Definition | Modify the system tag groups and system tags that determine the placement of a compute resource on a virtual datastore at runtime. You can enter the Resource Set or Disk Identifier by name or select its tag group and tags.
|
Compute Resources | Custom Action |
| Modify the post-deployment actions (AO Workflow or Script) in compute resources. You can also enter the Component Identifier by name or select its tag group and tags. For a description of other compute resource fields, see Creating-copying-or-editing-a-service-blueprint. |
Compute Resources | Number of Instances | Request Definition | Modify the number of instances in compute resources. You can also enter the Resource Set by name or select its tag group and tags. For a description of other compute resource fields, see Creating-copying-or-editing-a-service-blueprint. |
PaaS Resource | Number of Instances | Request Definition | Modify the number of instances of the PaaS service being provisioned. For a description of PaaS-related resource fields, see Setting up service blueprints for PaaS. |
PaaS Resource | Custom Action | Request Definition | Modify the post-deployment actions for a PaaS resource set. You can identify the resource set by name or select its tag group and tags. For a description of PaaS-related resource fields, see Setting up service blueprints for PaaS. |
PaaS Resource Instance | Installable Resource | Request Definition | Select a different BMC Database Automation template used to define a database system. For a description of PaaS-related resource fields, see Setting up service blueprints for PaaS. |
PaaS Resource Instance | Memory Size | Request Definition | Modify the memory size (in MB) associated with an instance of a PaaS resource. This option modifies the Memory Size (MB) defined for a PaaS resource set in a blueprint definition. You can identify the resource set by name or select its tag group and tags. |
Additional NIC | Tags | Request Definition | This option allows users to select (at runtime) a network for a NIC defined in the service blueprint. In the Option Choice Blueprint Configuration Editor, provide the details for the resource set and the NIC number on which new tags will be applied, and select the new tag to be used instead of the tag from the service blueprint. For example, a resource set has two NICs: NIC0 with a Management tag and NIC1 with a Web Network tag. NIC1’s network is selected at runtime based on selecting a choice from Web Network 1, Web Network 2, and so on. For more information, see Creating-copying-or-editing-a-service-blueprint.
|
Additional NIC | Toggle Static/Dynamic | Request Definition | Modify whether the IP address used for the private network should be assigned dynamically through DHCP, or set statically in the machine configuration at the time of deployment. You can also enter the Resource Set or NIC Identifier by name or select its tag group and tags. For more information, see Creating-copying-or-editing-a-service-blueprint. |
Additional NIC | Toggle NAT Address Assignment | Request Definition | Modify if Network Address Translation (for the NIC) should be used to provide a separate IP address to access the public network (internet) at the time of deployment. You can also enter the Resource Set or NIC Identifier by name or select its tag group and tags. For more information, see Creating-copying-or-editing-a-service-blueprint. |
Additional NIC | Toggle DNS Registration Required | Request Definition | Select this option if DNS registration is required for each NIC on a deployed VM. You can then select Private IP for on-premises environments or Private IP or Public IP for off-premises environments. Note: During an upgrade, the DNS Registration Required flag is not modified in BMC Network Automation by default. If required, you must select this option manually. For more information, see Creating-copying-or-editing-a-service-blueprint. |
Additional VLB Pool | Tags | Request Definition | This option allows users to select (at runtime) a network for the VLB pool defined in the service blueprint. In the Option Choice Blueprint Configuration Editor, provide the details for the resource set and the VLB pool that need to be selected for the client network, and select the new tag to be used instead of tag in service blueprint. For example, a resource set in a service blueprint has a VLB pool with a client network tag called Customer. This tag needs to be selected at runtime based on selection choices from Customer 1, Customer 2, and so on. Create an option choice called Additional VLB Pool Tags. For this option choice, provide details about the resource set, the VLB pool to be updated with new tag, and the new tag to be applied. For more information, see Creating-copying-or-editing-a-service-blueprint . |
Additional VLB Pool | Toggle NAT Address Assignment | Request Definition | Modify if Network Address Translation (for the VLB Pool) should be used to provide a separate IP address to access the public network (internet) at the time of deployment. You can also enter the Resource Set or the VLB Pool Identifier by name or select its tag group and tags. For more information, see Creating-copying-or-editing-a-service-blueprint. |
Network Resources | Additional NIC |
| Modify additional NIC assigned either at the time of deployment or post-deployment. You can enter the Resource Set by name or select its tag group and tags. For more information, see Creating-copying-or-editing-a-service-blueprint .
When adding options for additional NICs, use different NIC numbers from the NICs in the blueprint. Using the same NIC numbers might cause the My Cloud Services console to mask other NIC options. For example, if you enter NIC 1 – Management NIC and NIC 1 – Customer NIC, when a user selects NIC 1 – Management NIC, the other NIC (NIC 1 – Customer NIC) is removed from the option list. Important: When creating post-deploy (Day 2) options, do not preselect option choices. Any preselected options are ignored. |
Network Resources | Additional VLB Pool | Request Definition | Modify additional VLB Pool assigned at the time of deployment. You can enter the Resource Set by name or select its tag group and tags. For more information, see Creating-copying-or-editing-a-service-blueprint. |
Network Resources | Additional VLB Entry | Request Definition | Modify additional VLB Pool entry assigned at the time of deployment. You can enter the Resource Set by name or select its tag group and tags. For more information, see Creating-copying-or-editing-a-service-blueprint . |
Network Resources | Remote Access Port | Request Definition | Modify the remote access port associated with the Service Deployment Definition. You can enter the Component Identifier by name or select its tag group and tags. For more information, see Creating-copying-or-editing-a-service-blueprint . |
Network Disk | Storage Size | Request Definition | Modify the minimum storage size (in GB) associated with the component requirements. For a description of other fields used with storage, see Creating-copying-or-editing-a-service-blueprint. |
Resource Set | Tags | Request Definition | Modify the system tag groups and system tags that determine the placement of a compute resource to a virtual cluster at runtime. You can enter the Resource Set by name or select its tag group and tags. For more information about resources in service blueprints, see Creating-copying-or-editing-a-service-blueprint. |
Resource Set | Custom Action | Request Definition | Modify the post-deployment actions in the resource set. You can enter the Component Identifier by name or select its tag group and tags. |
Service Deployment Definition | Tags | Request Definition | Modify the system tag groups and system tags and runtime with this option for Service Deployment Definitions. For example, you might create two deployment definitions in a blueprint, and you want users to be able to select either definition when requesting the service. For more information about service blueprint definitions, see Creating-copying-or-editing-a-service-blueprint. |
Service Deployment Definition | Parameters |
| Modify the deployment model parameters (configurable options or settings, user names, passwords, or other information) specified by the package in the Service Deployment Definition at post-deployment. For a description of fields used with Service Deployment Definition parameters, see To edit package installation parameters. |
Service Deployment Definition | Custom Action | Request Definition | Modify the post-deployment actions in the Service Deployment Definition. For more information, see Creating-copying-or-editing-a-service-blueprint. |
Service Deployment Definition | Network Path | Request Definition | Modify the network path settings (ad hoc or pending) in the Service Deployment Definition at the time of deployment. For more information, see Creating-copying-or-editing-a-service-blueprint. |
Service Deployment Definition | Monitoring |
| Service-level modification that enables service monitoring as a part of a service request or as a post deployment action. For more information, see Managing-servers-in-a-service, Managing-cloud-resources, and Enabling-resource-monitoring-for-end-users. |
