Upgrade VMware vCloud Director for Service Providers v5.5.3 to v8.0

My lab environment is running vCloud Director (vCD) v5.5.3 build 2578696, on vSphere 5.5 build 1331820, with vCenter Server Appliance 5.5 Update 2.

On this blog I am going to document the upgrade procedure of vCD to version 8.0. Subsequent posts will follow that encompass the upgrade of vCenter and ESXi to v6.0.

I recommend reading the VMware Update sequence for VMware vSphere v5.5 and its compatible VMware products document which can be found here. This document lists the update sequence that you must to follow.

For my environment the upgrade sequence will be: vCD | vCenter | ESXi | VMware Tools.

I get to skip the NSX upgrade as my lab is already running NSX for vSphere v6.1.4, and currently vCD does not support v6.2.

In my lab I only have one vCD cell server to upgrade. An overview of the upgrade process is:

  1. Restrict access to vCD and display a maintenance message for the duration of the upgrade.
  2. Quiesce vCD cell servers from the Cell Management Tool.
  3. Upgrade the vCD software on all cell servers. Do not restart vCD services until the database is upgraded.
  4. Upgrade the vCD database.
  5. Restart the vCD services on the cell servers.
  6. Remove the access restriction so vCD is able to be used by clients.
  7. If you had the vCD web console open during the upgrade, log out to clear the browser cache.

I have already downloaded the vmware-vcloud-director-8.0.0-3017494.bin file. I used WinSCP to copy this file over to my vCD server and placed it in /var/opt so I can access it locally during the upgrade.

The first step is to restrict access to vCD. vCD responds to all requests with a maintenance message. I did this by logging into the vCD server with Putty as root and running the following commands:

cd /opt/vmware/vcloud-director/bin

./vmware-vcd-cell maintenance

1

The second step is to check the cell status, followed by using the Cell Management Tool to quiescse the cell.

To check the cell status:

./cell-management-tool -u administrator cell –status

2

To quiescse the cell, and to prevent new jobs from running:

./cell-management-tool -u administrator cell –quiesce true

3

Recheck the cell status, when the Job Count is 0 then shutdown the cluster:

./cell-management-tool -u administrator cell –status

./cell-management-tool -u administrator cell –shutdown

I re-checked the cell was down by running another status and confirming I was unable to connect to the cell.

4

The third step is to upgrade the vCD software on all your vCD cell servers. From your Putty window change directory to where you placed the download vCD BIN file, in my case /var/opt, then run the following command to make the installation file executable:

chmod u+x vmware-vcloud-director-8.0.0-3017494.bin

Run the installation file with the following command:

./vmware-vcloud-director-8.0.0-3017494.bin

The installer starts and then prompts you if you wish to continue the upgrade, which I select: Y

5

The upgrade begins and completes. Repeat the above on all your remaining cell servers. Do not restart vCD services until you have upgraded the vCD database.

6

The forth step is to upgrade the vCD database. Run the following command:

/opt/vmware/vcloud-director/bin/upgrade

At this point the upgrade pauses and checks that you are running compatible versions of vShield Manager or NSX. If not it will stop the upgrade. In my case the tests passed and I can proceed to upgrade. I am prompted “Do I wish to upgrade the product now?” To which I select: Y

7

The upgrade completes. I have an option to start the vCD services now, to which I select: Y, and the services start successfully. This also removes the maintenance message.

8

I logged back into the vCD web console, went to Help/About to confirm the version had upgraded.

9

From here, if required you would need to upgrade your vShield Manager or NSX Manager. Following this you would upgrade vCenter and ESXi – which I will cover in another post.

Leave a Reply

Fill in your details below or click an icon to log in:

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

%d bloggers like this: