Re: [slurm-users] Setting up slurmrestd

2021-01-08 Thread Karl Lovink
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I'm trying to configure slurmrestd but I haven't been very successful so far. The plan is to use splunk to approach the endpoints. To test the communication with slurmrestd I am now using curl. However, I always get "Authentication failure" b

Re: [slurm-users] Setting up slurmrestd

2021-01-08 Thread Karl Lovink
Hi Luke, Thanks it’s working now. Thanks. One last question, is it possible to create a non-expiring token. Yes, I know it is not secure Sincerely yours, Karl > On 8 Jan 2021, at 20:25, Luke Yeager wrote: > >  > There's this: https://slurm.schedmd.com/rest.html > > From my personal no

Re: [slurm-users] Upcoming Slurm 20.11.3 release will revert to older step launch semantics

2021-01-08 Thread Ionel GARDAIS
Hi Tim, We dive into Slurm starting with 20.11.0 and IntelMPI. We faced pinning issues with mpirun that did not exist when using directly srun. Then we hit the wall with the 20.11.1 and the PMI issue. It led us to try the 20.02.6 which solved both the PMI issue and the pinning issue with mpirun

Re: [slurm-users] Setting up slurmrestd

2021-01-08 Thread Luke Yeager
There's this: https://slurm.schedmd.com/rest.html From my personal notes: • Install these packages before re-compiling Slurm (ubuntu 20.04): libhttp-parser-dev, libjwt-dev, and libyaml-dev • Setup JWT using these instructions: https://slurm.schedmd.com/jwt.html • Create /etc/slu

[slurm-users] Upcoming Slurm 20.11.3 release will revert to older step launch semantics

2021-01-08 Thread Tim Wickberg
Hey folks - As some of you have observed, one of the changes made in the Slurm 20.11 release was to the semantics for job steps launched through the 'srun' command. This also inadvertently impacts many MPI releases that use srun underneath their own mpiexec/mpirun command. For 20.11.{0,1,2}