rnigam
Contributor
Contributor

Strange vCPU value reported by Chargeback.

Hi All,

We are unable to understand how Chargeback is handling vCPU count variable. We did a small experiment where we had a machine with 1 vCPU and 2 GB of memory and 50GB HD running for like 24 hrs one day + 11 hrs in the next day using vCloud Director. We wanted to observe the behavior of what happens if the machine gets turned off in the middle and hence we turned it off after 11 hrs on the second day.

When I tried generating reports for those two dates (24-25 Apr and 25-26 Apr) individually, I got strange numbers in Chargeback Usage and Cost Reports for different billing policies.

vCPU numbers

Test2 vDC:

From 24’th April to 25’th April (was Turned on for 24 Hours)

Case 1: Billing Policy : if (vmpower=on) {usage;}

    Cost Report :                      $0.53

                Usage Report:                          1

Case 2: Billing Policy: usage;

                Cost Report:                       $0.72

                Usage Report:                           1

Case 3: Billing Policy: Allocation;

                Cost Report:                       $0.72

                Usage Report:                           1

Case 4: Billing Policy: if (vmpower=on) {Allocation;}

                Cost Report:                       $0.53

                Usage Report:                           1

From 25’th April to 26’th April (was Turned on for 11 Hours)

Case 1: Billing Policy : if (vmpower=on) {usage;}

    Cost Report :                      $0.17

                Usage Report:                          1

Case 2: Billing Policy: usage;

                Cost Report:                       $0.72

                Usage Report:                           1

Case 3: Billing Policy: Allocation;

                Cost Report:                       $0.72

                Usage Report:                           1

Case 4: Billing Policy: if (vmpower=on) {Allocation;}

                Cost Report:                       $0.17

                Usage Report:                           1

Seems like its rounding out the value of vcpu count in usage report in all cases to 1. We were expecting a numbeer close to 0.5 for the usage report when we used billing policy as usage for the second day.

Can someone please help me understand what is happening here and why are we not getting absolute fractional numbers for the vCPU count when we are clearly giving 'usage' as the  billing parameter for vCPU. We would really not like to bill the customer for the fraction he has not used at all.

FYI, the vCPU cost in the cost model is 0.015 USD/Count computed Hourly.

Thanks,

Rohan

Reply
0 Kudos