You can create a vCloud Director server group by deploying one or more instances of the vCloud Director appliance. You deploy the vCloud Director appliance by using the vSphere Client (HTML5) or the VMware OVF Tool.

Important: Mixed vCloud Director installations on Linux and vCloud Director appliance deployments in one server group are unsupported.

The vCloud Director appliance is a preconfigured virtual machine that is optimized for running the vCloud Director services.

The appliance is distributed with a name of the form VMware vCloud Director-v.v.v.v-nnnnnn_OVF10.ova, where v.v.v.v represents the product version and nnnnnn the build number. For example: VMware vCloud Director-

The vCloud Director appliance package contains the following software:
  • VMware Photon™ OS
  • The vCloud Director group of services
  • PostgreSQL 10

The primary-small and standby-small vCloud Director appliance sizes are suitable for lab or test systems. The primary-large and standby-large sizes meet the minimum sizing requirements for production systems. Depending on the workload, you might need to add additional resources.

Important: Installing any third-party component on the vCloud Director appliance is unsupported. You can install only supported VMware components according to VMware Product Interoperability Matrices. For example, you can install a supported version of a VMware vRealize ® Operations Manager™ or VMware vRealize ® Log Insight™ monitoring agent.

Appliance Database Configuration

Starting with version 9.7, the vCloud Director appliance includes an embedded PostgreSQL database with а high availability (HA) function. To create an appliance deployment with a database HA cluster, you must deploy one instance of the vCloud Director appliance as a primary cell, and two instances as standby cells. You can deploy additional instances of the vCloud Director appliance in the server group as vCD application cells, which run only the vCloud Director group of services without the embedded database. vCD application cells connect to the database in the primary cell. See Appliance Deployments and Database High Availability Configuration.

By default, the vCloud Director appliance uses TLS, in place of the deprecated SSL, for database connections, including replication. This feature is active immediately after deployment, using a self-signed PostgreSQL certificate. To use a signed certificate from a certificate authority (CA), see Replace a Self-Signed Embedded PostgreSQL and vCloud Director Appliance Management UI Certificate.

Note: The vCloud Director appliance does not support external databases.

Appliance Network Configuration

Starting with version 9.7, the vCloud Director appliance is deployed with two networks, eth0 and eth1, so that you can isolate the HTTP traffic from the database traffic. Different services listen on one or both of the corresponding network interfaces.
Note: The eth0 and eth1 networks must be placed on separate subnets.
Service Port on eth0 Port on eth1
SSH 22 22
HTTP 80 n/a
HTTPS 443 n/a
PostgreSQL n/a 5432
Management UI 5480 5480
Console proxy 8443 n/a
JMX 8998, 8999 n/a
JMS/ActiveMQ 61616 n/a

After the creation of the vCloud Director appliance, you can use the vSphere networking features to add a new network interface card (NIC). See the Add a Network Adapter to a Virtual Machine information in the vSphere Virtual Machine Administration guide.

The vCloud Director appliance supports user customization of firewall rules by using iptables. To add custom iptables rules, you can add your own configuration data to the end of the /etc/systemd/scripts/iptables file.