Description of problem: Sometimes all the machines are blocked for a long time due to e.g.: - bad habit of including reservesys at the end of all tasks - people submitting same jobs multiple times - people holding machines reserved - or just too big load It is often legal usage, so can not be banned/prevented in general. We need to apply some level of self-control: I/we can not run more jobs: have to release some machines... Solution(?): Implement recipe quotas, so one user/group does not block all machines for a long time whatever their job priority is. This would require a "sudo"/rungroup command to allow user to pick a group for a job if he is a member of multiple groups.
Bulk reassignment of issues as Bill has moved to another team.
The current scheduler isn't clever enough to have different quotas based on which systems they're using, but we could potentially limit access to the *general* pool this way. Anything more sophisticated would need to wait until we're able to switch to a more sophisticated scheduling engine.
This is on hold until we evaluate the possibility of switching to a more capable scheduling engine.
If we decide to pursue a simpler scheme that only limits access to the general pool, that will be filed as a separate RFE based on usage analysis of Red Hat's main Beaker instance. It's a tricky problem, since preliminary checks of an OS build are *supposed* to spin up hundreds of recipes in a relative short span of time.