7.2

Table Of Contents
Table 457. Provisioned Resource Options
Option Description
A custom resource that you previously created Select the custom resource that defines the
vRealize Orchestrator resource type required to run the
provisioning blueprint.
A provisioning blueprint runs a vRealize Orchestrator workflow
to provision resources on the target endpoint using the
vRealize Orchestrator plug-in API for the endpoint. For example,
add virtual NICs to a network device in vSphere.
You can define post-provisioning operations for this type of
provisioned resources. You can also make the blueprint
scalable, by adding or removing instances when needed.
Results
n
The blueprint is eligible to for scaling.
n
The blueprint appears in the design canvas in the category
specified for the selected custom resource.
n
The blueprint is displayed on the Items tab when you deploy
a blueprint that includes it, and you can run any actions on
the item after deployment.
No provisioning A non-provisioning blueprint runs a vRealize Orchestrator
workflow to perform a task that does not require the API to make
changes to an endpoint. For example, build a report and email
or post it to a target communication system.
Results
n
The blueprint is not eligible for scaling. You can use non-
provisioning blueprints as supporting workflows in scalable
blueprints. For example, you can create a blueprint to
update a high availability load balancer.
n
The blueprint appears in the XaaS category in the design
canvas.
n
The blueprint is not displayed on the Items tab when you
deploy a blueprint that includes it, nor can you run any
actions on the item after deployment.
Component Lifecycle Tab
The Component Lifecycle tab is available if you selected Make available as a component in the design
canvas on the General tab.
You use these options to define how this blueprint behaves post-deployment during scale-in and scale-out
operations when it is used as a component in a composite blueprint.
The availability of the different options depends on the blueprint. Not all blueprint workflows support or
require all the options. Because your XaaS might be used in a composite blueprint, you should configure
the update and destroy options, as well as allocate and decallocate, if they are available for the blueprint
so that the blueprint scales correctly.
Configuring vRealize Automation
VMware, Inc. 435