To upgrade VMware Cloud Director to a new version, shut down the VMware Cloud Director services on all cells in the server group, install the new version on each server, upgrade the VMware Cloud Director database, and restart the VMware Cloud Director cells.
If your existing VMware Cloud Director server group consists of VMware Cloud Director installations on Linux, you can use the VMware Cloud Director installer for Linux to upgrade your environment.
For VMware Cloud Director installations on Linux, you can either perform an orchestrated upgrade, or manually upgrade VMware Cloud Director. See Perform an Orchestrated Upgrade of a VMware Cloud Director Installation or Manually Upgrade a VMware Cloud Director Installation. With the orchestrated upgrade, you run a single command which upgrades all cells in the server group and the database. With the manual upgrade, you upgrade each cell and the database in a sequence.
Starting with version 10.3, VMware Cloud Director no longer allows administrator and tenant LDAP servers to bypass SSL certificate validation. Before you upgrade VMware Cloud Director, you must test your connection. If any of the organizations have these invalid configurations, for each one, you must turn off the Accept all certificates setting for the LDAP server and import the certificates in the LDAP settings UI.
In recent releases, when you update the LDAP settings to turn off the Accept all certificates setting, a trust on first use dialog box automates the import of the certificate for the LDAP server of an organization. However, in earlier releases, it is a two-step process of turning the Accept all certificates setting off, and then, using the UI to upload the certificate of the LDAP server.
- Oracle databases are unsupported. If your existing VMware Cloud Director installation uses an Oracle database, see the Upgrade and Migration Paths table.
- Activating and deactivating ESXi hosts is unsupported. Before starting the upgrade, you must activate all ESXi hosts. You can place the ESXi hosts in maintenance mode by using the vSphere Client.
- VMware Cloud Director uses Java with an improved LDAP support. If you are using an LDAPS server, to avoid LDAP login failures, you must verify that you have a properly constructed certificate. For information, see the Java 8 Release Changes at https://www.java.com.
Starting with VMware Cloud Director 10.0, Microsoft SQL Server databases are unsupported.
- The database software you are currently using for the VMware Cloud Director database. For more information, see the Upgrade and Migration Paths table.
- The VMware vSphere ® release you are currently using.
- The VMware NSX® release that you are currently using.
- Any third-party components that directly interact with VMware Cloud Director.
For information about the compatibility of VMware Cloud Director with other VMware products and with third-party databases, refer to the VMware Product Interoperability Matrices at http://partnerweb.vmware.com/comp_guide/sim/interop_matrix.php. If you plan to upgrade your vSphere or NSX components as part of the VMware Cloud Director upgrade, you must upgrade them after the upgrade of VMware Cloud Director. See After You Upgrade VMware Cloud Director.
After you upgrade at least one VMware Cloud Director server, you can upgrade the VMware Cloud Director database. The database stores information about the runtime state of the server, including the state of all VMware Cloud Director tasks it is running. To ensure that no invalid task information remains in the database after an upgrade, you must verify that no tasks are active on any server before you begin the upgrade.
The upgrade also preserves the following artifacts, which are not stored in the VMware Cloud Director database:
- Local and global properties files are copied to the new installation.
- Microsoft Sysprep files used for the guest customization support are copied to the new installation.
The upgrade requires sufficient VMware Cloud Director downtime to upgrade all servers in the server group and the database. If you are using a load balancer, you can configure it to a return a message, for example, The system is offline for upgrade.
Starting with version 10.1, service providers and tenants can use the VMware Cloud Director API to test connections to remote servers, and to verify the server identity as part of an SSL handshake. To protect VMware Cloud Director network connections, configure a deny list of internal hosts that are unreachable to tenants who are using the VMware Cloud Director API for connection testing. Configure the deny list after the VMware Cloud Director installation or upgrade and before granting tenants access to VMware Cloud Director. See Configure a Test Connection Denylist.
- Run the cell management tool
trust-infra-certscommand to import automatically all certificates into the centralized certificate store. See Import Endpoints Certificates from vSphere Resources. - In the Service Provider Admin Portal UI, select each vCenter Server and NSX instance, and reenter the credentials while accepting the certificate.
Upgrade Paths and Workflows
| Source environment | Target environment |
|---|---|
| VMware Cloud Director 10.3 on Linux with an external PostgreSQL database | |
| VMware Cloud Director 9.7 on Linux with an external Microsoft SQL Server database |
|
| VMware Cloud Director 9.7, 10.0, 10.1, or 10.2 on Linux with an external PostgreSQL database | Upgrade your environment to VMware Cloud Director 10.3 on Linux. See Perform an Orchestrated Upgrade of a VMware Cloud Director Installation or Manually Upgrade a VMware Cloud Director Installation. |
| VMware Cloud Director appliance 9.7, 10.0, 10.1, or 10.2 with an embedded PostgreSQL database | Not supported |
