The vCloud Director installer verifies that the target server meets all upgrade prerequisites and upgrades the vCloud Director software on the server.

vCloud Director software is distributed as a Linux executable file named vmware-vcloud-director-5.1.0-nnnnnn.bin, where nnnnnn represents a build number. After the upgrade is installed on a member of a server group, you must run a tool that upgrades the vCloud Director database that the group uses before you can restart vCloud Director services on the upgraded server.

Verify that all organizations in the system that contain an organization network also contain an organization vDC. Because the upgrade process converts existing organization networks to organization vDC networks, organizations that contain organization networks but do not contain an organization vDC cannot be upgraded, and the database upgrade fails.

Verify that you have superuser credentials for the target server.

If you want the installer to verify the digital signature of the installation file, download and install the VMware public key on the target server. If you have already verified the digital signature of the installation file, you do not need to verify it again during installation. See Download and Install the VMware Public Key.

Use the cell management tool to quiesce and shut down vCloud Director services on the server's cell.

1

Log in to the target server as root.

2

Download the installation file to the target server.

If you purchased the software on a CD or other media, copy the installation file to a location that is accessible to all target servers.

3

Verify that the checksum of the download matches the one posted on the download page.

Values for both MD5 and SHA1 checksums are posted on the download page. Use the appropriate tool to verify that the checksum of the downloaded installation file matches the one shown on the download page. A Linux command of the following form validates the checksum for installation-file using the MD5 checksum-value copied from the download page.

md5sum -c checksum-value installation-file
4

Ensure that the installation file is executable.

The installation file requires execute permission. To be sure that it has this permission, open a console, shell, or terminal window and run the following Linux command, where installation-file is the full pathname to the vCloud Director installation file.

chmod u+x installation-file
5

Use the cell management tool to quiesce the cell and shut down vCloud Director services on the server.

See Use the Cell Management Tool to Quiesce and Shut Down a Server.

6

In a console, shell, or terminal window, run the installation file.

To run the installation file, type its full pathname, for example ./installation-file. The file includes an installation script and an embedded RPM package.

Note

You cannot run the installation file from a directory whose pathname includes any embedded space characters.

If the installer detects a version of vCloud Director installed on this server that is equal to or later than the version in the installation file, it displays an error message and exits. Otherwise, it prompts you to confirm that you are ready to upgrade this server.

Checking architecture...done
Checking for a supported Linux distribution...done
Checking for necessary RPM prerequisites...done
Checking free disk space...done
An older version of VMware vCloud Director has been detected.  Would you like
to upgrade it?  The installer will stop the vmware-vcd service,
back up any configuration files from the previous release and migrate the 
product configuration as necessary.
7

Respond to the upgrade prompt.

Option

Action

Continue the upgrade.

Type y.

Exit to the shell without making any changes in the current installation.

Type n.

After you confirm that you are ready to upgrade the server, the installer verifies that the host meets all requirements, unpacks the vCloud Director RPM package, stops vCloud Director services on the server, and upgrades the installed vCloud Director software.

Would you like to upgrade now? (y/n) y 
Extracting vmware-vcloud-director ......done
Upgrading VMware vCloud Director...
Installing the VMware vCloud Director 
Preparing...                ##################################################
vmware-vcloud-director      ##################################################
Migrating settings and files from previous release...done
Migrating in-progress file transfers to /opt/vmware/vcloud-director/data/transfer...done
Uninstalling previous release...done

The installer prints a warning of the following form if you did not install the VMware public key on the target server.

warning:installation-file.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 66fd4949
8

(Optional) Update logging properties.

After an upgrade, new logging properties are written to the file /opt/vmware/vcloud-director/etc/log4j.properties.rpmnew.

Option

Action

If you did not change existing logging properties

Copy this file to /opt/vmware/vcloud-director/etc/log4j.properties.

If you changed logging properties

Merge /opt/vmware/vcloud-director/etc/log4j.properties.rpmnew file with the existing /opt/vmware/vcloud-director/etc/log4j.properties. Merging these files preserves your changes.

When the vCloud Director software upgrade is complete, the installer displays a message indicating where the old configuration files are stored, then reminds you to run the database upgrade tool.

If you have not already done so, upgrade the vCloud Director database that this server uses.

If you already upgraded the vCloud Director database that this server group uses, you can restart the upgraded server. See Start or Stop vCloud Director Services.