
5
Infrastructure components
The following is a list of infrastructure components.
Domain Name Resolution
BIND 9
Ubuntu 8 virtual machine
Accurate Network Time NTP Server Ubuntu 8 virtual machine
Browser plug-in for admin client Adobe Flash Administrative console
What We Used: Network Connections Description
VMware
- ESX & ESXi
- vCenter
- vCloud Director
- vShield
- vMotion
A distinct network to coalesce management for infrastructure
components. This network should be composed of an assigned
VLAN and IP subnet. In testing VLAN 100 and the IP network of
10.1.100.0/255.255.252.0 was used. We label this tc_admin in
our vSphere environments.
Oracle 11gR2 database servers
F5 BIG-IP GTM Appliance management interface
F5 BIG-IP LTM Appliance management interface
LANforge management interface
Ethernet switches
VMware - vSphere (vCenter and ESX configured)
- vCloud Director network mappings at site 1 (Private cloud)
> Direct Organization Network connected to an external
network which is backed by a dvPort Group. In our testing we
used VLAN 1057 and 10.133.57.0/24 for the direct connect
external network. In VSphere, we label this network
"dvPG_vm_vcloud_private_external."
> Internal Organization vCNI network which is backed by an
vCNI Network Pool. We used VLAN 1058 and
10.133.58.0/24 for the isolated network. In vSphere, we label
this network "dvPG_vm_vcloud_private_internal."
- vCloud Director network mappings at site 2 (Public cloud)
> Internal Organization vCNI network which is backed by an
vCNI Network Pool. In our testing we used VLAN 1059 and
10.133.59.0/24 for this network. In VSphere, we label this
network "dvPG_vm_vcloud_public_external."
> Internal Organization vCNI network which is backed by an
vCNI Network Pool. In our testing we used VLAN 1060 and
10.133.60.0/24 for this network. In VSphere, we label this
network "dvPG_vm_vcloud_public_internal.
Networks for application traffic at each site:
At least two VLANs are required at each cloud site. One VLAN
and IP network tuple will be assigned for inbound traffic to the
cloud and one VLAN and IP network tuple will be assigned for
private-internal cloud application traffic.
- VLAN
- IPSubnet
A network is required for clients, and in our example for load
generation. The VLAN and IP Subnet selected must also be
made available to and configured on the LANforge. This allows
the client WAN profile to be managed and configured
independently of the WAN emulation settings used between the 2
cloud sites. In our testing we used VLAN 1061 and
10.133.61.0/24 for the client network
.
Role What we used Platform
Commenti su questo manuale