Posted by: Nathan Simon
The vCloud Suite Digest is a collection of common technical questions and answers. Get information directly from the people who find and fix issues themselves. I have included part of the intro, and one of the Q & A’s to get your technical juices flowing, check it out below.
Behind us is a legion of people a group of people far too numerous to mention (for us these are the unsung heroes of VMware) who provide definitive answers and guidance. People fixing problems on a daily basis, that don’t get half the spotlight that jumped up evangelists do. In this months edition we cover such topics as:
- vCloud Director Database Encryption
- vCloud Director Database Settings
- vCloud Director and NFS Transfer Share
- vCloud Director: Maximum Number of VMs
- vCloud Director: Sticky Sessions
- vCNS Edge Gateway: vNIC Maximum
- vCNS Edge Gateway Load Balancing
- vCloud Connector: Copying vApps from vCD 1.5 to 5.1
vCloud Director: Maximum Number of VMs
Q.What is the purpose of “Maximum number of VMs” in the Org VDC setup? This value does not seem to hinder consumers from adding/starting more VMs.
A. These settings affect only vApps that you start after specifying the value. vApps that are already running are not affected. The usage information that vCloud Director reports for this organization VDC does not reflect the new settings until all running vApps are stopped and started again.
A change was made with vCD 5.1.1 to the Allocation Pool model, which enables administrators to work around the maximum number of virtual machines on an organization VDC caused by the vCPU to MHz mapping parameter. This limit can now be worked around by setting a low vCPU to MHz mapping without CPU limiting virtual machines in the organization VDC.
Go here to read the full article.