-
Notifications
You must be signed in to change notification settings - Fork 109
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
feat: node resource topology scheduler plugin #298
feat: node resource topology scheduler plugin #298
Conversation
fc46d5b
to
c74515d
Compare
cf48b9c
to
d292543
Compare
48b985c
to
16fe377
Compare
@caohe pls take your time to confirm whether we can merge this pr |
Sure, we can merge this pr first kubewharf/enhanced-k8s#12 |
enhanced-k8s has been merged, but the api still requires another approve, so you may need to approve that firstly @caohe |
16fe377
to
3690c5e
Compare
return []framework.ClusterEvent{ | ||
{Resource: framework.Pod, ActionType: framework.Delete}, | ||
{Resource: framework.Node, ActionType: framework.Add | framework.UpdateNodeAllocatable}, | ||
{Resource: framework.GVK(nrtGVK), ActionType: framework.Add | framework.Update}, |
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.
Is this CRD nrt or cnr?
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.
Is this CRD nrt or cnr?
cnr, it has been updated
"github.com/kubewharf/katalyst-core/pkg/scheduler/util" | ||
) | ||
|
||
func (tm *TopologyMatch) Reserve(ctx context.Context, state *framework.CycleState, pod *corev1.Pod, nodeName string) *framework.Status { |
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.
How do we implement "pessimistic allocation" if multiple numa nodes are needed?
What type of PR is this?
Enhancements
What this PR does / why we need it:
add topologyMatch plugin to support topology-aware scheduling for both nativePolicy and dynamicPolicy
nativePolicy + single-numa-node,
dynamicPolicy + dedicated_cores + numaBinding + single-numa-node,
dynamicPolicy + dedicated_cores + numaBinding + numaExclusive + single-numa-node,
dynamicPolicy + dedicated_cores + numaBinding + numeric,
dynamicPolicy + dedicated_cores + numaBinding + numaExclusive + numeric
are supported.
Which issue(s) this PR fixes:
#160