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
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.
What to do next
n
If you have not already done so, upgrade the vCloud Director database that this server uses.
n
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,” on page 32.
Upgrade the vCloud Director Database
After you upgrade a server in your vCloud Director server group, you must upgrade the group's
vCloud Director database before you restart vCloud Director services on the server.
All servers in a vCloud Director server group share the same database, so regardless of how many servers
you are upgrading, you need to upgrade the database only once. After the database is upgraded,
vCloud Director servers cannot connect to it until they, too, are upgraded.
Prerequisites
IMPORTANT Back up your existing database before you upgrade it. Use the procedures that your database
software vendor recommends.
Verify that all vCloud Director cells are inactive. See “Use the Cell Management Tool to Quiesce and Shut
Down a Server,” on page 35
vCloud Director Installation and Upgrade Guide
38 VMware, Inc.