Cloud Lab-27: vCloud Director Cells- ”Install and Configure Cell-1” (Part 2)

In previous post, i have installed vCloud Director on the Cell1 VM and also do some initial configuration. today, i am moving forward from where i left off .

LAB-27 TASKS (Part 2)

In this Lab we perform following tasks

  1. Configure vCloud Director Cell-1 Server
  2. Securing the Configuration Files
  3. Install Microsoft Sysprep Files on (Cell-1) Server
  4. vCloud Director Cell-1 Setup Wizard

1-Configure vCloud Director Cell-1 Server.

Begin by logging onto the cloud-cell1 server as root and invoking the script located at 

/opt/vmware/vcloud-director/bin/configure

It will prompt you the series of questions.  First two option is to choose http and console IP address.

cloudlab27-vCDC-InstallCell1-39

Next option is to provide “SSL Certificate keystore path” and “syslog” details. I don’t have any syslog in my lab. But it is recommended in production.

NOTE: In this example the file has been temporarily copied to the vCloud transfer location, so it will be accessible on all cells for the installation process. But if you have different security requirements this could be any local or network location as long as it is the same on all cell servers

cloudlab27-vCDC-InstallCell1-40

In next option, it will ask you about your “database server” and “cloud-cell1 database” details.

cloudlab27-vCDC-InstallCell1-41

In last but not the least it will ask you to “start the vCloud Director service” and provide you the “vCloud Directory Setup URL”.

cloudlab27-vCDC-InstallCell1-42

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.

CAUTION: you name should be set correctly otherwise it will throw you java errors in cell.log file and won’t start the vCloud director. In my lab my cell host name is “cloud-cell1”

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.

cloudlab27-vCDC-InstallCell1-43

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-cell1.vmlab.com

2-Securing the Configuration Files.

Installing your first cell server “automatically created an answer file” that can be used to automate installation of subsequent cell servers. The file is created in

 /opt/vmware/vcloud-director/etc/responses.properties .

Although the file does not contain plain-text passwords, it does contain connection details for your environment. Therefore, it is a sensitive file and should be removed or protected once you have finished working with it—especially if you “move it to a shared location” for installing subsequent cell servers.

If you look at the response file, you’ll see the contents shown below.

cloudlab27-vCDC-InstallCell1-44

If you plan to copy this file to a shared location to deploy additional cell servers, you will need to ensure that the owner of the file is “vcloud.vcloud” after you have copied it. “vcloud.vcloud” is a user created by the vCloud installer on your cell server

3-Install Microsoft Sysprep Files on (Cell-1) 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.

Prerequisites

Verify that you have access to the 32- and 64-bit Sysprep binary files for Windows 2003 and Windows XP.

Procedure

Log in to the target server as root.

# cd /opt/vmware/vcloud-director/guestcustomization/default/windows
cloudlab27-vCDC-InstallCell1-45

Create a directory named sysprep.

# mkdir sysprep
#cd Sysprep

For each guest operating system that requires Sysprep binary files, create a subdirectory of

$VCLOUD_HOME/guestcustomization/default/windows/sysprep

Guest OS  Subdirectory to Create Under$VCLOUD_HOME/guestcustomization/default/windows/sysprep
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-cell1.

Following is the sysprep directory location at vCenter “C: /ProgramData/vmware/Vmware VirtualCenter/sysprep”

Below is the look of sysprep directory.

cloudlab27-vCDC-InstallCell1-46

Use SCP to Copy only srv2003, srv2003, xp, xp-64 directories to your Cloud-Cell1.

cloudlab27-vCDC-InstallCell1-47

In Cloud cell 1. Go to sysprep directory and list the directory to verify the copied directory structure.

#cd sysprep
#ls

cloudlab27-vCDC-InstallCell1-48

Now check the contents of each directory, for example in srv2003

#cd srv2003

Every directory’s content should look like as shown below.

cloudlab27-vCDC-InstallCell1-49

Now change the permission of sysprep directory to “vcloud.vcloud”
#chown vcloud:vcloud /opt/vmware/vcloud-director/guestcustomization/default/windows/ -R
cloudlab27-vCDC-InstallCell1-50

Verify the permission

#ls –l
cloudlab27-vCDC-InstallCell1-51

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

4-vCloud Director Cell-1 Setup Wizard

Now that you have your first cell server installed and you can connect to it, you should carry out initial configuration of vCloud Director before proceeding any further. To accomplish this, you use the Adobe Flash–based web interface.

Connect directly to the cell server using a web browser. https://cloud-cell1.vmlab.com.

NOTE:  If you are deploying a load balancer, you should still connect directly to the cell server to do the first-time configuration of the vCloud Director software—in this example, https://cloud-cell1.vmlab.com. Once you’ve built the subsequent cell servers, you can configure the load balancer and access the vCloud interface through it.

cloudlab27-vCDC-InstallCell1-52

Click “Next”

cloudlab27-vCDC-InstallCell1-53

Accept the license. Click “Next”
cloudlab27-vCDC-InstallCell1-54

Enter the “license Key”. Click “Next”
cloudlab27-vCDC-InstallCell1-55

Enter the “vCloud Administrator account” details. Click “Next”.
cloudlab27-vCDC-InstallCell1-56

CAUTION: Ensure that the system name and installation ID are unique—especially the installation directory ID since it is used to generate MAC Address and your need to ensure that it does not conflict with any other vCloud Director Installation Within you organization

Click “Next”
cloudlab27-vCDC-InstallCell1-57

Review the configured summary. Click “finish”
cloudlab27-vCDC-InstallCell1-58

Now login to “cloud-cell1”. Enter the cloud administrative credentials which we defined in vCloud configuration first wizard.
cloudlab27-vCDC-InstallCell1-59

In Manage & Monitor tab-> Cloud Resources -> click on Cloud Cells and check your cloud cells.
cloudlab27-vCDC-InstallCell1-60

NOTE: Don’t worry about the error “None of the Cells have a vCenter Proxy service running”. It will disappear when we add vCenter in cloud inventory

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