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
Creating Multi-Machine
Blueprints 4
Machine blueprints determine a machine's attributes, the manner in which it is provisioned, and its policy
and management settings.
A tenant administrator or business group manager allows users to provision multi-machine services by
creating one or more entitled multi-machine blueprints. Before you create a multi-machine blueprint, you
must first create blueprints for each of the component machines to include in the multi-machine service. A
multi-machine blueprint contains references to component blueprints. The component blueprints must be
available to the same business groups as the multi-machine blueprint.
A multi-machine blueprint includes information that applies only to a multi-machine service as a whole.
Configuration options, such as a reservation policy, apply only to component machines.
For information about what you can edit in multi-machine blueprints, and their component blueprints, see
Editing Multi-Machine Blueprints.
This chapter includes the following topics:
n
Specifying Scripts for Multi-Machine Service Provisioning
n
Specifying Custom Properties for Multi-Machine Services
n
Blueprint Action Settings for Multi-Machine Services
n
Create a Multi-Machine Blueprint
n
Publish a Blueprint
Specifying Scripts for Multi-Machine Service Provisioning
You can designate scripts or workflows to run at specific points during the multi-machine service life cycle.
Scripts are run on the Distributed Execution Manager worker machine, not on the guest operating system
of the component machine.
For information about how to specify custom logic to run at each stage, see Specify Scripting Information
for a Multi-Machine Blueprint.
PowerShell scripts can use the following parameters:
n
VirtualMachine
n
VirtualMachineProperties
VMware, Inc.
33