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
Upgrading vCloud Director 3
To upgrade vCloud Director to a new version, install the new version on each server in the vCloud Director
server group, upgrade the vCloud Director database, and restart vCloud Director services. You must also
upgrade the vSphere components that support vCloud Director, including vShield Manager.
After you upgrade a vCloud Director server, you must also upgrade its vCloud Director database. The
database stores information about the runtime state of the server, including the state of all vCloud Director
tasks it is running. To ensure that no invalid task information remains in the database after an upgrade, you
must ensure that no tasks are active on the server before you begin the upgrade.
IMPORTANT The upgrade process requires you to upgrade vCloud Director, vShield Manager, vCenter, and
all hosts. You must prevent users from accessing vCloud Director until the vShield Manager upgrade step is
complete.
The upgrade preserves the following artifacts:
n
Local and global properties files are copied to the new installation.
n
Microsoft sysprep files used for guest customization are copied to the new installation.
If you use a load balancer to distribute client requests across members of your vCloud Director server
group, you can upgrade a subset of the server group while keeping existing services available on the others.
If you do not have a load balancer, the upgrade requires sufficient vCloud Director downtime to upgrade
the database and at least one server. You might also have to upgrade registered vCenter servers if they are
not running a compatible version of vCenter software. Upgrading vCenter servers and ESXi hosts can incur
additional vCloud Director downtime, because virtual machines are inaccessible while their hosts or
vCenter server are being upgraded.
Upgrading a vCloud Director Server Group
1 Disable user access to vCloud Director. You can also display a maintenance message while the upgrade
is underway. See “Displaying the Maintenance Message During an Upgrade,” on page 35.
2 Use the cell management tool to quiesce all cells in the server group and shut down vCloud Director
services on each server. See “Use the Cell Management Tool to Quiesce and Shut Down a Server,” on
page 35.
3 Upgrade vCloud Director software on all members of the server group. See “Upgrade vCloud Director
Software on Any Member of a Server Group,” on page 36. You can upgrade the servers individually
or in parallel, but you must not restart vCloud Director services on any upgraded member of the group
before you upgrade the vCloud Director database.
4 Upgrade the vCloud Director database. See “Upgrade the vCloud Director Database,” on page 38.
5 Restart vCloud Director on the upgraded servers. See “Start or Stop vCloud Director Services,” on
page 32.
VMware, Inc.
33