You can upgrade the vCloud Director appliance from version 9.7 to version 10.0 or upgrade vCloud Director 10.0 to a patch release.
During the upgrade of the vCloud Director appliance deployment, the vCloud Director service stops working and some downtime can be expected. The downtime depends on the time you need to upgrade each vCloud Director appliance and to run the vCloud Director database upgrade script. The number of working cells in the vCloud Director server group reduces until you stop the vCloud Director service on the last vCloud Director appliance. A properly configured load balancer in front of the vCloud Director HTTP endpoints should stop routing traffic to the cells that are stopped.
After you apply the upgrade to every vCloud Director appliance and the database upgrade is complete, you must reboot each vCloud Director appliance.
- Log in to the vCenter Server instance on which resides the primary vCloud Director appliance of your database high availability cluster.
- Navigate to the primary vCloud Director appliance, right-click it, and click .
- Right-click the appliance and click OK. . Enter a name and, optionally, a description for the snapshot, and click
- Right-click the vCloud Director appliance and click .
- Verify that all nodes in your database high availability configuration are in a good state. See Check the Status of a Database High Availability Cluster.
- In a Web browser, log in to the appliance management user interface of a vCloud Director appliance instance to identify the primary appliance, https://appliance_ip_address:5480.
Make a note of the primary appliance name. You must upgrade the primary appliance before the standby and application cells. You must use the primary appliance when backing up the database.
- Download the update package to the appliance you are upgrading.
Note: You must upgrade the primary appliance first.vCloud Director is distributed as an executable file with a name of the form VMware_vCloud_Director_v.v.v.v- nnnnnnnn_update. tar.gz, where v. v. v. v represents the product version and nnnnnnnn the build number. For example, VMware_vCloud_Director_10.0.0.4424-14420378_update.tar.gz.
- Create the local-update-package directory in which to extract the update package.
- Extract the update package in the newly created directory.
tar -zxf VMware_vCloud_Director_v.v.v.v-nnnnnnnn_update.tar.gz \ -C /tmp/local-update-package
- Set the local-update-package directory as the update repository.
vamicli update --repo file:///tmp/local-update-package
- Check for updates to verify that you established correctly the repository.
vamicli update --checkThe upgrade release appears as an Available Update.
- Shut down vCloud Director by running the following command:
/opt/vmware/vcloud-director/bin/cell-management-tool -u <admin username> cell --shutdown
- Apply the available upgrade.
vamicli update --install latest
- Repeat Step 2 to Step 8 on the remaining standby and application cells.
- From the primary appliance, back up the vCloud Director appliance embedded database.
- From any appliance, run the vCloud Director database upgrade utility.
- Reboot each vCloud Director appliance.
shutdown -r now
What to do next
- If the upgrade is successful, you can delete the snapshot of the vCloud Director appliance.
- If the upgrade is not successful, you can roll back the vCloud Director appliance to the snapshot that you took before the upgrade. See Roll Back a vCloud Director Appliance When an Upgrade Fails.