7.3

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 workow
name and state name.
{workowName}.{stateName}
n
VMPSMasterWorkow32.Requested
n
VMPSMasterWorkow32.MachineActiv
ated
n
BasicVmWorkow.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.
{workowName}.
{stateName}.EVENT.{eventName}
n
VMPSMasterWorkow32.Requested.EV
ENT.OnProvisionMachine
n
VMPSMasterWorkow32.VMPSMaster
Workow32.EVENT.OnBuildSuccess
n
BasicVmWorkow.CreatingMachine.EV
ENT.OnCreatingMachineComplete
VMPS Master Workflow Life Cycle States
The VMPS master workow life cycle states represent an IaaS virtual machine life cycle, from request to
destruction .You can use the VMPS master workow 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 dierent provisioning types, such as create, clone, kickstart, or WIM.
n
Manage. Includes actions, such as power on, power o, or snapshot.
n
Destroy. Includes deactivating, unprovisioning, and disposing of the machine.
These basic stages are included in the master workow. You can use the VMPSMasterWorkow32 states
when you create conditions for the following event topics:
n
Machine life cycle
n
Machine provisioning
The global event states are messages sent to the event broker by the VMPS Master Workow. Global events
can be triggered at any time.
Chapter 1 Life Cycle Extensibility
VMware, Inc. 23