7.3

Working with Provisioning and Life Cycle Workflow Subscriptions
You create provisioning and life cycle workow subscriptions so that you can use vRealize Orchestrator to
extend your management of IaaS machines. The provisioning subscriptions extend what you can do during
the provisioning process. The life cycle subscriptions extend what you can do when the user is managing the
provisioned items.
IaaS Service Integration
You create a workow subscription based on a provisioning or life cycle event topic that runs a custom
vRealize Orchestrator workow based on a message generated by the IaaS service. vRealize Automation
includes two event topics that you can use for IaaS integration.
n
Machine provisioning. Create workow subscriptions that run workows during the provisioning and
disposal of IaaS machines.
n
Machine lifecycle. Create workow subscriptions that run workows related to management actions
that an owning user runs on the provisioned machine.
Configuring vRealize Orchestrator Workflows for Provisioning and Life Cycle
Workflows
You must congure your vRealize Orchestrator workows to support the IaaS service message.
Provisioning and Life Cycle Event Topic Schema
The machine provisioning and machine life cycle event topics use the same life cycle schema. The
dierences are in the triggering states. Machine provisioning receives messages based on provisioning states
and events, and machine life cycle receives messages based on active states and events. Some provisioning
states include BuildingMachine and Disposing. Some life cycle states include InstallTools and O.
The event message is the event data payload. The following is the structure of the event data payload.
{
machine : {
id : STRING, /* IaaS machine ID */
name : STRING, /* machine name */
externalReference : STRING, /* machine ID on the hypervisor */
owner : STRING, /* machine owner */
type : INTEGER, /* machine type: 0 - virtual machine; 1 - physical
machine; 2 - cloud machine */
properties : Properties /* machine properties, see notes below how to expose
virtual machine properties */
},
blueprintName : STRING, /* blueprint name */
componentId : STRING, /* component id */
componentTypeId : STRING, /* component type id */
endpointId : STRING, /* endpoint id */
requestId : STRING, /* request id */
lifecycleState : { /* see Life Cycle State
Definitions*/
state : STRING,
phase : STRING,
event : STRING
},
virtualMachineEvent : STRING, /* fire an event on that machine - only
processed by Manager Service as consumer */
workflowNextState : STRING, /* force the workflow to a specific state -
Chapter 1 Life Cycle Extensibility
VMware, Inc. 21