3.1.1 Component Sizing
The following table lists the requirements for each of the components that run in the management cluster. For the number of virtual machines and organizations listed in the private or public service definitions, you do not have to worry about scaling too far beyond the provided values.
Table 3. Component Requirements for a Management Cluster
Item | vCPU | Memory | Storage | Networking |
vCenter Server | 2 | 4GB | 20GB | 1 GigE |
Database server | 4 | 16GB | 100GB | 1 GigE |
vCloud Director cell 1 | 2 | 4GB | 30GB | 1 GigE |
vCloud Director cell 2 | 2 | 4GB | 30GB | 1 GigE |
vCenter Chargeback Manager | 2 | 4GB | 30GB | 1 GigE |
vCloud Networking and Security Manager | 2 | 8GB | 8GB | 100Mb |
TOTAL | 14 | 40GB | 218GB* | 4 GigE* |
* Numbers rounded up or down do not affect overall sizing.
The database server hosts databases for vCenter Server, vCenter Server Single Sign-On, vCloud Director, and vCenter Chargeback Manager. Use different users and instances for each database per VMware design guidelines. VMware vCloud Director 5.1 supports both Oracle and SQL Server databases.
In addition to the storage requirements in
Table 3, a shared storage volume must be configured and made accessible to all cells
in a vCloud Director server group to facilitate file transfers in a multicell environment. The size
needed for this volume varies
depending on the expected number of
concurrent uploads. After an upload completes,
the vApp data moves
to the designated organization virtual datacenter
and the data no longer resides on the NFS volume. The recommended starting size for the NFS transfer volume is 250GB
. Transferred images can be large, so monitor
this volume and increase the size if necessary.For additional installation prerequisites, see
the vCloud Director Installation and Configuration Guide (
http://www.vmware.com/support/pubs/vcd_pubs.html).