UBL limits don't update immediately

Deadline
1

I just set the UBL limit to 0 and it’s still using licenses when I requeue the slaves.

Also the old bug of unchecking “Use UBL” and rechecking it resets the license application type so uncheck that is a poor option.

Name Status Stubs In Use Stub Limit Usage Level WhiteList Return At Task Progress Stub Holders Limit Overage Use Third Party UBL License Application Licensed Per Core nuke_r In Use 3 0 Slave Yes 0 % render-vm-03, render-vm-04, render-vm-01 0 True nuke No

This in spite of Overage set to 0.

2

AughhhH! this is by design!

This doesn’t work at all. This has to change. This makes usage based impossible. Because if I turn off usage based… suddenly I supposedly have infinite permanent licenses which is the opposite of the truth. We have 0 perm render licenses so when I set the overage usage to 0 (I don’t want to use overage) it suddenly starts hammering our interactive licenses and then errors out. The choice shouldn’t be between UBL expenses and Infinite permanent.

3

Hey Gavin,

So just to make sure I understand what behavior you would like to see:

  1. If “Use third party licensing” is disabled, then a limit of zero and overage of zero means an unlimited limit (current functionality)

  2. If “Use third party licensing” is enabled, then a the limit corresponds to how many permanent license you have an overage represents how many slaves you are willing to let use UBL. If Limit is 0, and overage is not, then all slaves will use overage (current functionality)

  3. If"Use third party licensing" is enabled, and both limit and overage are zero, then the limit is impossible to check out, instead of being unlimited, and slaves will not be able to pick up jobs that require this limit (functionality would be added)

How does that sound?

4

I would just add a checkbox to both settings for consistency so that the user isn’t expected to understand that “0” means “infinity” sometimes but not other times depending on whether another one setting is also 0 (which may or may not be infinity depending on yet another 0).

This is effectively a 0 vs Null situation so I would just explicitly have an “No Limit” option everywhere instead of 0 being either 0 or Null depending on circumstance.

So I would change 1 to be 0 always being 0.

#3 would be a minimum stopgap. If people want to set it to 9999 that would work for the 1-2 clients on earth who hit that. :smiley:

5

We’ll go ahead with adding a toggle for whether or not a limit is unlimited. It should make it into the next build of 8.0.