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
n
Create a custom workow 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 workow illustrations show the main states of the master workow, highlighting in yellow the
states you can customize by using IaaS workow stubs. The Customizable State Change Workows table
lists the workow stubs available, their corresponding place in the master workow 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 conguration 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 workow stub to
update a conguration management database (CMDB)
record with DCHP IP address and storage information.
Customizations made by using the
WFStubMachineProvisioned are typically reversed by using
WFStubUnprovisionMachine.
Expired WFStubMachineExpired Move an expired machine to low cost storage to reduce
archival costs and update the CMDB record and billing
system to reect storage and cost changes.
UnprovisionMachine WFStubUnprovisionMachine Remove machines from active directory accounts.
Customizations made by using the
WFStubMachineProvisioned are typically reversed by using
WFStubUnprovisionMachine.
Disposing WFStubMachineDisposing Return IP addresses to the pool.
Life Cycle Extensibility
6 VMware, Inc.