Github user jayakarteek commented on the issue:
https://github.com/apache/cloudstack/pull/1918
@rafaelweingartner
The CPU.Reservation value by **default** is 0, Also the value is set in
VMware not from the ACS UI.
this gives ambiguity about the CPU allocated and Utilised.
Use case 1 :
CPU.Reservation is 0 by default, In this case we cannot calculate % as the
value is always zero.
Use case 2:
CPU.Reservation is set by VMware admin say 500Mhz.
But while creating vm-instance using ACS UI , admin selected service
offering as Medium Instance which is 1Ghz CPU. so CPU utilisation will be wrong.
In case say cloud environment has 30 instances , then Vmware admin has to
manually set the CPU.Reservation value for each of the VM Instance which is
cumbersome.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
