7.1
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
Table 3‑1. Extending Machine Lifecycles by Using vRealize Orchestrator Checklist
(Continued)
Task Details
Use the workflow template provided in the
Extensibility subdirectory of the vRealize Automation
plug-in library to create a custom
vRealize Orchestrator workflow to run during the
machine lifecycle. You can run multiple workflows in
the same state for the same blueprint as long as you
nest them under a single wrapper workflow.
For information about developing workflows with vRealize Orchestrator,
see the vRealize Orchestrator documentation. For training in
vRealize Orchestrator development for vRealize Automation integrations,
see the training courses available from VMware Education and the
instructional material provided by VMware Learning.
Run the provided workflow that inserts your custom
workflow into an IaaS workflow stub and configures a
blueprint to call the IaaS workflow stub.
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 Chapter 4 Configuring Workflow
Subscriptions to Extend vRealize Automation.
Assign a State Change Workflow to a Blueprint and Its Virtual Machines
Configuring the vRealize Automation Plug-in for Machine
Extensibility
You configure your vRealize Automation and IaaS hosts, install the customizations for machine
extensibility, and create a vRealize Automation endpoint for your vRealize Orchestrator instance.
Add a vRealize Automation Host
You can run a workflow to add a vRealize Automation host and configure the host connection parameters.
Procedure
1 From the drop-down menu in the Orchestrator client, select Run or Design.
2 Click the Workflows view.
3 Select Library > vRealize Automation > Configuration.
4 Right-click the Add a vRA host workflow and select Start workflow.
5 Enter a unique name for the host in the Host Name text box.
6 Enter the URL address of the host in the Host URL text box.
For example: https://hostname.
Life Cycle Extensibility
VMware, Inc. 12