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
Introduction to Multi-Machine
Services 1
With the multi-machine services feature of vRealize Automation, users can provision multi-machine
services, and their component machines, in a virtual datacenter based on existing templates.
Multi-machine services are compound services composed of multiple machines that can be provisioned
and managed with vRealize Automation as a single entity.
For example, in a tiered application deployment, you might have multiple database servers, application
servers, and Web servers. In addition to creating blueprints for each of the server types, you can also
create a multi-machine blueprint that includes all of the machines needed for the entire application
deployment. Users can then provision the multi-machine service and perform actions, such as rebooting,
on all of the component machines with a single action.
This chapter includes the following topics:
n
Multi-Machine Service Concepts
n
Multi-Machine Service Life Cycle
n
Comparing Multi-Machine Services and vApps
n
Configuring IaaS for Multi-Machine Services Checklist
Multi-Machine Service Concepts
Multi-machine services are containers for their component machines. Component machines can be
virtual, physical, or cloud, or any combination of the three.
The following characteristics describe multi-machine services in vRealize Automation:
n
They are defined by a blueprint that references one or more component blueprints.
n
They can have a lease duration associated with them.
n
They are not counted as a machine in reports or licensing but their component machines are counted.
n
Requests can be made subject to approval.
n
Many machine operations, such as reboot, can be performed on the multi-machine service as a
whole. The requested action is performed on all of the components in the service.
Some blueprint types, such as vCloud Director blueprints, cannot be added as components of a multi-
machine blueprint.
VMware, Inc.
8