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
Currently for the immediate binding case we have two scheduling logic
Volumeweighted, here we pick the node where less number of volumes are provisioned
CapacityWeighted here we pick the node where size of all the provisioned volumes are less
These 2 are not sufficient as there is a possibility of getting a node where enough space is not availabe as none of above scheduling logic look for the free space available in the volumegroup.
Now that since we have lvmnode CR which has all the information about the volume group. We can use that to find the best node. We need to create a node map (
This is also a problem with heterogenous clusters, where some nodes don't (yet) have the VG created.
openebs-lvm-controller keeps trying to create the volume on a node where the volume group doesn't even exist, and keeps failing (and also doesn't seem to take taints into consideration, preventing a pod from getting scheduled there).
This is also a problem with heterogenous clusters, where some nodes don't (yet) have the VG created.
openebs-lvm-controller keeps trying to create the volume on a node where the volume group doesn't even exist, and keeps failing (and also doesn't seem to take taints into consideration, preventing a pod from getting scheduled there).
@flokli , We have created an enhancement ticket #312. It has some additional suggestions also. Please take a look.
Currently for the immediate binding case we have two scheduling logic
These 2 are not sufficient as there is a possibility of getting a node where enough space is not availabe as none of above scheduling logic look for the free space available in the volumegroup.
Now that since we have lvmnode CR which has all the information about the volume group. We can use that to find the best node. We need to create a node map (
lvm-localpv/pkg/driver/schd_helper.go
Line 96 in d4c4beb
The schedule currently picks the node which one less weighted(https://github.com/openebs/lib-csi/blob/develop/pkg/scheduler/scheduler.go#L81) in the map, we need to modify it to pick the highest weighted node as here we need to pick the node where free space is more.
The text was updated successfully, but these errors were encountered: