Hey Hendryk,
You wrote
this is obviously a solution, thank you. But one question to clarify things: your partitions 'devel' and 'devcore' use the nodes m[209-213] at daytime while these nodes are put into the partitions 'node' and 'core' at night and weekend. What if a user starts a job in the 'core' partition at e.g. 08:30 and uses exactly the nodes m[209-213]? Does the reservation block such jobs whenever the runtime is too long such that it conflicts with the "partition switch at 9 o'clock"?
The reservation blocks such jobs from overlapping the reservation on those nodes. That is the very reason for adding the reservations. I can mention that I also added an "alternate" field to the devel and devcore partition definitions, like this: PartitionName=devel Nodes=m[209-213] Shared=EXCLUSIVE DefaultTime=00:00:01 MaxTime=60 MaxNodes=10 Alternate=node State=UP PartitionName=devcore Nodes=m[209-213] Shared=NO DefaultTime=00:00:01 MaxTime=60 MaxNodes=10 Alternate=core State=UP That might help some users, when there are no available devel and devcore nodes, but I presume that this addition would be of no use in your scenario. Best wishes, -- Lennart Karlsson, UPPMAX, Uppsala University, Sweden http://www.uppmax.uu.se/
