CGRU Forum

With the new tickets system, how would I handle something like this:
I have 5 nuke render licenses, but each render node can render 5 nuke renders at the same time as nukes license are per node and not per render.

Pool ticket set to 5 and tickets host set to 5?

This is the opposite of what I need for my redshift renders. ie. I can only have one redshift render/node

Hi!

For nuke you should add a pool ticket NUKE with 999 count and 5 max hosts.
(999 - is a total limit - you can set any big number you will never reach with 5 hosts).

For redshift you can create a special pool. And add there a single redshift service.

ok we'll try that, thanks!

and also i forgot to say,
your nuke tasks block should have 1 NUKE ticket too.

Can the tickets be configured in the farm.json? Like that we dont have to do it on every host via interface?

Eberrippe wrote: ↑Fri Aug 12, 2022 10:13 am Can the tickets be configured in the farm.json? Like that we dont have to do it on every host via interface?

I just relealized the farm.json got kicked out. Meaning every configuration has to be done via pools. But is there a config file for that somewhere?

You does need to configure farm settings on every host.
You can do this on the pool.
Pool is like pattern in the old farm.json, and it has "pattern" parameter to gather hosts by mask, again just like it was in farm.json.