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.
I have been trying to export some VMs from my home lab to my public cloud provider, however when I tried to select a cloud I received the error that the vCloud Connector Node was not available. After logging into the vCloud Connector server, I could see both nodes were down. I had enabled the firewall on both my public clouds yesterday, so I realised I had blocked the ports that the vCloud Connector Node uses to talk to the vCC server and other nodes. So I wondered which ports needed to be enabled. Reading through the vCloud Installation and Configuration guide for vCC 1.5.0 there is a great diagram on page 37 that explains the end to end data flow. As you can see by the diagram above the vCloud Connector Nodes talk on port 8443. You need to open this port at both sides, your private cloud and your public cloud. Using my public cloud provider portal I enabled the required port and pointed to the internal IP of the vCC node. After logging into the vCloud Connector server and refreshing the page I can now see that my public cloud nodes are both up and available again.
I have just realised that VMware Chargeback 2.0 has been released. A quick point to note is that vCenter Chargeback is now known as Chargeback Manager. From a vCloud perspective, this is what we have all been waiting for. Chargeback Manager 2.0 provides support for all the features in vCloud Director 1.5 and vSphere 5.0. To read the full release notes click here This is some of the important features I think will interest people: Charge thin and thick provisioned virtual machines differently Tier based Storage costing Complete support for vSphere 5.0 and vCloud Director 1.5 Support for overage charging for org vDCs in the Allocation Pool model of vCloud Director Support for burstable billing or 95th percentile billing for the external network traffic in vCloud Director New cost models and billing policies for vCloud Director Complete support for vSphere 5.0 and vCloud Director 1.5
Although I posted this back in July, I regularly get asked about the location of the official VMware vCloud Director documentation, so thought I would post it again, with a couple of direct links to version 1.5 documentation. All the available documents can be found at this link: http://www.vmware.com/support/pubs/vcd_pubs.html vCD 1.5 installation guide click here vCD 1.5 Administration guide click here vCD 1.5 Users Guide click here