phsm commented on issue #7591: URL: https://github.com/apache/cloudstack/issues/7591#issuecomment-1584587876
@NuxRo Thanks for reviewing this bug report. I think you've misunderstood what is the actual bug is here. The bug is that the overprovisioning factor is affecting the cloudstack_host_cpu_usage_mhz_total metric when you change the overprovisioning factor while it shouldn't. 1. Lets consider you have overprovisioning factor 10. 2. When you start a VM with 2 cores, 2000Mhz on an empty hypervisor, then the metric cloudstack_host_cpu_usage_mhz_total for that hypervisor will show you the value of 2000. This is correct behavior: the metric shows you the real usage, not multiplied by overprovisioning factor. 3. When you **change** the overprovisioning factor while the VM is running, the metric values becomes multiplied on what seems to be `(new_overprovision_factor - old overprovision_factor)` So this is inconsistency in the behavior: usage metric is not affected by overprovisioning factor when you start a VM. When you change the overprovisioning factor, then the VM usage becomes affected by overprovisioning factor. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
