vCloud Director must be configured to support environments that can securely support multiple tenants.

The vCloud Director environment must be fully configured to support workloads before you can continue with the vCloud Availability for vCloud Director installation. You must create the Resource vSphere, Provider VDCs, Organizations, and Organization VDCs before installing the vCloud Availability for vCloud Director solution. For more information, see the vCloud Director Documentation.

vCloud Director is configured to use the following settings:

  • Enabled Public URL and certificates. For more information, see the vCloud Director Administrator's Guide.

  • Shared single sign-on. For more information, see Configure vCloud Director to use vCenter Single Sign On in vCloud Director Administrator's Guide.

By default, vCloud Availability for vCloud Director 2.0 supports the use of TLS 1.2 during the SSL handshake process. To build a pure TLS 1.2 environment for vCloud Availability for vCloud Director operations, the vSphere Replication and vCenter Server instances that are deployed on-premise must also support TLS 1.2. For more information, select the Transport Layer Security category from the drop-down in the Interoperability Pages for vCloud Availability for vCloud Director 2.0.

Configure the timeout settings for the vCloud Director extensions.

Use a text editor to open /opt/vmware/vcloud-director/etc/global.properties file. Set the extensibility.timeout value to 60.

Use a wildcard certificate for all public interfaces of vCloud Director to enable certificate sharing between multiple hosts and subdomains. For example:

*.provider.com

Copies of the following files are required to create and configure a Cloud Proxy:

  • /opt/vmware/vcloud-director/etc/responses.properties

  • certificates.ks