All members of a vCloud Director share database connection and other configuration details that you specify when installing and configuring the first member of the group. These details are captured in a response file that you must use when adding members to the group.

About this task

vCloud Director software is distributed as a digitally signed Linux executable file with a name of the form vmware-vcloud-director-distribution-v.v.v-nnnnnn.bin, where v.v.v represents the product version and nnnnnn the build number. For example: vmware-vcloud-director-distribution-8.10.0-3698331.bin. Running this executable installs or upgrades vCloud Director.

The vCloud Director installer verifies that the target server meets all platform prerequisites and installs vCloud Director software on it. After the software is installed on the target server, you must run a script that configures the server's network and database connections. This script creates a response file that you must use when configuring additional members of this server group.

Prerequisites

  • Verify that the target server and the network it connects to meet the requirements specified in Summary of Network Configuration Requirements for vCloud Director.

  • Verify that you have superuser credentials for the target server.

  • Verify that the target server mounts the shared transfer service storage volume at /opt/vmware/vcloud-director/data/transfer.

  • To have the installer verify the digital signature of the installation file, download and install the VMware public key on the target server. If you 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.

Procedure

  1. Log in to the target server as root.
  2. Download the installation file to the target server.

    If you purchased the software on media, copy the installation file to a location that is accessible to the target server.

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

    Values for 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 displays the checksum for installation-file.

    [root@cell1 /tmp]# md5sum installation-file
    checksum-value installation-file 

    Compare the checksum-value produced by this command with the MD5 checksum copied from the download page.

  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.

    [root@cell1 /tmp]# chmod u+x installation-file
  5. In a console, shell, or terminal window, run the installation file.

    To run the installation file, type its full pathname, for example:

    [root@cell1 /tmp]# ./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.

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

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

    When the installer runs, it takes these actions.

    1. Verifies that the host meets all requirements

    2. Verifies the digital signature on the installation file

    3. Creates the vcloud user and group

    4. Unpacks the vCloud Director RPM package

    5. Installs the software

    After the software is installed, the installer prompts you to run the configuration script, which configures the server's network and database connections.

What to do next

Decide whether to run the configuration script.

For more information about running the configuration script, see Configure Network and Database Connections.