You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
undeploy: ## Undeploy controller from the K8s cluster specified in ~/.kube/config. Call with ignore-not-found=true to ignore resource not found errors during deletion.
Copy file name to clipboardExpand all lines: cloud/scheduler/README.md
+30-2Lines changed: 30 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,12 @@ Basic flow of the node selection process is `filter => score => select one node
8
8
9
9
### Filter Plugins
10
10
11
-
Filter plugins filter the node based on nodename, overcommit ratio etc.
11
+
Filter plugins filter the node based on nodename, overcommit ratio etc. So that we can avoid to run qemus on not desired Proxmox nodes.
12
+
13
+
-[NodeName plugin](./plugins/nodename/node_name.go) (pass the node matching specified node name)
14
+
-[CPUOvercommit plugin](./plugins/overcommit/cpu_overcommit.go) (pass the node that has enough cpu against running vm)
15
+
-[MemoryOvercommit plugin](./plugins/overcommit/memory_overcommit.go) (pass the node that has enough memory against running vm)
16
+
-[NodeRegex plugin](./plugins/regex/node_regex.go) (pass the node matching specified regex)
12
17
13
18
#### regex plugin
14
19
@@ -20,11 +25,17 @@ value(example): node[0-9]+
20
25
21
26
### Score Plugins
22
27
23
-
Score plugins score the nodes based on resource etc.
28
+
Score plugins score the nodes based on resource etc. So that we can run qemus on the most appropriate Proxmox node.
29
+
30
+
-[NodeResource plugin](./plugins/noderesource/node_resrouce.go) (nodes with more resources have higher scores)
31
+
-[Random plugin](./plugins/random/random.go) (diabled by default. just a reference implementation of score plugin)
24
32
25
33
## How to specify vmid
26
34
qemu-scheduler reads context and find key registerd to scheduler. If the context has any value of the registerd key, qemu-scheduler uses the plugin that matchies the key.
27
35
36
+
-[Range plugin](./plugins/idrange/idrange.go) (select minimum availabe vmid from the specified id range)
You can specify vmid range with `(start id)-(end id)` format.
30
41
```sh
@@ -64,4 +75,21 @@ spec:
64
75
metadata:
65
76
annotations:
66
77
node.qemu-scheduler/regex: node[0-9]+ # this annotation will be propagated to your ProxmoxMachine via MachineSet
78
+
```
79
+
80
+
## How to configure (or disable/enable) specific Plugins
81
+
82
+
By default, all the plugins are enabled. You can disable specific plugins via plugin-config. for CAPPX, check example ConfigMap [here](../../config/manager/manager.yaml)
0 commit comments