sug: document aj.block.addTicket

[keyframe]

I've recently upgraded to 3.1.1 from 2.3.1 and discovered that farm.json is no longer a thing.

It took a bit of head scratching to figure out how to use the new ticket system via the python api -- addTicket does not appear in the docs.
After looking at the provided submit script, I was able to decipher it, but it might be useful to document since this appears to be the only way to throttle resource use currently.

Best,

G

[keyframe]

On this topic, would I be correct in assuming that 'multi license' tasks (such as hbatch process of rsproxy files) would get two tickets '1 x hbatch' and '1 x redshift'?

G

[timurhai]

You can use tickets to measure and limit anything, licences, RAM, network i/o of a pool, and so on.
You can define any custom tickets for any custom resource.

https://cgru.readthedocs.io/en/latest/a ... ckets.html

Yes, it is always the lack of documentation, is it always some new feature needed instead to document existing one.

https://github.com/CGRU/cgru/blob/maste ... af.py#L290