vCloud Director 5.1 was recently announced at VMworld 2012, and on September 10, vCloud Director 5.1 was officially released. Since many of you have existing vCloud Director 1.5 installations, here is a guide to help you upgrade to vCloud Director 5.1.
The general steps for upgrading are as follows:
- Quiesce all cells
- Upgrade vCloud Director
- Upgrade vCloud Director database
- Restart vCloud Director service
- Upgrade vShield Manager
- Upgrade ESXi hosts and vCenter Server
Quiesce All Cells
To start off the process, we’ll quiesce and shutdown the cell. First, let’s check the cell status.
- /opt/vmware/vcloud-director/bin/cell-management-tool -u <username> cell –status
My installation has zero active jobs, but yours may have some or even many. We’ll run a quiesce command to suspend the task scheduler. Once all tasks are finished, the cell is turned to inactive.
- /opt/vmware/vcloud-director/bin/cell-management-tool -u <username> cell –quiesce true
Now that the cell is inactive, we can gracefully shut it down.
- /opt/vmware/vcloud-director/bin/cell-management-tool -u <username> cell –shutdown
The cell has now been successfully shut down.
Upgrade vCloud Director
The next step is to upgrade vCloud Director. To do so, we’ll need to get the upgrade bits onto the server. I’ve copied mine into the /tmp directory. Before I run the upgrade installer, I need to make sure it’s executable.
- chmod u+x vmware-vcloud-director-5.1.0-810718.bin
Now that it’s executable, we can run it.
Note that I’m prompted because I’m not running a supported Linux distribution (CentOS 5.8 x64). If you’re on RedHat Enterprise Linux of a supported rev, you shouldn’t see the error.
Hit ‘y’ to upgrade.
You should see something similar to the screenshots below during the upgrade process.
The vCloud Director upgrade is now complete.
Upgrade vCloud Director Database/Restart Service
The next step is to upgrade the vCloud Director database. To do so, run the following command.
Note – It’s very important to have a full backup of your database before proceeding. Hit ‘y’ to upgrade the database.
You should see a screen similar to that below. Hit ‘y’ to rebuild indexes, then to update database statistics or ‘n’ to skip. This is recommended to increase database performance. When finished, hit ‘y’ to automatically start the vmware-vcd service.
The vCloud Director database has now been upgraded. My lab vCloud Director wasn’t accessible at this point until I fully rebooted the machine, but your mileage may vary. A simple ‘service vmware-vcd restart’ may be all that’s required.
Upgrade vShield Manager
The next step is to upgrade vShield Manager from 5.0 to 5.1, which will be accomplished via the vShield Manager GUI.
Log in as you usually would as an administrative user.
Once logged in, click on ‘Settings & Reports’
Now, click on the ‘Updates’ tab.
On the ‘Updates’ tab, click ‘Upload Upgrade Bundle’.
Browse to the file location, then hit ‘Upload File’. Note – I ran into a problem here where vShield Manager would not recognize my upgrade package as legit. See the link below for a resolution.
You should then see a popup similar to the one below. Click ‘OK’.
Once the upgrade file has been imported, click ‘Install’ to perform the upgrade.
vShield Manager will now confirm the upgrade. Click ‘Confirm Install’.
You should now see the process go forward.
After the installation is finished, the virtual appliance will reboot, and you will have to log back in, possibly even re-enable the vShield Manager vCenter plugin. When you log back in to vShield Manager, you should see a new interface, as below.
On the ‘Updates’ tab, you’ll see that you’re on the new revision, 5.1.0-807847.
vShield Manager is now up to date.
Upgrade ESXi hosts and vCenter Server
This is not a necessary step for operation of vCloud Director 5.1, and is itself a lengthy article, so watch this space for another article outlining the upgrade process for ESXi hosts and vCenter Server.