You can upgrade the VMware Cloud Director appliance to the latest version or apply patches to the VMware Cloud Director appliance by using an update package.
During the upgrade of the VMware Cloud Director appliance deployment, the VMware Cloud Director service stops working and some downtime can be expected. The downtime depends on the time you need to upgrade each VMware Cloud Director appliance and to run the VMware Cloud Director database upgrade script. The number of working cells in the VMware Cloud Director server group reduces until you stop the VMware Cloud Director service on the last VMware Cloud Director appliance. A properly configured load balancer in front of the VMware Cloud Director HTTP endpoints should stop routing traffic to the cells that are stopped.
After you apply the upgrade to every VMware Cloud Director appliance and the database upgrade is complete, you must reboot each VMware Cloud Director appliance.
- When upgrading from version 10.1 or later or when patching, if the automatic failover in case of a primary database service failure is enabled, change the failover mode to
Manualduring the upgrade. After the upgrade, you can set the failover mode to
Automatic. See Automatic Failover of the VMware Cloud Director Appliance.
- Log in to the vCenter Server instance on which resides the primary VMware Cloud Director appliance of your database high availability cluster.
- Navigate to the primary VMware Cloud 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 VMware Cloud Director appliance and click .
- Verify that all nodes in your database high availability configuration are in a good state. See View the VMware Cloud Director Appliance Cluster Health and Failover Mode.
- In a Web browser, log in to the appliance management user interface of a VMware Cloud 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.VMware Cloud Director is distributed as an executable file with a name of the form VMware_Cloud_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_Cloud_Director_10.1.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_Cloud_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 VMware Cloud 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 VMware Cloud Director appliance embedded database.
- From any appliance, run the VMware Cloud Director database upgrade utility.
- Reboot each VMware Cloud Director appliance.
shutdown -r now
What to do next
- If the upgrade is successful, you can delete the snapshot of the VMware Cloud Director appliance.
- If the upgrade is not successful, you can roll back the VMware Cloud Director appliance to the snapshot that you took before the upgrade. See Roll Back a VMware Cloud Director Appliance When an Upgrade Fails.