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
Create a vSphere Endpoint for Networking and Security Virtualization
An IaaS administrator creates an instance of a vSphere endpoint to allow vRealize Automation to
interact with a vCloud Networking and Security or NSX instance.
n
Run the Enable Security Policy Support for Overlapping Subnets Workflow in vRealize Orchestrator
Before you use the NSX security policy features from vRealize Automation, an administrator must
run the Enable security policy support for overlapping subnets workflow in vRealize Orchestrator.
n
Creating a Network Profile
A fabric administrator creates external network profiles and templates for network address
translation (NAT), routed, and private network profiles.
n
Configuring a Reservation for Network and Security Virtualization
An IaaS administrator can use a reservation to assign external networks and routed gateways to
network profiles for basic and multi-machine networks, specify the transport zone, and assign
security groups to multi-machine components.
Configuring vRealize Orchestrator Endpoints
If you are using vRealize Automation workflows to call vRealize Orchestrator workflows, you must
configure the vRealize Orchestrator instance or server as an endpoint.
You can associate a vRealize Orchestrator endpoint with a multi-machine blueprint to make sure that all
of the vRealize Orchestrator workflows for machines provisioned from that blueprint are run using that
endpoint.
vRealize Automation by default includes an embedded vRealize Orchestrator instance. It is
recommended that you use this as your vRealize Orchestrator endpoint for running vRealize Automation
workflows in a test environment or creating a proof of concept . For more information about managing the
embedded vRealize Orchestrator instance, see Advanced Service Design.
You can also install a plug-in on an external vRealize Orchestrator server.
It is recommended that you use this vRealize Orchestrator endpoint for running vRealize Automation
workflows in a production environment.
To install the plug-in, see the README available with the plug-in installer file from the VMware product
download site at http://vmware.com/web/vmware/downloads under the vCloud Networking and Security
or NSX links.
Create a vRealize Orchestrator Endpoint
vRealize Automation uses vRealize Orchestrator endpoints to run network and security-related workflows.
You can configure multiple endpoints to connect to different vRealize Orchestrator servers. Each endpoint
must have a priority.
When executing vRealize Orchestrator workflows, vRealize Automation tries the highest priority
vRealize Orchestrator endpoint first. If that endpoint is not reachable, then it proceeds to try the next
highest priority endpoint until a vRealize Orchestrator server is available to run the workflow.
IaaS Integration for Multi-Machine Services
VMware, Inc. 13