Each server in a VMware Cloud Director server group must meet certain hardware and software requirements. In addition, a supported database must be accessible to all members of the group. Each server group requires access to a vCenter Server system, an NSX Manager instance, and one or more ESXi hosts.

Compatibility with Other VMware Products

For the most recent information about compatibility between VMware Cloud Director and other VMware products, see the VMware Product Interoperability Matrix at http://partnerweb.vmware.com/comp_guide/sim/interop_matrix.php.

vSphere Configuration Requirements

vCenter Server instances and ESXi hosts intended for use with VMware Cloud Director must meet specific configuration requirements.
  • vCenter Server networks intended for use as VMware Cloud Director external networks or network pools must be available to all hosts in any cluster intended for VMware Cloud Director to use. Making these networks available to all hosts in a data center simplifies the task of adding new vCenter Server instances to VMware Cloud Director.
  • vSphere Distributed Switches are required for isolated networks and network pools backed by NSX Data Center for vSphere.
  • vCenter Server clusters used with VMware Cloud Director must specify a vSphere DRS automation level of Fully Automated. Storage DRS, if enabled, can be configured with any automation level.

    When the DRS setting in vCenter Server is set to Manual, VMware Cloud Director does not support the power on function of VMs. VMware Cloud Director supports the power on function only when the DRS automation level is Fully Automated or Partially Automated.

  • vCenter Server instances must trust their hosts. All hosts in all clusters managed by VMware Cloud Director must be configured to require verified host certificates. In particular, you must determine, compare, and select matching thumbprints for all hosts. See Configure SSL Settings in the vCenter Server and Host Management documentation.
Note: VMware recommends that VMware Cloud Director manages a vCenter Server instance exclusively. When you use a vCenter Server instance for VMware Cloud Director and other purposes, a vCenter Server administrator might accidentally move VMware Cloud Director resources. This can cause VMware Cloud Director to operate incorrectly, including losing virtual machines that VMware Cloud Director manages.

Supported Platforms, Databases, and Browsers

See the VMware Cloud Director Release Notes for information about the server platforms, browsers, LDAP servers, and databases supported by this release of VMware Cloud Director.

Disk Space, Memory, and CPU Requirements

For more information about disk space, memory, and CPU requirements, see VMware Cloud Director Appliance Sizing Guidelines.

Shared Storage

NFS or other shared storage volume for the VMware Cloud Director transfer service. The storage volume must be expandable and accessible to all servers in the server group.