Private Cloud With VMWARE vCloud Director (Lab Setup)

Private Cloud Lab Scenario

Following are the requirement and scenario which we need to know before start building the vCloud Environment.

Lab Environment Summary

At the time of my lab I have one giant server with 4 x 16 CPUs and 256 GB RAM. I am going to build my vCloud lab on nested virtualized environment.

I divide my lab/cloud environment into two categories.

  •  Management cluster
  • Resource/Compute cluster

Each resource cluster has his own vCenter for management. In general, it is best practice to separate the both layers (Management and Computing Resource). It simplify management and troubleshooting process. One of biggest advantage of layered approached is, if one layer suffer any kind of degradation it will not impact the other one.

LabSetup

Environment brief Summary

In my lab each server have following specs

  • 2 socket X 6 core CPU’s
  • 15 GB RAM
  • 4 X 1 GB NIC (Mgmt.)
  • 6X 1 GB NIC (RG)

I am using Standard vSwitch for my Management Cluster for ease and dvSwitch for vCloud RG Cluster because dvSwitch is the requirement for VMware vCloud Environment.

Cluster Software Storage Network Description
Management Cluster 3 X ESXi hosts (N+1 Cluster)Most Resilience 1 x NFS (500 GB) vSwitch This cluster hold the Mgmt. environment of whole vCloud
RG Cluster (Gold) 3 X ESXi hosts (N+1 Cluster)Most Resilience   2 X ISCSI (50GB) 1x NFS (50 GB) dvSwitch Most Resilient and High Computing Environment for Production Tier1 Application.
RG Cluster (Silver) 3 X ESXi hosts (N+1 Cluster)Resilience 2 X ISCSI (50GB) 1x NFS (50 GB) dvSwitch Resilient and Mid-Range Computing Environment for Production/Development Tier1/2 Application.
RG Cluster (Bronze) 2 X ESXi hosts (N+0 Cluster)Non-Resilience 2 X ISCSI (50GB) 1x NFS (50 GB) dvSwitch Non-Resilient and low range Computing Environment for RND Tier3 Application.

Management Cluster Network Design

Each management host has following network design

Cluster Virtual NICs Traffic Type VLAN (Optional)
Management Host Vmnic0 Management  
Vmnic1 VMotion  
Vmnic2 ISCSI/NFS  
Vmnic3 VMs  

 Resource Group Cluster Network Design

Each Resource group host has following network design

Cluster Virtual NICs Traffic Type VLAN (Optional)
 Resource Group Host Vmnic0 Management/Vmotion  
Vmnic1 ISCSI/NFS  
Vmnic2 Cloud External Network  
Vmnic3 Cloud VLAN-Portgroup Backed  
Vmnic4 Cloud VCD-NI-Portgroup Backed  
Vmnic5 Cloud VSphere Port Group Backed  

 Components of different layers.

Management layer

Name License Type Qty Description
ESXi (With Enterprise Plus License) vSphere Enterprise Plus 3 Used to Build the management layer for vCloud Lab
vCenter Server Standard License 2 Use for management of VCloud Mgmt and RG Cluster Environment
VCenter Update Manager (VUM) No need (Comes in VSphere Enterprise Plus) 1 Used for patching the whole cloud environment
Virtual SAN (open Filer) Free 1 provide shared storage in the vcloud
Active Directory with (DNS/DHCP) Role Windows 2008 Std R2 License. 1 Provide centralized authentication, name resolution and dynamic IP allocation in Cloud
Certificate Authority (CA) Windows 2008 Std R2 License. 1  SSL Certificate Security Server for while Cloud Lab Environment
SQL Server Enterprise License for Production but in Lab use can use express which is free 1 Hold Databases of different Cloud Components
vCloud Director (Cell) Cloud Suit Enterprise 2 For Cloud DeploymentRequired 2, if you wants Cloud in HA mode.
vCloud Network and Security (vCNS) Cover in Cloud Suit License 1 Required for vCloud director security and vCloud cells load balancing

 Resource Group Layer (Private Cloud)

Name License Type Qty Description
ESXi (With Enterprise Plus License) vSphere Enterprise Plus 8 Used to Build the different Computing Model in Cloud

 Cloud LAB inventory with IP/FQDN.

Sr # Server Name FQDN Name IP Address / Subnet
1 AD/DNS/DHCP cloud-ad.vmlab.com 192.168.150.1/255.255.255.0
2 CA Server cloud-ca.vmlab.com 192.168.150.2/255.255.255.0
3 SQL cloud-sql.vmlab.com 192.168.150.3/255.255.255.0
4 Virtual SAN cloud-vsan.vlab.com 192.168.150.4/255.255.255.0
5 VCenter Update Manager cloud-vum.vmlab.com 192.168.150.5/255.255.255.0
6 vCloud Mgmt. Server mgmt-srv.vmlab.com 192.168.150.6/255.255.255.0
7 Mgmt. VCenter vc-mgmt.vmlab.com 192.168.150.7/255.255.255.0
8 RG VCenter vc-rg.vmlab.com 192.168.150.8/255.255.255.0
9 vCloud Directory (Cell1) http cloud-cell1.vmlab.com 192.168.150.9/255.255.255.0
10 vCloud Directory (Cell1) VM Console cloud-cell1-vmrc.vmlab.com 192.168.150.10/255.255.255.0
11 vCloud Directory (Cell2) http cloud-cell2.vmlab.com 192.168.150.11/255.255.255.0
12 vCloud Directory (Cell2) VM console cloud-cell2-vmrc.vmlab.com 192.168.150.12/255.255.255.0
13 NTP Server cloud-ntp.vmlab.com 192.168.150.13/255.255.255.0
14 Syslog Server cloud-syslog.vmlab.com 192.168.150.14/255.255.255.0
15 ESXi-1 (Mgmt.) esxi-1-mgmt.vmlab.com 192.168.150.16/255.255.255.0
16 ESXi-2 (Mgmt.) esxi-2-mgmt.vmlab.com 192.168.150.17/255.255.255.0
17 ESXi-3 (Mgmt.) esxi-3-mgmt.vmlab.com 192.168.150.18/255.255.255.0
18 ESXi-1 (RG) esxi-1-rg.vmlab.com 192.168.150.19/255.255.255.0
19 ESXi-2 (RG) esxi-2-rg.vmlab.com 192.168.150.20/255.255.255.0
20 ESXi-3 (RG) esxi-3-rg.vmlab.com 192.168.150.21/255.255.255.0
21 ESXi-4 (RG) esxi-4-rg.vmlab.com 192.168.150.22/255.255.255.0
22 ESXi-5 (RG) esxi-5-rg.vmlab.com 192.168.150.23/255.255.255.0
23 ESXi-6 (RG) esxi-6-rg.vmlab.com 192.168.150.24/255.255.255.0
24 ESXi-7 (RG) esxi-7-rg.vmlab.com 192.168.150.25/255.255.255.0
25 ESXi-8 (RG) esxi-8-rg.vmlab.com 192.168.150.26/255.255.255.0
26 vCNS-LB Vcns-lb.vmlab.com 192.168.150.27/255.255.255.0
27 VCNS-LB (edge gateway internal IP)   192.168.150.30/255.255.255.0
Public IPs (In lab we assume these are our WAN IPs)
1 VCNS-LB (Public IP HTTP) Vcloud.vmlab.com 10.0.10.150.100/255.255.255.0
2 VCNS-LB (Public IP Console Proxy) Vcloud-vmrc.vmlab.com 10.0.10.150.101/255.255.255.0
3 vCloud Mgmt. Server(public IP) mgmt-srv.vmlab.com 10.0.10.150.150/255.255.255.0

 Note: in my lab I will use one extra server (vCloud Mgmt. Server) for my cloud lab management. I did not show this in my lab diagram, because it’s optional and may or may not be used in production environment.

 

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s