6.2

Extending Machine Lifecycles
By Using vRealize Automation
Designer 3
You can inject custom logic into predetermined stages of the IaaS machine life cycle by using vRealize
Automation Designer to directly edit the state change workflow stubs and, optionally, call out to custom
vRealize Orchestrator workflows.
This chapter includes the following topics:
n
Extending Machine Lifecycles By Using vRealize Automation Designer Checklist
n
Installing and Configuring vRealize Automation Designer
n
Customizing IaaS Workflows By Using vRealize Automation Designer
Extending Machine Lifecycles By Using vRealize
Automation Designer Checklist
The Extending Machine Lifecycles By Using vRealize Automation Designer Checklist provides a high-
level overview of the steps required to install and configure vRealize Automation Designer to customize
IaaS machine life cycles.
Table 3‑1. Extending Machine Lifecycles By Using vRealize Automation Designer Checklist
Task Details
Download and install vRealize Automation
Designer.
Installing vRealize Automation Designer
Create a vRealize Automation endpoint for your
vRealize Orchestrator instance.
Create a vRealize Orchestrator Endpoint
Associate your vRealize Orchestrator endpoint with
a machine blueprint.
Associate a vRealize Orchestrator Endpoint with a Blueprint
Using vRealize Automation Designer activities,
customize an IaaS Workflow stub. Optionally, you can
use vRealize Orchestrator workflow activities to call
out to custom vRealize Orchestrator workflows.
Customize an IaaS Workflow
After you create a custom state change workflow, a
tenant administrator or business group manager must
enable it for specific blueprints by adding a custom
property.
Configure a Blueprint to Call a State Change Workflow
VMware, Inc. 19