
9
Configuring vCloud Director management
Use the following guidance for configuring vCloud Director management:
1. Install vCloud Director nodes for each site
a) Each needs at least two IP addresses - though three is preferable.
• One for Service access.
• One for vSphere proxy.
• One for management.
2. Configure vCloud Director for each site's provider resources.
a) Create a Provider vDC. In our example, we named this provider
Public_provider for the Public Cloud and Private_provider in
the Private Cloud.
b) Add the vCenter to the vCloud Director as appropriate.
c) Prepare the ESX/ESXi hosts with the vCloud Director agent.
d) Map the vCenter resources to provider-side objects in the Public
vCloud Director.
• Provider DC to resource pool.
• Two Provider level vCloud external networks:
◆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_public. This network is connected to the vSphere
network labeled dvPG_vm_vcloud_public_external.
◆One connected to a vNetwork Distributed Switch dvPort
Group. IN our example, we created another Provider
vDC level External Network which is backed by a
dvPort Group for access to the LTM-VE management
interface. We labeled this Ext_Net_to_tc_admin. This
network is connected to the vSphere network we labeled
tc_admin.
• 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
1060 and attached it to the dvSW_01. We labeled this
network pool as
blue_vCNI_dvPG_vm_vcloud_Public_internal.
e) Map the vCenter resources to provider-side objects in the Private
vCloud Director.
• One Provider level vCloud external network.
Commenti su questo manuale