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

[carlo.giesa]

Hi there!

I'm jumping into this discussion since we are facing similar questions about the new ticketing system. Is there a way that IT could manage this via rules or configurations. Of course, I could implement ticket assignment in the job submission process, but I have the impression that license handling should be configurable in a more dynamic way than through submission code. Is there anything obvious I'm missing here?

We also checked out the JOB_CREATED event, but it seems that events generate jobs that are executed as any other job on the farm. This is of course problematic if we want to make sure that the event runs before the job starts to assign the correct tickets as an example.

Any hints on that?

Greets,
Carlo

[timurhai]

Tickets designed as limits (counts) that should be assigned by the job submission script.
As submission script, during command construction, checks scene.
During this checks it can find out what tickets are needed and now much (what soft should be launched).

JOB_CREATED event was designed for some statistics and project tracking.

So, there is no dynamic way to assign ticket. And many others did not faced such needs.

You have tasks that can launch different types of software and this can not be checked during the job submission?