7.1

Creating a vSphere Reservation for NSX Network and Security Virtualization
You can create a vSphere reservation to assign external networks and routed gateways to network proles
for networks, specify the transport zone, and assign security groups to machine components.
If you have congured VMware NSX, and installed the NSX plug-in for vRealize Automation, you can
specify NSX transport zone, Edge and routed gateway reservation policy, and app isolation seings when
you create or edit a blueprint. These seings are available on the NSX  tab on the New Blueprint
and Blueprint Properties pages.
The network and security component seings that you add to the blueprint design canvas are derived from
your NSX conguration and require that you have installed the NSX plug-in and run data collection for the
NSX inventory for vSphere clusters. Network and security components are specic to NSX and are available
for use with vSphere machine components only. For information about conguring NSX, see NSX
Administration Guide.
When vRealize Automation provisions machines with NAT or routed networking, it provisions a routed
gateway as the network router. The Edge or routed gateway is a management machine that consumes
compute resources. It also manages the network communications for the provisioned machine components.
The reservation used to provision the Edge or routed gateway determines the external network used for
NAT and routed network proles. It also determines the reservation Edge or routed gateway used to
congure routed networks. The reservation routed gateway links routed networks together with entries in
the routing table.
You can specify an Edge or routed gateway reservation policy to identify which reservations to use when
provisioning the machines using the Edge or routed gateway. By default, vRealize Automation uses the
same reservations for the routed gateway and the machine components.
You select one or more security groups in the reservation to enforce baseline security policy for all
component machines provisioned with that reservation in vRealize Automation. Every provisioned machine
is added to these specied security groups.
Successful provisioning requires the transport zone of the reservation to match the transport zone of a
machine blueprint when that blueprint denes machine networks. Similarly, provisioning a machine's
routed gateway requires that the transport zone dened in the reservation matches the transport zone
dened for the blueprint.
When you select an Edge or routed gateway and network prole on a reservation when conguring routed
networks, select the network path to be used in linking routed networks together and assign it the external
network prole used to congure the routed network prole. The list of network proles available to be
assigned to a network path is ltered to match the subnet of the network path based on the subnet mask and
primary IP address selected for the network interface.
If you want to use an Edge or routed gateway in vRealize Automation reservations, congure the routed
gateway externally in the NSX environment and then run inventory data collection. For NSX, you must have
a working NSX Edge instance before you can congure the default gateway for static routes or dynamic
routing details for an Edge services gateway or distributed router. See NSX Administration Guide.
Create a Reservation for Hyper-V, KVM, SCVMM, vSphere , or XenServer
You must allocate resources to machines by creating a reservation before members of a business group can
request machine provisioning.
Each business group must have at least one reservation for its members to provision machines of that type.
For example, a business group with a vSphere reservation, but not a KVM (RHEV) reservation, cannot
request a KVM (RHEV) virtual machine. In this example, the business group must be allocated a reservation
specically for KVM (RHEV) resources.
Chapter 3 Configuring Resources
VMware, Inc. 213