scheduler: fix that cpu should be preferred if numa policy is restricted #2033
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ⅰ. Describe what this PR does
When pods request multi resources, and some of these resources need to be placed on 2 numa nodes and some other resources can be placed on 1 numa node, the pods can not be scheduled. This PR solve the problem by set preferred property to true for restricted policy and cpu resource to solve the problem.
Ⅱ. Does this pull request fix one issue?
Ⅲ. Describe how to verify it
Label a node that have 2 numa nodes with
node.koordinator.sh/numa-topology-policy=restricted
and create a pod that request 2 cpus and all gpu cards on node. The pod will be pending.Ⅳ. Special notes for reviews
V. Checklist
make test