3.1.1 Component Sizing
The following table lists the requirements for each of the components that run in the management cluster. The following recommendations will scale to accommodate the number of virtual machines and organizations listed in the private or public service definitions.
Table 3. Component Requirements for a Management Cluster
Item | vCPU | Memory | Storage | Networking |
vCenter Server | 2 | 4GB | 20GB | 1GigE |
Database server | 4 | 16GB | 100GB | 1GigE |
vCloud Director cell 1 | 2 | 4GB | 30GB | 1GigE |
vCloud Director cell 2 | 2 | 4GB | 30GB | 1GigE |
vCenter Chargeback Manager | 2 | 4GB | 30GB | 1GigE |
vCloud Networking and Security Manager | 2 | 8GB | 8GB | 100Mb |
Total | 14 | 40GB | 218GB* | 4GigE* |
* Numbers rounded up or down do not affect overall sizing.
The database server hosts databases for vCenter Server, VMware vCenter Single Sign-On, vCloud Director, and vCenter Chargeback Manager. Use different users and instances for each database based on VMware design guidelines. VMware vCloud Director 5.1 supports both Oracle and Microsoft SQL Server databases.
To facilitate file transfers in a multicell environment, a shared storage volume must be configured and made accessible to all cells in a vCloud Director server group. The necessary volume size varies on the expected number of concurrent uploads. Following an upload, 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 Upgrade Guide in the vCloud Director documentation (
http://www.vmware.com/support/pubs/vcd_pubs.html).