set submit to fail on "none" pool

Deadline
1

Would it be possible to have job submissions fail when the user selects the “none” pool on purpose?

Our setup is such that in addition to a dedicated server farm, workstations are also harnessed to render when rendertime is tight - but we don’t have a homogenous workstation setup (licensing, of course). So the pools are jiggered so that different workstations are in different pools depending on the software installed.

Some users, in a misguided attempt to “game” the system, have opted to use the “none” pool as that will grab all the slaves when there are no other jobs on the queue.

To return to the question then: can job submissions be triggered to fail with the use of the “none” pool?

Regards,

Ron Santos
I.T.
Real Image

2

Hi Ron,

There isn’t a built-in system for this. You could edit the submission script(s) you use to remove ‘none’ from the list of choices, but that requires manual work.

In Deadline 5.1, there will be a new Slave setting that you can turn on to prevent certain slaves from picking up jobs in the “none” pool or group. This should help you achieve what you’re looking for. Deadline 5.1 should be released mid-December, but if you would like to upgrade now, we are still accepting beta requests:
viewtopic.php?f=10&t=5919

Cheers,

  • Ryan