5.5
Table Of Contents
- vCloud Director Installation and Upgrade Guide
- Contents
- VMware vCloud Director Installation and Upgrade Guide
- Overview of vCloud Director Installation, Configuration, and Upgrade
- vCloud Director Architecture
- Configuration Planning
- vCloud Director Hardware and Software Requirements
- Browsers That vCloud Director Supports
- Summary of Network Configuration Requirements for vCloud Director
- Installing and Configuring a vCloud Director Database
- Create SSL Certificates
- Installing and Configuring vShield Manager
- Installing and Configuring an AMQP Broker
- Download and Install the VMware Public Key
- Creating a vCloud Director Server Group
- Install and Configure vCloud Director Software on the First Member of a Server Group
- Configure Network and Database Connections
- Install vCloud Director Software on Additional Members of a Server Group
- Install Microsoft Sysprep Files on the Servers
- Start or Stop vCloud Director Services
- Uninstall vCloud Director Software
- Upgrading vCloud Director
- vCloud Director Setup
- Cell Management Tool Reference
- Index
n
The port at which the broker listens for messages. The default is 5672.
n
The RabbitMQ virtual host. The default is "/".
What to do next
By default, the vCloud Director AMQP service sends unencrypted messages. If you configure it to encrypt
these messages using SSL, it verifies the broker's certificate by using the default JCEKS trust store of the Java
runtime environment on the vCloud Director server. The Java runtime environment is typically located in
the $JRE_HOME/lib/security/cacerts directory.
To use SSL with the vCloud Director AMQP service, select Use SSL on the AMQP Broker Settings section of
the Extensibility page of the vCloud Director Web console, and provide either of the following:
n
an SSL certificate pathname
n
a JCEKS trust store pathname and password
If you do not need to validate the AMQP broker's certificate, you can select Accept all certificates.
Download and Install the VMware Public Key
The installation file is digitally signed. To verify the signature, you must download and install the VMware
public key.
You can use the Linux rpm tool and the VMware public key to verify the digital signature of the
vCloud Director installation file, or any other signed downloaded file from vmware.com. If you install the
public key on the computer where you plan to install vCloud Director, the verification happens as part of
the installation or upgrade. You can also manually verify the signature before you begin the installation or
upgrade procedure, then use the verified file for all installations or upgrades.
NOTE The download site also publishes a checksum value for the download. The checksum is published in
two common forms. Verifying the checksum verifies that the file contents that you downloaded are the
same as the contents that were posted. It does not verify the digital signature.
Procedure
1 Obtain and import the VMware Packaging Public Keys.
a Create a directory to store the VMware Packaging Public Keys.
b Use a Web browser to download all of the VMware Public Packaging Public Keys from the
http://packages.vmware.com/tools/keys directory.
c Save the key files to the directory that you created.
d For each key that you download, run the following command to import the key.
# rpm --import /key_path/key_name
key_path is the directory in which you saved the keys.
key_name is the filename of a key.
2 (Optional) Use the Linux rpm tool to verify the digital signature of the downloaded file.
# rpm --checksig installation-file
After you verify the digital signature of the file, you can use it to install or upgrade vCloud Director on
any server, without having to install the public key on that server. The installer warns you if no key is
installed. You can ignore the warning if you already verified the signature of the file.
vCloud Director Installation and Upgrade Guide
22 VMware, Inc.