Skip to content

Commit 379966b

Browse files
authored
Merge pull request #301 from grondo/rfc21-prolog-epilog
rfc21: add job prolog and epilog events
2 parents 4972637 + 3fd6045 commit 379966b

File tree

1 file changed

+74
-0
lines changed

1 file changed

+74
-0
lines changed

spec_21.rst

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -317,6 +317,80 @@ Example:
317317
{"timestamp":1552593348.088391,"name":"alloc","context":{"annotations":{"sched.resource_summary":"rank0/core[0-1]"}}}
318318
319319
320+
Prolog-start Event
321+
^^^^^^^^^^^^^^^^^^
322+
323+
A prolog action has started for the job. This event SHALL prevent the job
324+
manager from initiating a start request to the execution system until the
325+
prolog action is completed with a corresponding ``prolog-finish`` event.
326+
327+
The following keys are REQUIRED in the event context object:
328+
329+
description
330+
(string) Name or description of the prolog action.
331+
332+
.. code:: json
333+
334+
{"timestamp":1552593348.073045,"name":"prolog-start","context":{"description":"/usr/sbin/job-prolog.sh"}}
335+
336+
337+
Prolog-finish Event
338+
^^^^^^^^^^^^^^^^^^^
339+
340+
A prolog action for the job has completed. The prolog description SHOULD
341+
match a previous ``prolog-start`` event.
342+
343+
The following keys are REQUIRED in the event context object:
344+
345+
description
346+
(string) Name or description of the prolog action.
347+
348+
status
349+
(integer) Completion status of the prolog action. A status of zero SHALL
350+
be considered success, with a non-zero status indicating failure.
351+
352+
.. code:: json
353+
354+
{"timestamp":1552594348.0,"name":"prolog-finish","context":{"description":"/usr/sbin/job-prolog.sh", "status":0}}
355+
356+
357+
Epilog-start Event
358+
^^^^^^^^^^^^^^^^^^
359+
360+
An epilog action has started for the job. This event SHALL prevent the job
361+
manager from initiating a free request to the scheduler until the
362+
epilog action is completed with a corresponding ``epilog-finish`` event.
363+
364+
The following keys are REQUIRED in the event context object:
365+
366+
description
367+
(string) Name or description of the epilog action.
368+
369+
.. code:: json
370+
371+
{"timestamp":1552593348.073045,"name":"epilog-start","context":{"description":"/usr/sbin/job-epilog.sh"}}
372+
373+
374+
Prolog-finish Event
375+
^^^^^^^^^^^^^^^^^^^
376+
377+
A epilog action for the job has completed. The epilog description SHOULD
378+
match a previous ``epilog-start`` event.
379+
380+
The following keys are REQUIRED in the event context object:
381+
382+
description
383+
(string) Name or description of the epilog action.
384+
385+
status
386+
(integer) Completion status of the epilog action. A status of zero SHALL
387+
be considered success, with a non-zero status indicating failure.
388+
389+
.. code:: json
390+
391+
{"timestamp":1552594348.0,"name":"epilog-finish","context":{"description":"/usr/sbin/job-epilog.sh", "status":0}}
392+
393+
320394
Free Event
321395
^^^^^^^^^^
322396

0 commit comments

Comments
 (0)