koord-scheduler: implement NodeNUMAResource plugin with CPUSet scheduling (#289)

This plugin extends the PreFilter/Filter/Score/Reserve/PreBind interfaces.

- Support LSE/LSR Pods to configure FullPCPUs and SpreadByPCPUs policies
  to apply for NUMA-Aware CPUSet.
- Supports configuring MostAllocated or LeastAllocated policies during
  scoring phase to select nodes that meet CPUBindPolicy requirements.

Signed-off-by: Joseph <joseph.t.lee@outlook.com>

Author: eahydra

cmd/koord-scheduler/main.go

@@ -26,6 +26,7 @@ import (
 	"github.com/koordinator-sh/koordinator/cmd/koord-scheduler/app"
 	"github.com/koordinator-sh/koordinator/pkg/scheduler/plugins/compatibledefaultpreemption"
 	"github.com/koordinator-sh/koordinator/pkg/scheduler/plugins/loadaware"
+	"github.com/koordinator-sh/koordinator/pkg/scheduler/plugins/nodenumaresource"
 
 	// Ensure scheme package is initialized.
 	_ "github.com/koordinator-sh/koordinator/apis/scheduling/config/scheme"
@@ -39,6 +40,7 @@ func main() {
 	// used by various kinds of workloads.
 	command := app.NewSchedulerCommand(
 		app.WithPlugin(loadaware.Name, loadaware.New),
+		app.WithPlugin(nodenumaresource.Name, nodenumaresource.New),
 		app.WithPlugin(compatibledefaultpreemption.Name, compatibledefaultpreemption.New),
 	)
 

docs/proposals/scheduling/20220530-fine-grained-cpu-orchestration.md

@@ -343,7 +343,7 @@ We use [NodeResourceTopology](https://github.com/k8stopologyawareschedwg/noderes
 
 ##### Compatible
 
-In order to be compatible with the existing NodeResourceTopology instances and prevent koordlet from conflicting with existing components, when koordlet creates a NodeResourceTopology, add the prefix `koord-` before the name to distinguish it, and add the label `app.kubernetes.io/managed-by=Koordinator` describes the node is managed by Koordinator.
+The koordlet creates or updates NodeResourceTopology periodically. The name of NodeResourceTopology is same as the name of Node. and add the label `app.kubernetes.io/managed-by=Koordinator` describes the node is managed by Koordinator.
 
 ##### Extension
 
@@ -466,7 +466,7 @@ metadata:
       ]
   labels:
     app.kubernetes.io/managed-by: Koordinator
-  name: koord-node1
+  name: node1
 topologyPolicies: ["SingleNUMANodePodLevel"]
 zones:
   - name: node-0