Hi,
We've been working with vCD 5.1 (5.1.1.868405, Appliance version), and have discovered apparent discrepancies between expect behavior of Allocation Pool vCPU and memory reservations / limits / shares, relative to our expectations and VMware documentation.
Based on documentation od the vCD User Interface, expected behavior of VMs in the Allocation Pool model were:
- vCPU reservation forced to 0 (no reservation) as was the case in vCD 1.0 and 1.5
- vCPU Limit set to vCPU speed configured for the Allocation Pool x number of vCPUs for the VM
- vCPU shares forced to Normal
- Memory reservation set to VM's memory size x % guarantee for the Allocation Pool (*think* that's how it was in vCD 1.x).
- Memory limit set to VM's memory size
- Memory shares forced to Normal
Instead, what we find is:
- vCPU limit is forced to Unlimited (not related to vCPU speed), NOT as expected
- Memory reservation always forced to 0 (no reservation, not related to % guarantee), NOT as expected
- Memory limit always forced to Unlimited (not related to VM memory size), NOT as expected
We tested this by creating VMs with various reservation / limits / shares, then starting them in the Allocation Pool vDC, then inspect actual VM setting in vSphere layer. No discrepancies were found in either the PAYG or Reservation Pool models.
Has anyone else found this?? Could we be doing something wrong to cause this behaviour?? Is it a known issue??
We need to be able to give our customers good guidance on how to configure under each of the vCD allocation models, including Allocation Pool, in prder to achieve required performance SLAs.
Cheers,
PeterB