-
Notifications
You must be signed in to change notification settings - Fork 1
ENH: Add support for PCPUs #29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #29 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 111 111
Lines 4111 4147 +36
=========================================
+ Hits 4111 4147 +36 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Identified an inconsistency, debugging, draft for now |
It's just been combined into the existing VCPUs field + more aliases adding
Addition of pcpus to vcpus is backwards-compatibile
|
Fixed: small typo from vscode autocomplete autocompleting the wrong variable |
| HypervisorProperties.VCPUS: lambda a: a.usage.vcpus + a.usage.pcpus, | ||
| HypervisorProperties.VCPUS_AVAIL: lambda a: a.usage.vcpus_avail | ||
| + a.usage.pcpus_avail, | ||
| HypervisorProperties.VCPUS_USED: lambda a: a.usage.vcpus_used | ||
| + a.usage.pcpus_used, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if we should be combining PCPU and VCPU like this since they are two different resources in openstack, its only our specific use case where we only use PCPUs that we run into this issue. I'd suggest return separate fields for PCPU and VCPU and let the users of the library decided how to handle them
It's just been combined into the existing VCPUs field + more aliases adding
Tested on dev: Works. No longer do hypervisors show 0 vCPUs