In the Usage Meter version 2.1.1 the Aggregate Billing Report is always showing the same values for both the Total Allocated vRAM and the Total Billed vRAM despite the Detailed billing report showing them to be considerably different. Is this a bug in the 2.1.1 version?
24576 (24x1024MB) as per a vCloud Service Provider Bundle guide document provided by VMWare. I can't reference you which document it was as I simply have the pertinent page printed out and stuck above my desk and I'll need to go trolling through my emails to find the correct reference which I currently can't do.
Message was edited by: dwhittaker - Added picture.
Reading between the lines of your question, is this simply a wording issue? "Allocated" meaning the billed (allocated*50%) or (reserved) amount of vRAM (not the full allocated amount assigned to a VM) and "Billing" meaning the amount that is actually billed assuming you have VMs that hit the cap specified in the report?
If so, that may need to be clarified, given that's a second definition of what allocated is in relation to vRAM reporting from vCloud UM. If not then ignore my rambling in this post.
According to VMware the report is working but the column headings are not great.
In the Aggregate Billing Report, there is a column called 'Total Allocated vRAM (GB-hour)'. This value is the aggregate of the 'billing ram' for each VM, not the 'allocated ram'. Hence the value should be the same as the 'Total Billed vRAM (GB-hour)' value, unless you have VMs that exceed the per-VM Memory Cap (24576MB).
The ‘Total Allocated vRAM (GB-Hour)’ column heading should really read something like ‘Total Billing vRAM (Uncapped GB-Hour)’ and the’Total Billed vRAM (GB-Hour)’ should really read something like ‘Total Billed vRAM (Capped GB-Hour)’.