Use slurmd's own detection for node definition #96
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.
Currently the node definitions are constructed using ansible facts. At least in some situations this doesn't appear entirely satisfactory to slurm, e.g.
slurmd -C
shows... Boards=1 ...
and nodes are getting set DOWN.This PR runs
slurmd -C
on all compute nodes, then uses values from the first-in-play in each partition (iaw existing logic) to provide node definitions.This is sort of Trust On First Use that the node configuration is in fact correct.
An alternative is only to specify NodeName and not the expected CPU parameters at all:
This would have 2x disadvantages:
Quotes from https://slurm.schedmd.com/slurm.conf.html.