7.4

Life Cycle Extensibility 1
Using vRealize Orchestrator with vRealize Automation, you can extend how you the manage the life cycle
of IaaS machines.
Extending vRealize Automation requires you to use provided vRealize Orchestrator workflows and to
create custom workflows.
This chapter includes the following topics:
n
Machine Extensibility Overview
n
Extending Machine Lifecycles By Using vRealize Orchestrator
n
Configuring Workflow Subscriptions to Extend vRealize Automation
n
Extending Machine Life Cycles By Using vRealize Automation Designer
n
Workflows and Distributed Execution Management
n
CloudUtil Command Reference
n
vRealize Automation Workflow Activity Reference
Machine Extensibility Overview
Provisioning or decommissioning a new machine, especially for mission-critical systems, typically requires
interacting with a number of different management systems, including DNS servers, load balancers,
CMDBs, IP Address Management and other systems.
Machine Life Cycle Extensibility
You can inject custom logic at various predetermined IaaS life cycle stages by leveraging IaaS state
change workflows, known as workflow stubs. You can use the workflow stubs to call out to
vRealize Orchestrator for bi-directional integration with external management systems.
Note The workflow stubs are replaced by the event broker workflow subscriptions. They are still
available, supported, and they can be used, but expect them to be removed in a future version of
vRealize Automation. To ensure future product compatibility, you should use the workflow subscriptions to
run custom workflows based on state changes. See Configuring Workflow Subscriptions to Extend
vRealize Automation.
VMware, Inc.
4