Assume we have a queue (queueA) that has a custom resource called “condo” and this queue has a “max_run_res.condo” settings of 10.
Now assume job submissions do not specify “condo=N” in their select statements.
How would you go about enforcing a restriction on queueA such that the total number of nodes with the custom resource “condo” which are running jobs from queueA is limited to 10?
Put another way, whenever a job lands on a node that provides that condo resource, the scheduler must account for that node as “running_res.condo” node.
Please let us know if this possible and what approaches we could explore.