Feature #11146
Updated by Tom Clegg about 7 years ago
h3. Background
From the user's perspective, it's hard to see what (if anything) is happening between the time a container is created/queued and the time it actually starts running.
In a SLURM setup, the container typically moves quickly from Queued to Locked state when crunch-dispatch-slurm puts it in the slurm queue, and then stays there for some time waiting for SLURM resources to run it.
h3. Proposed feature
Soon after a container is submitted to the SLURM queue, Workbench should start indicating how close the resulting SLURM job is to the front of the queue.
h3. Implementation
When checking squeue, crunch-dispatch-slurm should notice the slurm queue position for each "Locked" container, and propagate this information to the API server.
* Add a new serialized field @dispatch_info@ with a @queue_position@ key
Workbench should display the latest queue position when available.