[slurm-users] SLURM reservations with MAGNETIC flag

[Bas van der Vlies]

Thanks Troy,

 That is our intention also for course/training purposes if there are course days.

regards


--
Bas van der Vlies
| Operations, Support & Development | SURFsara | Science Park 140 | 1098 XG  Amsterdam
| T +31 (0) 20 800 1300  | bas.vandervlies at surf.nl | www.surf.nl |




> On 25 Sep 2020, at 17:03, Baer, Troy <troy at osc.edu> wrote:
> 
> I've been looking at it for classroom type reservations, but I ran into a bug where jobs that weren't eligible to access the reservation were being attracted to it anyway.  That's supposed to be fixed in 20.02.6.  See https://bugs.schedmd.com/show_bug.cgi?id=9593 for details.
> 
> 	--Troy
> 
> On 9/25/20, 10:49 AM, "slurm-users on behalf of Bas van der Vlies" <slurm-users-bounces at lists.schedmd.com on behalf of bas.vandervlies at surf.nl> wrote:
> 
>    Are people using the MAGNETIC reservation flag? My question would be how? because to my it would be more useful if the reservation is tried first and then the free nodes. 
>    That is what I expected with the MAGNETIC flag.
> 
> 
>    Bas van der Vlies
>    | Operations, Support & Development | SURFsara | Science Park 140 | 1098 XG  Amsterdam
>    | T +31 (0) 20 800 1300  | bas.vandervlies at surf.nl | https://urldefense.com/v3/__http://www.surf.nl__;!!KGKeukY!mRT6FSlug4OBODiqDnysihd41efy6vwp4wT9pmdFkOUqPDR0jy3l6d-gzG2P$  |
> 
> 
> 
> 
>> On 24 Sep 2020, at 12:16, Bas van der Vlies <bas.vandervlies at surf.nl> wrote:
>> 
>> We have installed slurm 20.02.5 and I am trying to use this new reservation flag
>> MAGNETIC:
>> * https://urldefense.com/v3/__https://slurm.schedmd.com/reservations.html__;!!KGKeukY!mRT6FSlug4OBODiqDnysihd41efy6vwp4wT9pmdFkOUqPDR0jy3l6VfveQgB$ 
>> 
>> From this page I understand that the job will land in the reservation even if we
>> did not specify the 
>> reservation name.  I tested it on our cluster setup but it does not seems to
>> work as expected
>> 
>> I create a reservation for 1 node for user bas with flag magnetic. I submit a
>> job and to my surprise the job is scheduled on a free node and not on the node
>> in the reservation. It is only scheduled in the reservation if all nodes are
>> occupied. Is this the default behaviour or did a miss a setting?
>> 
>> I have set all available nodes offline except the reservation node and then I
>> see this:
>> ```
>> bas at batch2:~/src$ srun -N1 --pty /bin/bash
>> srun: Required node not available (down, drained or reserved)
>> srun: job 1713 queued and waiting for resources
>> srun: job 1713 has been allocated resources
>> ```
>> 
>> From this I see that the "magentic" reservation is considered as last.
>> 
>> 
>> regards
>> 
>> -- 
>> --
>> Bas van der Vlies
>> | Operations, Support & Development | SURF | Science Park 140 | 1098 XG 
>> Amsterdam
>> | T +31 (0) 20 800 1300 | bas.vandervlies at surf.nl | https://urldefense.com/v3/__http://www.surf.nl__;!!KGKeukY!mRT6FSlug4OBODiqDnysihd41efy6vwp4wT9pmdFkOUqPDR0jy3l6d-gzG2P$ 
> 
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4182 bytes
Desc: not available
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20200925/b744aa0a/attachment-0001.bin>