7.3
Table Of Contents
- Life Cycle Extensibility
- Contents
- Life Cycle Extensibility
- Machine Extensibility Overview
- Extending Machine Lifecycles By Using vRealize Orchestrator
- Configuring Workflow Subscriptions to Extend vRealize Automation
- Event Topics Provided With vRealize Automation
- Workflow Subscriptions and Event Broker Terminology
- Blockable and Replyable Event Topics
- Best Practices for Creating vRealize Orchestrator Workflows for Workflow Subscriptions
- Workflow Subscription Settings
- Working with Provisioning and Life Cycle Workflow Subscriptions
- Configuring vRealize Orchestrator Workflows for Provisioning and Life Cycle Workflows
- Workflow Subscription Life Cycle State Definitions
- Configuring the Timeout Values for States and Events
- Configuring the Error Behavior for States and Events
- Scenario: Take a Post-Provisioning Snapshot of a Virtual Machine
- Working with Approval Workflow Subscriptions
- Troubleshooting Workflow Subscriptions
- Troubleshooting vRealize Orchestrator Workflows That Do Not Start
- Troubleshooting Provisioning Requests That Take Too Much Time
- Troubleshooting a vRealize Orchestrator Workflow That Does Not Run for an Approval Request
- Troubleshooting a Rejected Approval Request That Should Be Approved
- Troubleshooting a Rejected Approval Request
- Extending Machine Life Cycles By Using vRealize Automation Designer
- Extending Machine Life Cycles By Using vRealize Automation Designer Checklist
- Installing and Configuring vRealize Automation Designer
- Customizing IaaS Workflows By Using vRealize Automation Designer
- Workflows and Distributed Execution Management
- CloudUtil Command Reference
- vRealize Automation Workflow Activity Reference
- Index
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 workows and to
create custom workows.
This chapter includes the following topics:
n
“Machine Extensibility Overview,” on page 5
n
“Extending Machine Lifecycles By Using vRealize Orchestrator,” on page 7
n
“Conguring Workow Subscriptions to Extend vRealize Automation,” on page 12
n
“Extending Machine Life Cycles By Using vRealize Automation Designer,” on page 44
n
“Workows and Distributed Execution Management,” on page 61
n
“CloudUtil Command Reference,” on page 63
n
“vRealize Automation Workow Activity Reference,” on page 74
Machine Extensibility Overview
Provisioning or decommissioning a new machine, especially for mission-critical systems, typically requires
interacting with a number of dierent 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
workows, known as workow stubs. You can use the workow stubs to call out to vRealize Orchestrator
for bi-directional integration with external management systems.
N The workow stubs are replaced by the event broker workow 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 workow subscriptions to run custom
workows based on state changes. See “Conguring Workow Subscriptions to Extend vRealize
Automation,” on page 12.
Creating a state change workow enables you to trigger the execution of a workow before the IaaS master
workow enters a specic state. For example, you can create custom workows to integrate with an external
database and record information at dierent stages of the machine life cycle.
n
Create a custom workow that runs before the master workow enters the MachineProvisioned state to
record such information as machine owner, approvers, and so on.
VMware, Inc.
5