Physical NSX Network

For VMware Integrated OpenStack deployments based on NSX, the API access, Management, Transport, and External network each require a separate and dedicated VLAN.

Request that your network administrator prepare the necessary VLANs.

VLAN	Description
API Access network	Provides access for users to the OpenStack services through APIs or the VMware Integrated OpenStack dashboard. Trunk all hosts in the Management cluster to this VLAN. Make externally accessible. Include at least 2 contiguous IP addresses for HA deployments or 1 IP address for compact or tiny deployments.
External	Provides external user access to deployments. Trunk all hosts in the NSX Edge cluster to this VLAN.
Management network	Carries traffic among the management components. Trunk all hosts in the Management cluster to this VLAN. Trunk all hosts in the Compute cluster to this VLAN. Include at least 11 contiguous IP addresses for HA deployments or 4 contiguous IP addresses for compact or tiny deployments. An additional 5 contiguous IP addresses are required if you want to deploy Ceilometer. Enable L2 or L3 access to this VLAN for the following components: vCenter Server NSX Manager NSX Controller If you are deploying the NSX Manager and NSX Controller VMs on the Management cluster, you must trunk their hosts to the Management network.
Metadata-service	The metadata-service network enables new OpenStack deployments to access and run customization scripts made available by the Nova metadata service, which is hosted by the OpenStack controllers.
Transport	Carries traffic among the OpenStack deployments. Trunk all hosts in the Compute cluster to this VLAN. Trunk all hosts in the NSX Edge cluster to this VLAN. Important: The Maximum Transmission Unit (MTU) settings for the Transport VLAN must be configured to support 1600 bytes. See the Knowledge Base at http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2093324.

Figure 1. Network Map for NSX Deployments