7.4
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
Creating a state change workflow enables you to trigger the execution of a workflow before the IaaS
master workflow enters a specific state. For example, you can create custom workflows to integrate with
an external database and record information at different stages of the machine life cycle.
n
Create a custom workflow that runs before the master workflow enters the MachineProvisioned state
to record such information as machine owner, approvers, and so on.
n
Create a custom workflow that runs before a machine enters the MachineDisposing state to record
the time at which the machine was destroyed and data such as its resource utilization at last data
collection, last logon, and so on.
The master workflow illustrations show the main states of the master workflow, highlighting in yellow the
states you can customize by using IaaS workflow stubs. The Customizable State Change Workflows table
lists the workflow stubs available, their corresponding place in the master workflow state, and examples
of custom logic you could use at each state to extend the machine life cycle.
Figure 1‑1. Master workflow states for provisioning machines
Figure 1‑2. Master workflow states for importing machines
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.
Life Cycle Extensibility
VMware, Inc. 5