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
These concepts apply to multi-machine services in vRealize Automation.
Component Blueprint
A machine blueprint that is part of a multi-machine service. A component
blueprint is referenced by a multi-machine blueprint. You can also use it to
request standalone machines that are not part of a multi-machine service.
Component Machine
A machine that is managed as part of a multi-machine service. A multi-
machine service might include several component machines.
Multi-machine Blueprint
A blueprint that defines a multi-machine service.
Multi-machine Service
A compound service composed of multiple machines that
vRealize Automation can provision and manage as a single entity.
For more information about the core concepts, see Foundations and Concepts.
Multi-Machine Service Life Cycle
Multi-machine services follow the same general life cycle as individual machines, from requesting and
provisioning through managing and decommissioning.
A multi-machine blueprint contains references to blueprints for the component machines. For each
component blueprint, it specifies the minimum and maximum number of machines for the multi-machine
service.
A multi-machine blueprint can specify scripts, or workflows, to run during the provisioning process or
when powering the multi-machine service on or off. Distributed Execution Manager worker services or
agents, not the component machines, run the scripts.
When users request a multi-machine service, they can specify the following settings:
n
How many component machines to provision, based on limits specified in the multi-machine blueprint
n
Specifications for the component machines, such as CPU, memory, and storage, based on the
individual component blueprints
n
General settings, such as lease duration and custom properties, to be applied to component
machines in the multi-machine service
Before provisioning the multi-machine service, vRealize Automation allocates resources for all of the
component machines. If the multi-machine service causes a reservation to become over-allocated, its
provisioning fails. After the resources are allocated, the component machines are provisioned and
powered on.
After the multi-machine service is provisioned, the machine owner can perform machine menu tasks on
the multi-machine service as a whole, such as powering the multi-machine service off and on, or
destroying the multi-machine service and its component machines.
If the multi-machine blueprint allows for a varying number of machines for any component type, the
machine owner can add or delete machines from the multi-machine service after it is provisioned.
IaaS Integration for Multi-Machine Services
VMware, Inc. 9