VM Metrics CPU Utilisation Percentage | CPU Cap enabled Compute Offering
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 32
Description
##### ISSUE TYPE
* Enhancement Request
##### COMPONENT NAME
~~~
UI CPU Metrics
~~~
##### CLOUDSTACK VERSION
~~~
4.18.1
~~~
##### CONFIGURATION
##### OS / ENVIRONMENT
KVM on Ubuntu 20.04
##### SUMMARY
On Deploying a VM with CPU CAP enabled offering, the CPU usage Metrics Not Hitting 100%, Its considering Actual Usage not the wait/steal time. Ideally It should be Usage + Steal+wait...
CPU Based auto scaling on above VM will also be affected by this.
##### STEPS TO REPRODUCE
~~~
1. Create compute offering with a lower CPU speed with CPU Cap Enabled
2. Deploy A VM with this offering
3. Induce stress in VM using stress command to utilize 100% CPU
4. Observe CPU Metrics
5. CPU Percentage not hit 100%
~~~
##### EXPECTED RESULTS
~~~
CPU Percentage should show 100%
~~~
##### ACTUAL RESULTS
~~~
CPU Percentage Incorrect
~~~
Contributor guide
Research direction
Reproduce the behavior with a CPU-capped compute offering on KVM and a VM running the listed stress command, then inspect how CloudStack's UI CPU metrics are calculated. Done means the displayed CPU percentage reaches the expected 100% under the described workload and CPU-based autoscaling is no longer affected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, ubuntu
- Domain
- cloud, infrastructure, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100