-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Implement spreading allocations based on a target node attribute #4527
Merged
Merged
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
7e9553c
Structs and validation for spread
7814c3b
Validate method, and rename ratio field to percent
5fa4620
Implement spread iterator that scores according to percentage of desi…
f3024ff
Fix warnings
090e0b7
Include spreads configured at job level when precomputing weights/des…
0b1d0b0
validate spread from job/task group validate methods
aa621a4
Allow empty spread targets, and validate target percentages.
dcd329e
fix comments
6c9a9fb
Support implicit spread target to account for remaining desired counts
3ab38b6
Implement support for even spread across datacenters, with unit test
9246f92
Remove hardcoded boosts for even spread.
9d73c2f
fix scoring algorithm when min count == current count
2f9bf27
comment and formatting cleanup
402934c
added some unit tests for -1 spread score
746601a
more cleanup
d8b5ec2
Fix scoring logic for uneven spread to incorporate current alloc count
383a4be
fix linting error
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Will it be possible to specify on job level and have the same behavior as
update{}
where it cascade / inherit down fromjob -> spread
tojob -> group -> spread
?Similar question for
affinity{}
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.
@jippi yes this and affinities both work similar to the update stanza and cascade down.