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
nixos/slurm: fix default module parameters, update documenation #41016
Conversation
Wether to enable the slurm control daemon. | ||
Note that the standard authentication method is "munge". | ||
The "munge" service needs to be setup up in order for | ||
slurm to work properly (see <literal>services.munge<literal>). |
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.
Would it be a good idea to enable munge
automatically?
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.
That would be a good idea. However, you need to provide a key file to the munge module to make it work.
Please add the |
@GrahamcOfBorg test slurm |
Success on x86_64-linux (full log) Attempted: tests.slurm Partial log (click to expand)
|
@@ -150,6 +169,8 @@ in | |||
|
|||
environment.systemPackages = [ wrappedSlurm ]; | |||
|
|||
services.munge.enable = true; |
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.
Should it be possible to use slurm
without munge
? If yes, please change the value to mkDefault true
so users can easily override it in their config.
However, you need to provide a key file to the munge module to make it work.
Can this change break existing configs that use slurm
without munge
? If yes, that should be documented in the release notes.
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.
You can run slurm
without munge
by turning off the authentication via extraConfig
.
If you do not set services.munge.enable=false
explicitly in that case, then this will result in the munged.service
to fail on startup (given that no service.munge.password
was provided).
I am not sure that this would really result in a breakage of an existing installation.
The way the slurm
module is coded now munge
is assumed to be there:
the slurmctld.service
specifies requires = [ "munged.service" ]
.
Munge is practially "hardcoded" into the nixos module already.
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.
Thanks for explaining. So there's no need for extra documentation.
Success on aarch64-linux (full log) Attempted: tests.slurm Partial log (click to expand)
|
build of nixos manual broke because of mismatched xml tags in an option description introduced in #41016.
Motivation for this change
Slurm's default process tracking facility is now cgroups. However, the lack of the
cgroups.conf
config files, required by slurm, breaks the test. I added the optionprocTrackType
to the module, setting thedefault to
proctrack/linuxproc
. This enables the minimal example of the test to run again.This PR follows the idea that a minimal setup configured through nix should be functional.
Integrating
cgroups.conf
requires an additional option in the module, since it is requiredto reside in the same directory as
slurm.conf
(will be part of a future PR).Things done
procTrackType
build-use-sandbox
innix.conf
on non-NixOS)nixos/tests/slurm.nix completes successfully
nix-shell -p nox --run "nox-review wip"
./result/bin/
)