7.0

n
Machine lifecycle. Create workflow subscriptions that run workflows 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 configure your vRealize Orchestrator workflows 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
differences 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 Off.
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 - only
processed by Manager Service as consumer */
virtualMachineAddOrUpdateProperties : Properties, /* properties on the machine to add/update - only
processed by Manager Service as consumer */
virtualMachineDeleteProperties : Properties /* properties to remove from the machine - only
processed by Manager Service as consumer */
}
The vRealize Orchestrator parameters are mapped to the event's payload by name and type.
Life Cycle Extensibility
VMware, Inc. 29