For those that are interested, I was able to resolve this by doing the
following:
- Remove the "get_user_environment" attribute from the "jobs" attribute.
- Add an additional attribute to the "environment" attribute titled
"SLURM_GET_USER_ENV" and setting that equal to 1.
Example before change:
Chris,
Do you have a link to that code? Haven't had any luck finding that repo
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
Chris,
Any ideas on whether there's a way to mirror this functionality in v0.0.40?
Best regards,
Juan
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
Ole,
We are running version 24.05.1. The RPM package is
slurm-slurmrestd-24.05.0-1.el9
Best regards,
Juan
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
Ole,
I am referring to the REST API. We have had it installed for a few years and
have recently upgraded it so that we can use v0.0.40. But this most recent
version is missing the "get_user_environment" field which existed in previous
versions.
Best,
Juan
--
slurm-users mailing list -- slur
In previous versions (v0.0.36) of the REST API the job submission endpoint had
a field titled "get_user_environment"; however, it doesn't appear to exist in
v0.0.40. Is there an equivalent parameter that should be used? What is the
suggested approach for mimicking this behavior in v0.0.40?
Best
Good Afternoon All,
It does not seem that the REST API allows for folks to configure their jobs to
utilize GPUs, using the traditional methods. IE, there does not appear to be an
equivalent between the --gpus (or --gres) flag on sbatch/srun and the REST
API's job submission endpoint. Can anyone
