-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Enable CPU cap in VRs if the offering has a CPU cap limitation #7234
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
Conversation
Codecov Report
@@ Coverage Diff @@
## main #7234 +/- ##
============================================
- Coverage 12.95% 12.95% -0.01%
Complexity 8986 8986
============================================
Files 2728 2728
Lines 256647 256648 +1
Branches 40024 40024
============================================
Hits 33256 33256
- Misses 219214 219215 +1
Partials 4177 4177
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
Kudos, SonarCloud Quality Gate passed! |
DaanHoogland
left a comment
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.
CLGTM
|
@ezntt please comment on why you approve. Did you test/review and if test, how? |
|
Sure, @DaanHoogland, I approve the feature based on my testing, which was carried out using a similar approach to the PR owner. I tested the change by creating a VR and verifying its dumpxml to confirm that cpushares tag was set correctly. Specifically, I confirmed that the tag: were properly defined, which confirmed that the change was successful. |
weizhouapache
left a comment
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.
code lgtm
Great work @ezntt , we have a rule to have at least one lgtm based on code review and one lgtm based on 3rd party testing. Hence my question. |
stephankruggg
left a comment
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.
CLGTM, not manually tested
|
I have performed a manual test on 4.17.2 release and I observe that cpu cap is honoured Let me know if any step is missing in reproducing the issue ? Steps that I have followed
Login to the kvm host where the router is running and execute virsh dumpxml <>
Observer the cpushare tag is present virsh dumpxml <> |
|
@blueorangutan package |
|
@DaanHoogland a [SF] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 6127 |










Description
When deploying a new VR, using a network offering with CPU cap, this limitation is not respected in the VR, because in the definition and persistence of VR in database, the configuration of CPU cap of the network offering is not considered, and always uses the value
false. This PR aims to fix this behavior, to respect the CPU cap of the network offering.Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
It was tested in a local lab:
dumpxmlin the VR definition;