6.2
Table Of Contents
- IaaS Integration for Multi-Machine Services
- Contents
- IaaS Integration for Multi-Machine Services
- Introduction to Multi-Machine Services
- Configuring Network and Security Integration
- Configuring vRealize Orchestrator Endpoints
- Create a vSphere Endpoint for Networking and Security Virtualization
- Run the Enable Security Policy Support for Overlapping Subnets Workflow in vRealize Orchestrator
- Creating a Network Profile
- Configuring a Reservation for Network and Security Virtualization
- Optional Configurations for Multi-Machine Services
- Creating Multi-Machine Blueprints
- Specifying Scripts for Multi-Machine Service Provisioning
- Specifying Custom Properties for Multi-Machine Services
- Blueprint Action Settings for Multi-Machine Services
- Create a Multi-Machine Blueprint
- Specify Blueprint Information for a Multi-Machine Blueprint
- Specify Build Information for a Multi-Machine Blueprint
- Specify Network Information for a Multi-Machine Blueprint
- Specify Scripting Information for a Multi-Machine Blueprint
- Add Multi-Machine Blueprint Custom Properties
- Specify Actions for Multi-Machine Blueprints
- Publish a Blueprint
- Configuring Multi-Machine Blueprints for Network and Security Virtualization
- Managing Multi-Machine Services
n
DataContext
The following PowerShell script is provided as a sample:
# Script to Test InvokePowerShell functions
$VirtualMachine.Notes = "Test";
foreach ($i in $VirtualMachineProperties)
{
$i.PropertyValue = $i.PropertyName;
}
A PowerShell script can modify some VirtualMachine fields and property values. Not all
VirtualMachine parameter fields can be modified.
For related information, see Import Custom PowerShell Scripts in IaaS Configuration for Physical
Machines.
Table 4‑1. Script Execution Stages in the Multi-Machine Life Cycle
Stage Description
Pre-provisioning Runs after all necessary approvals are complete, but before provisioning any machines.
Post-provisioning Runs after all component machines are provisioned and powered on.
Pre-startup Runs before powering on the multi-machine service and all its component machines.
Post-startup Runs immediately after powering on the multi-machine service and all its component machines. The multi-
machine service state is set to On after the post-startup scripts run.
Pre-shutdown Runs immediately before powering off the multi-machine service and its component machines.
Post-shutdown Runs after powering off the multi-machine service and its component machines. The multi-machine
service state is set to Off after the post-shutdown scripts execute.
Provisioning scripts are run only during the initial provisioning of a multi-machine service. The startup and
shutdown scripts are run every time the multi-machine service is powered on or off, except for when the
service is initially powered on during provisioning. The pre-provisioning and post-provisioning scripts must
include everything that you want to run before and after the initial power on action.
You can also run workflows during the various stages of the multi-machine life cycle. The workflows must
accept an argument named MasterMachine of type VirtualMachine
(DynamicOps.ManagementModel.VirtualMachine). The Components property of MasterMachine is a list
of AppServiceComponents, each of which represents a component machine of the multi-machine service.
Scripts or workflows must be installed in the Model Manager before you can use them in a multi-machine
blueprint.
Specifying Custom Properties for Multi-Machine Services
Tenant administrators and business group managers can specify custom properties that apply to all
component machines in a multi-machine service in the multi-machine blueprint. When the same property
exists in more than one source, vRealize Automation follows a specific order of precedence when
applying properties to the machine.
IaaS Integration for Multi-Machine Services
VMware, Inc. 34