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
The machine owner can view the components that make up a multi-machine service and manage them
as a group or individually. Most machine operations are available for individual component machines,
except for changing the owner or lease.
These operations are inclusive to the multi-machine service and modify the group as a whole. Conversely,
some actions are inclusive to the individual components, such as suspending, redeploying, and
connecting using Microsoft Remote Desktop Protocol or VMware Remote Console.
Comparing Multi-Machine Services and vApps
You can use vRealize Automation multi-machine services or vApps to group component machines.
Table 1‑1. Comparison of Multi-Machine Service and vApp (vCloud) Features
vRealize Automation Multi-Machine Service vApp (vCloud)
Create a multi-machine blueprint that references individual
machine blueprints in vRealize Automation.
Use existing vApp templates created in vCloud Director or
vCloud Air.
Provision machines of any type (virtual, physical, or cloud) as
part of a service.
Provision virtual machines from vCloud Director or vCloud Air.
Use vRealize Automation to manage component machines of a
multi-machine service.
Use vCloud Director or vCloud Air to manage vApp machines.
Application-specific networks can be defined in a multi-machine
blueprint for vCloud Networking and Security and NSX.
Application-specific networks are defined in a vApp.
Component machines can be added or removed after initial
provisioning.
Component machines cannot be added or removed after initial
provisioning.
vRealize Automation defines startup and shutdown order. The vApp template defines startup and shutdown order.
For both, access to the component portal for Microsoft Remote Desktop Protocol, Virtual Network
Computing, and SSH depends on the guest and console and the endpoint.
Configuring IaaS for Multi-Machine Services Checklist
IaaS administrators, tenant administrators or business group managers, and fabric administrators perform
required and optional configurations to implement multi-machine services in vRealize Automation.
For information about how to create the necessary network profiles, fabric groups, business groups,
reservation policies, and machine endpoints, see the following documents:
n
IaaS Configuration for Virtual Platforms
n
IaaS Configuration for Cloud Platforms
n
IaaS Configuration for Physical Machines
The following high-level checklist shows the tasks required to integrate multi-machine services into an
existing vRealize Automation deployment.
IaaS Integration for Multi-Machine Services
VMware, Inc. 10