Dear All,
I have an issue with the vCAC 6.0, I have also tried it in 5.2 and it's the same issue there, so I guess it's more an approach than a bug, more over it's stated so in the manual for 5.2. So here're the details:
I have a cluster: Cluster 01, within it I have two esx hosts esxhost01 and esxhost02, each with 16GB of memory. When you look at these nodes through vSphere Client you can see that each host has the following values for Consumed Memory, look through: Select ESX Host -> Summary -> Memory Usage / Capacity
esxhost1 Memory Usage: 13 840MB, Capacity 16 381 MB (hence "free memory" -> 2 541 MB)
esxhost2 Memory Usage: 13 501MB, Capacity 16 381 MB (hence "free memory" -> 2 880 MB)
When you look at the ESX Host -> Performance -> Advanced -> Memory
esxhost1 Active Average: 1 160 MB
esxhost2 Active Average: 1 394 MB
As you may or may not know, when vCAC provisions a VM in the Cluster that came from vCenter, it pins the machine on a particular host in the cluster.
When I try provisioning an empty VM through vCAC (5.2/6.0) using the blueprint with the Blueprint Type Server: Server, Action: Create, Provisioning workflow: BasicVMWorkflow with the size of memory below 2 880 MB, the provisioning happens. However, if I use 3 000 MB for VM memory, I get the error:
[11/14/2013 1:49:22 PM] [Info]: WorkitemResponse [<?xml version="1.0" encoding="utf-16"?><workItemResponse id="ab8a95d2-ec3d-44d5-ac88-a9f73585d291"><task type="CloneVM"><result succeeded="False"><message>Value cannot be null.
Parameter name: No available host has sufficient free memory to satisfy your request.</message><parameter name="VirtualMachine.Admin.BuildFailure">true</parameter></result></task></workItemResponse>]
But when I do it through the vSphere Client, I'm able to provision an empty VM with 8GB of memory!
In the vCAC 5.2 document titled "vCloud Automation Center Operating Guide" on page 164 it states:
Note: When selecting the node in a cluster on which to provision a requested machine, vCAC considers three factors: whether the node is in maintenance mode, its overall status (green, yellow or red) and the amount of free memory it has available.
I guess that this is the logic that prevents me from creating my machines through vCAC. I think this logic is invalid, VMware - what do you think? I beleive it needs to be corrected and use the same logic for checking the memory as does vSphere client use.
Thanks,
Roman
PS: Cross posted into "VMware Cloud Automation Beta"