In Previous post, i have finished the deployment of vCloud Director Cell-1. in this post, i will show you how to install vCloud Director Cell-2 for High availability and load balancing purpose of your Cloud environment.
In this Lab we perform following tasks
Following are the steps to install/configure the vCloud director (Cell-2) server.
- Preparing the vCloud Director Cell-2 Server
- Install vCloud Director on Cell-2
- Configure the Transfer Location
- Configure vCloud Director Cell-2 Server
- Install Microsoft Sysprep Files on (Cell-2) Server
- vCloud Director Cell-1 Setup Wizard
1-Preparing the vCloud Director Cell-2 Server
The first step of this post is to set up the second vCloud Director Cell. The installation uses a special “responses” file but before that installation we need to handle the shared transfer area and stop the first cell…
Install RPM for vCloud
Following packages are required by the vCloud directory for start insatllation.
#yum install alsa-lib bash chkconfig coreutils findutils glibc grep initscripts krb5-libs libgcc libICE libSM libstdc libX11 libXau libXdmcp libXext libXi libXt libXtst module-init-tools net-tools pciutils procps redhat-lsb sed tar which
Test SQL Connection
Before installing Check connection with SQL server and make sure firewall in not blocking his port.
#telnet cloud-sql.vmlab.com 1433
If telnet is not available then install telnet rpm.
#yum install telnet
Check if java is installed.
If not then use below cmd to install it
#yum install java
2-Install vCloud Director on Cell-2
1-Copy the vmware-cloud-director-5.5.0-1323688.bin to the /root on the Cell-2
2-Next change the privileges on the .bin file.
#chmod u+x vmware-cloud-director-5.5.0-1323688.bin
From Cell-1 copy the /opt/vmware/vcloud-director/etc/responses.properties on /opt/vmware/vcloud-director/data/transfer/ (NFS Store)
Do not run configuration script. Select “n” to start it later
3-Configure the Transfer Location
To mount the NFS share on cloud-cell2 we need to install following packages. Go to shell or console and run the below cmd.
#yum install nfs-utils rpcbind
Start the rpcbind service
#service rpcbind start
Make “rpcbind” service to start automatically at boot time.
#chkconfig rpcbind –level 35 rpcbind on
Set share area permission
#chown –R vcloud:vcloud /opt/vmware/vcloud-director/data/transfer/
Mount Share Area
#mount vcloud-vsan.vmlab.com:/mnt/vg_cloud-transfer1/lv_cloud_transfer1/nfs_cloud_transfer1 /opt/vmware/vcloud-director/data/transfer/
Verify the mounted directory contents. It look like as shown below
As you have seen Cell-1 Cert Directory, where we store our vcloud.ks (certificate) file and “response. Properties” of the Cell-1 configuration file. Later we will use this to configure Cell-2.
Followed by editing the /etc/fstab file to make sure this NFS location was mounted for future boot times:
Add below line in /etc/fstab
vcloud-vsan.vmlab.com:/mnt/vg_cloud-transfer1/lv_cloud_transfer1/nfs_cloud_transfer1 /opt/vmware/vcloud-director/data/transfer/ nfs rw 0 0
4-Configure vCloud Director Cell-2 Server
Now run the vCloud script with the “responses.properties” file. Who work as answer file for our Cell-2 installation.
#/opt/vmware/vcloud-director/bin/configure -r /opt/vmware/vcloud-director/data/transfer/responses.properties
It will only ask you to provide “http” and “proxyconsole” IP settings.
Click “Y” to start the VCloud Director Service.
Although the vCloud cell service has started, a number of background activities are going on to complete cell service startup. Therefore, you may not be able to connect to the cell server URL for a couple of minutes.
If you want to check on the status, you can monitor the cell.log file, which is located at /opt/vmware/vcloud-director/logs/cell.log.
Once the log file confirms the application has initialized, you should check that you can connect to the web server via HTTPS using a web browser by going to the FQDN of the cell server—in this example, https://cloud-cell2.vmlab.com
5-Install Microsoft Sysprep Files on (Cell-2) Server
Before vCloud Director can perform guest customization on virtual machines with certain older Windows Guest operating systems, you must install the appropriate Microsoft Sysprep files on each member of the Server group. Sysprep files are required only for some older Microsoft operating systems. If your cloud does not need to Support guest customization for those operating systems, you do not need to install Sysprep files.To install the Sysprep binary files, you copy them to a specific location on the server. You must copy the Files to each member of the server group.
Verify that you have access to the 32- and 64-bit Sysprep binary files for Windows 2003 and Windows XP.
Log in to the target server as root.
# cd /opt/vmware/vcloud-director/guestcustomization/default/windows
Create a directory named sysprep.
# mkdir sysprep
For each guest operating system that requires Sysprep binary files, create a subdirectory of $VCLOUD_HOME/guestcustomization/default/windows/sysprep
|Subdirectory to Create Under
|Windows 2003 (32-bit)||svr2003|
|Windows 2003 (64-bit)||svr2003-64|
|Windows XP (32-bit)||xp|
|Windows XP (64-bit)||Xp-64|
Table: Subdirectory Assignments for Sysprep Files
I already configured sysprep in my vCenter installation section. I am going to copy those sysprep files from vCenter to my cloud-cell2.
Following is the sysprep directory location at vCenter “C: /ProgramData/vmware/Vmware VirtualCenter/sysprep”
Below is the look of sysprep directory.
Use SCP to Copy only srv2003, srv2003, xp, xp-64 directories to your Cloud-Cell2.
In Cloud Cell-2, Go to sysprep directory and list the directory to verify the copied directory structure.
Now check the contents of each directory, for example in srv2003
Every directory’s content should look like as shown below.
Now change the permission of sysprep directory to “vcloud.vcloud”
#chown vcloud:vcloud /opt/vmware/vcloud-director/guestcustomization/default/windows/ -R
Verify the permission
NOTE: When the Sysprep files are copied to all members of the server group, you can perform guest customization on virtual machines in your cloud. You do not need to restart vCloud Director after the Sysprep files are copied
6-vCloud Director Cell-2 Setup Wizard
Now Login using https://cloud-cell2.vmlab.com
Provide your vcloud administrative credentials which you defined in Cell-1.
Once Loged in ->From home -> Manage & Monitor -> Cloud Cells
Verify 2nd Cell has appeared in Cloud Cell inventory.