6.2

Figure 1‑3. Master workflow states for machine lease expiration
Figure 1‑4. Master workflow states for disposing a machine
Table 1‑1. Customizable State Change Workflows
Master Workflow State Customizable Workflow Name Extensibility Examples
BuildingMachine WFStubBuildingMachine Prepare for the machine to be created on the hypervisor.Create a
configuration management database (CMDB) record, call out to
an external system to assign an IP address to a machine, and
then during machine disposal, use WFStubMachineDisposing to
return the IP address to the pool.
RegisterMachine WFStubMachineRegistered Add an imported machine to an application provisioning tool to
receive updates and undergo compliance checks.
MachineProvisioned WFStubMachineProvisioned The machine exists on the hypervisor, and any additional
customizations are completed at this point, for example guest
agent customizations. Use this workflow stub to update a
configuration management database (CMDB) record with DCHP
IP address and storage information. Customizations made by
using the WFStubMachineProvisioned are typically reversed by
using WFStubUnprovisionMachine.
Expired WFStubMachineExpired Move an expired machine to low cost storage to reduce archival
costs and update the CMDB record and billing system to reflect
storage and cost changes.
UnprovisionMachine WFStubUnprovisionMachine Remove machines from active directory accounts.
Customizations made by using the WFStubMachineProvisioned
are typically reversed by using WFStubUnprovisionMachine.
Disposing WFStubMachineDisposing Return IP addresses to the pool.
Choosing a Lifecycle Extensibility Scenario
You can use vRealize Orchestrator or vRealize Automation Designer to extend machine lifecycles.
You can extend machine lifecycles by using vRealize Automation Designer to call out to
vRealize Orchestrator, or by using vRealize Orchestrator directly. Both approaches allow you to inject
custom logic into predetermined stages of the IaaS machine lifecycle by creating custom
vRealize Orchestrator workflows and then insert the custom workflows into the state change workflow
stubs. However, you can only restrict custom state change logics to particular blueprints if you are using
vRealize Orchestrator directly, and you can only restrict the execution of workflows to specific Distributed
Execution Managers by vRealize Automation Designer.
Machine Extensibility
VMware, Inc. 9