This is a re-post from the official VMware vCloud blog: http://blogs.vmware.com/vcloud/2012/05/some-more-vcloud-director-configuration-maximums.html
A question was asked yesterday regarding some of the configuration maximums that are currently not listed in the vSphere 5 configuration maximums document. Having discussed with vCloud Engineering and Product Management it has been confirmed that these numbers are used to provide the supported scale of vCloud Director and can be published to the wider community.
The information listed will assist consultants and architects to better understand the supported scale when designing there public and private vCloud infrastructures.
| # of Console sessions (concurrent) | 300 |
| # of Console sessions (active) | 100 |
| # of Cells | 10 |
| # of Logical Networks | 10156 |
| # of vApp Networks | 2987 |
| # of External Networks
|
524 |
| # of Isolated Org Networks | 2264 |
| # of Public Org Networks | 2005 |
| # of Routed Org Networks | 2376 |
| # of Network Pools | 10 |
| # of Catalogs | 1024 |
| # of Media | 1024 |
For the # of console sessions, concurrent is open but idle (think of not displaying screen updates), while Active is sessions that are in use.
The # of cells is the maximum vCD cells you can have in one load balanced group.
It would be great if these made it into a future vSphere 5.x Config Maximums document.
Thanks for posting these undocumented maximums and I agree with Jason these should be documented as they are important to consider when designing a vCloud solution.
Is the number of active/concurrent consoles per cell?
Hi
Yes, the concurrent/active console sessions are per cell. Kinda makes sense too, when looking at the scalability of vCloud Director.