7.4

Each message contains a lifecycleState element that is based on the IaaS machine state changes.
The element has the following structure in the message.
lifecycleState : {
state : STRING,
phase : STRING,
event : STRING
}
Table 1‑12. LifecycleState Elements
Property Description Format and Values Examples
state Contains workflow
name and state name.
{workflowName}.{stateName}
n
VMPSMasterWorkflow32.Requested
n
VMPSMasterWorkflow32.MachineActivated
n
BasicVmWorkflow.BuildComplete
phase Contains the phase that
triggered a message.
PRE, POST, EVENT
n
PRE. An event is published when entering
this state.
n
POST. An event is published when exiting
this state.
n
EVENT. An event is published when an
IaaS event is received in this state..
event Contains the event.
This property is optional
and exists only when
the phase is EVENT.
{workflowName}.{stateName}.EVENT.
{eventName}
n
VMPSMasterWorkflow32.Requested.EVEN
T.OnProvisionMachine
n
VMPSMasterWorkflow32.VMPSMasterWor
kflow32.EVENT.OnBuildSuccess
n
BasicVmWorkflow.CreatingMachine.EVENT
.OnCreatingMachineComplete
VMPS Master Workflow Life Cycle States
The VMPS master workflow life cycle states represent an IaaS virtual machine life cycle, from request to
destruction .You can use the VMPS master workflow states and events when you create triggering
conditions based on life cycle state events and life cycle state names.
Each virtual machine goes through four basic stages.
n
Request. Includes approvals.
n
Provision. Includes different provisioning types, such as create, clone, kickstart, or WIM.
n
Manage. Includes actions, such as power on, power off, or snapshot.
n
Destroy. Includes deactivating, unprovisioning, and disposing of the machine.
These basic stages are included in the master workflow. You can use the VMPSMasterWorkflow32 states
when you create conditions for the following event topics:
n
Machine life cycle
n
Machine provisioning
Life Cycle Extensibility
VMware, Inc. 25