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 regards,
Juan
On 14-08-2024 19:52, jpuerto--- via slurm-users wrote:
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?
What software are you referring to with the mentioned versions? REST prerequisites are listed in https://slurm.schedmd.com/rest_quickstart.html
/Ole
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
On 15-08-2024 15:04, jpuerto--- via slurm-users wrote:
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.
Yes, but what is the name of the RPM package (or similar package) that you have installed and whose versions you refer to?
/Ole
Ole,
We are running version 24.05.1. The RPM package is slurm-slurmrestd-24.05.0-1.el9
Best regards,
Juan
On 8/15/24 7:04 am, jpuerto--- via slurm-users wrote:
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.
I had a look at the code in Slurm 23.11 and it looks like it is in the v0.0.38 but not in the v0.0.39 version there. It looks like the code was restructured significantly around that time, so I'm not competent to say if this is because it moved elsewhere and I'm not seeing it, or if it got dropped then.
Chris,
Any ideas on whether there's a way to mirror this functionality in v0.0.40?
Best regards,
Juan
Chris,
Do you have a link to that code? Haven't had any luck finding that repo
https://github.com/SchedMD/slurm/blob/ffae59d9df69aa42a090044b867be660be2596...
but no longer in
https://github.com/SchedMD/slurm/blob/slurm-23.02/src/plugins/openapi/v0.0.3...
Which underwent major revision
In the next openapi version
On 22/08/2024 21:18:35, jpuerto--- via slurm-users wrote:
Chris,
Do you have a link to that code? Haven't had any luck finding that repo
On 22/8/24 11:18 am, jpuerto--- via slurm-users wrote:
Do you have a link to that code? Haven't had any luck finding that repo
It's here (on the 23.11 branch):
https://github.com/SchedMD/slurm/tree/slurm-23.11/src/slurmrestd/plugins/ope...
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:
{ "job": { "get_user_environment": 1 } }
Example after change: { "job": { "environment": { "SLURM_GET_USER_ENV": 1 } } }
Is anyone in contact with the development team? I feel that this is pretty basic functionality that was removed from the REST API without warning. Considering that this was a "patch" release (based on traditional semantic versioning guidelines), this type of modification shouldn't have happened and makes me worry about upgrading in the future.
Best regards,
Juan
On 27/8/24 10:26 am, jpuerto--- via slurm-users wrote:
Is anyone in contact with the development team?
Folks with a support contract can submit bugs at https://support.schedmd.com/
I feel that this is pretty basic functionality that was removed from the REST API without warning. Considering that this was a "patch" release (based on traditional semantic versioning guidelines), this type of modification shouldn't have happened and makes me worry about upgrading in the future.
Slurm hasn't used semantic versioning for a long time, they moved to a year.month.minor version system a long time ago. The major releases are (now) every 6 months, so the most recent ones have been:
* 23.02.0 * 23.11.0 (old 9 month system) * 24.05.0 (new 6 month system)
Next major release should be in November:
* 24.11.0
All the best, Chris
Actually this is not Slurm versioning strictly speaking, this is openapi versioning - the move from 0.0.38 to 0.0.39 also dropped this particular endpoint.
You will notice that the same major Slurm version supports different API versions.
On 28/08/2024 03:02:00, Chris Samuel via slurm-users wrote:
On 27/8/24 10:26 am, jpuerto--- via slurm-users wrote:
Is anyone in contact with the development team?
Folks with a support contract can submit bugs at https://support.schedmd.com/
I feel that this is pretty basic functionality that was removed from the REST API without warning. Considering that this was a "patch" release (based on traditional semantic versioning guidelines), this type of modification shouldn't have happened and makes me worry about upgrading in the future.
Slurm hasn't used semantic versioning for a long time, they moved to a year.month.minor version system a long time ago. The major releases are (now) every 6 months, so the most recent ones have been:
- 23.02.0
- 23.11.0 (old 9 month system)
- 24.05.0 (new 6 month system)
Next major release should be in November:
- 24.11.0
All the best, Chris
-
Chris Samuel -
Christopher Samuel
-
Daniel Letai -
jpuerto＠psc.edu -
Ole Holm Nielsen