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
We're currently investigating how to reduce the amount of boilerplate our users have to deal with. Allowing them to set custom defaults in $HOME/.slurm/default which are picked up by the cli_filter/user_defaults plugin is an interesting option. Pyxis' arguments, mostly container-image and container-mounts, are great candidates here.
Unfortunately, the plugin only deals with standard Slurm arguments, not those added by SPANK plugins. After scanning slurm_opt_t, srun_opt_t etc. I came to the conclusion that plugin-specific arguments are simply not accessible there. They seem to be buried somewhere deep inside srun. The only possible point of interaction I see is through manipulation of the job environment (or potentially slurm_opt_t->spank_job_env, though I don't know what that actually does), i.e., cli_filter/user_defaults could be patched to add some Pyxis-specific env vars to hold the defaults.
So I guess I have two questions:
Did I overlook something, and this is actually very easy to achieve?
What are the chances that Pyxis might add support for reading arguments from env vars like PYXIS_CONTAINER_IMAGE?
ps: Don't hesitate to close this if you feel it's a silly request/outside your jurisdiction/...
The text was updated successfully, but these errors were encountered:
Hello Pyxis people,
We're currently investigating how to reduce the amount of boilerplate our users have to deal with. Allowing them to set custom defaults in
$HOME/.slurm/default
which are picked up by thecli_filter/user_defaults
plugin is an interesting option. Pyxis' arguments, mostlycontainer-image
andcontainer-mounts
, are great candidates here.Unfortunately, the plugin only deals with standard Slurm arguments, not those added by SPANK plugins. After scanning
slurm_opt_t
,srun_opt_t
etc. I came to the conclusion that plugin-specific arguments are simply not accessible there. They seem to be buried somewhere deep inside srun. The only possible point of interaction I see is through manipulation of the job environment (or potentiallyslurm_opt_t->spank_job_env
, though I don't know what that actually does), i.e.,cli_filter/user_defaults
could be patched to add some Pyxis-specific env vars to hold the defaults.So I guess I have two questions:
PYXIS_CONTAINER_IMAGE
?ps: Don't hesitate to close this if you feel it's a silly request/outside your jurisdiction/...
The text was updated successfully, but these errors were encountered: