
Hybrid Cloud Application Architecture
F5
®
Deployment Guide 10
◆ One connected to vNetwork Distributed Switch dvPort
Group. In our example, we created a Provider vDC level
External Network connected to an external network
which is backed by a dvPort Group for access to and
from the application environment. We labeled this
red_private. This network is connected to the vSphere
network labeled dvPG_vm_vcloud_private_external.
• One Provider vCloud Network Pool:
◆ A network pool of type VCD Cloud Network Isolation.
In our example, we assigned this network a VLAN ID of
1058 and attached it to the dvSW-priv-01. WE labeled
this network pool as
blue_vCNI_dvPG_vm_vcloud_private_internal.
3. Datastores need to be provisioned for the vCloud Director.
Configuring the vSphere and physical networks
Use the following guidance for configuring the vSphere and physical
network devices:
◆ vNetwork Distributed Switches for ESX/ESXi networking.
◆ The following tasks are per vCloud Director site:
1. Provision VLANs and IP subnets as needed.
2. Configure Ethernet switching:
a) Interconnect external VLANs with LANForge (if using WAN
emulation) and ESX/ESXi hosts.
b) Interconnect all management interfaces
3. Install the two vSphere vCenter servers at Version 4.0 U1 or higher
Note: If using a Service Provider, only one is necessary.
Configuring security
Use the following guidance for configuring security:
◆ Install vShield managers for each site and configure ESX/ESXi
networking as per the vCloud Director documentation- vShield manager
configuration only needs an IP address and DNS resolver configured. All
other configuration is done automatically using reverse DNS and vCloud
Director.
Configuring the vCloud Director
In this section, we configure the vCloud Director. You must have
administrative access to complete these tasks.
Commenti su questo manuale