koordinator
koordinator copied to clipboard
proposal: support pod customizing numa policy
Ⅰ. Describe what this PR does
Introduce new api for pod level numa topology policy. With the new api, users can specify numa topology policy for each pod, so that pods that are more sensitive to latency can decide how they need to be orchestrated, rather than being passively scheduled according to the numa topology policy on the node.
Ⅱ. Does this pull request fix one issue?
Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist
- [ ] I have written necessary docs and comments
- [ ] I have added necessary unit tests and integration tests
- [ ] All checks passed in
make test
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 67.47%. Comparing base (
da6a05c
) to head (23f7ce6
). Report is 44 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #1910 +/- ##
==========================================
+ Coverage 67.23% 67.47% +0.24%
==========================================
Files 407 420 +13
Lines 45644 46858 +1214
==========================================
+ Hits 30687 31617 +930
- Misses 12741 12938 +197
- Partials 2216 2303 +87
Flag | Coverage Δ | |
---|---|---|
unittests | 67.47% <ø> (+0.24%) |
:arrow_up: |
Flags with carried forward coverage won't be shown. Click here to find out more.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
BTW, please fix DCO by git commit -s.
/lgtm
/lgtm
@hormes Hi, is there any questions for this proposal? If not we can start to implement the new feature. Please take a look if you have time, thanks.
@hormes Hi, is there any questions for this proposal? If not we can start to implement the new feature. Please take a look if you have time, thanks.
LGTM. /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hormes
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [hormes]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment