Using Service Blueprints in a vCloud context
The vApp templates generated in vCloud Director serve as service blueprints for vCloud provisioning. The vApp templates are automatically imported into BMC Cloud Lifecycle Management. In other words, you do not create service blueprints for vCloud provisioning because they are automatically generated.
Only the vApp templates part of public catalogs in vCloud Director are automatically imported into BMC Cloud Lifecycle Management.
BMC Cloud Lifecycle Management does not support vApp networks; only Org VDC Networks are supported.
This topic includes the following sections:
Naming of service blueprints
Auto-generated blueprints use this naming convention: FM_Blueprintprefix_nameofimportedVapptemplate.
Same as the blueprint prefix you entered when you registered the VMware vCloud provider type.
Name of the vApp template in the vCloud Director environment.
The following example lists the blueprints derived from vApp templates:
These vCloud service blueprints support only a subset of the BMC Cloud Lifecycle Management service blueprint features. The vApp template has its own defaults that are used in the BMC Cloud Lifecycle Management context. You can override some defaults, but not all.
Comparison of vApp template defaults with service definition features
The following table contrasts the service definition feature for the service blueprint features with the vApp template counterparts. In most cases, the service definition feature is disabled and the vApp template default is used. In the following examples, you can see that the components, connections, operations, and parameters of the service definition features are disabled for the service blueprint based on the vApp template.
Service definition feature
vApp template default
Name of the disk in the virtual machine (VM). You cannot modify the value.
Not supported. You cannot add additional operations.
Not supported. You cannot add parameters.
Comparison of vApp template defaults with service deployment definition features
Under the Service Deployment Definitions tabs, you can update certain vApp template values in the Resource Sets subtab. The remaining subtabs (Parameters, Post Deployment Actions, and Network Paths) are disabled.
Allowed operations in the Resource Sets subtab
The following table contrasts the Components, Compute Resources, and Post Deployment Actions features with their vApp template counterparts:
Resource Sets feature
vApp template default
The name of the disk in the VM. You cannot change this value.
The underlying vApp template serves as the Installable Resource value. It uses the following default values, which you cannot modify:
Not supported. You cannot add post-deployment actions.
Under the Network Resources subtab, the Virtual Load Balancer Pools, the Virtual Load Balancer Pool Entries, and the Remote Access Ports subtabs are not supported.
However, you can update some options under the NIC subtab.
You can modify the Network Selection Method parameters.
Use Network Policies
Select this option to add tags to the NIC Tags field. When you select the Use Network Policies option, the Use Labels option is disabled, and you must add a NIC tag to the NIC Tags field. The selected NIC tag should match the tag assigned to the network in Logical Data Center, as defined in the corresponding policy. After updating your network selection method, the Available Network Interface Cards pane looks similar to this example:
This field is pre-filled with the Org VDC Network label defined on the template in the vCloud Director. This Org VDC Network label serves as the default. Select this option to update the label of the network identifier. The label should match the label assigned to the network in the Logical Data Center.
In addition to updating the network selection methods, you can choose a dynamic or static IP selection whether you have chosen to use NIC tags or a network label. If you modify the IP selection of the default label, you override the IP selection on the Org VDC Network. If you change the IP selection, be sure all impacted networks support the specified static or dynamic IP address.
The Assign NAT Address and NIC Number fields are disabled for vApp template-based service blueprints.
Where to go from here
After viewing or updating data in the vCloud Service Blueprint, you can proceed to define Service Catalog entries.