Skip to content

Feature/resource reservation (#380) - #404

Merged
gyptazy merged 3 commits into
mainfrom
feature/373-add-resource-reservation-for-nodes
Dec 24, 2025
Merged

gyptazy merged 3 commits into
mainfrom
feature/373-add-resource-reservation-for-nodes

Conversation

@gyptazy

@gyptazy gyptazy commented Dec 23, 2025 •

Copy link
Copy Markdown
Owner

Add resource reservation of memory for nodes (by @Chipmonk2)

Comitted by: @Chipmonk2 via #380
Fixes: #373

Add resource reservation of memory for nodes
@gyptazy gyptazy added this to the Release 1.1.11 milestone Dec 23, 2025
@gyptazy gyptazy self-assigned this Dec 23, 2025
@gyptazy
gyptazy force-pushed the feature/373-add-resource-reservation-for-nodes branch from 8aff2e8 to 8499b3e Compare December 23, 2025 14:27
@gyptazy
gyptazy force-pushed the feature/373-add-resource-reservation-for-nodes branch 2 times, most recently from c742458 to 636763f Compare December 24, 2025 07:41
@gyptazy

gyptazy commented Dec 24, 2025 •

Copy link
Copy Markdown
Owner Author

Hey @Chipmonk2,

I made some additional changes to this PR. It is now directly integrated into the maxmem evaluation of the node and simply returns the adjusted values by the reservation values from the given config or simply return the API values. I also "simplified" the code functions. This way, we also do not need to re-evaluate the percentage values an can immediately also use it for cpu and disks.

Have a nice day and thanks again for this PR!

Thanks,
gyptazy

  - Renamed to set_node_resource_reservation
  - Immediately apply the values as maxmem for a node
    - Avoid recalculating percentage values
  - Simplified code
  - Adjusted debug logging
@gyptazy
gyptazy force-pushed the feature/373-add-resource-reservation-for-nodes branch from 636763f to e0331e8 Compare December 24, 2025 08:07
@gyptazy
gyptazy merged commit 15a05d3 into main Dec 24, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature: Add Threshold to avoid overloading a node (Memory)

2 participants