[Iplant-api-dev] Job events

[Rion Dooley]

Hi Jon,

Pausing and checkpointing jobs is highly dependent on the underlying system and, at the moment, I’m unaware of any systems that will actually allow you to pull that off reliably.

You can make a POST request to a specific job resource with a form of action="stop" or a content type of application/json and body of

{ "action":"stop" }

That will kill a running job or cancel a submitted job. The former will cause a KILLED event to fire. The latter will cause a STOPPED event to fire. If you’re testing out webhooks as part of your application, you can, of course, just manually POST to your web hook URL to emulate the behavior.

—
Rion

On Mar 1, 2015, at 9:52 PM, Duvick, Jonathan P [GDCBS] <jduvick at iastate.edu<mailto:jduvick at iastate.edu>> wrote:

Can I effect these event states via the API?
-KILLED Job execution killed at user request
-PAUSED Job execution paused by user
How are the dependencies and outcomes different from STOPPED?

(http://preview.agaveapi.co/documentation/event-reference/)

Thanks,

Jon Duvick
PlantGDB Manager
http://www.plantgdb.org/
Department of Genetics, Development and Cell Biology
2258 Molecular Biology Building
Iowa State University
Ames IA 50011

(515) 294-2360
(515) 294-6755 FAX
_______________________________________________
Iplant-api-dev Mailing List: Iplant-api-dev at iplantcollaborative.org<mailto:Iplant-api-dev at iplantcollaborative.org>
List Info and Archives: http://mail.iplantcollaborative.org/mailman/listinfo/iplant-api-dev
One-click Unsubscribe: http://mail.iplantcollaborative.org/mailman/options/iplant-api-dev/dooley%40tacc.utexas.edu?unsub=1&unsubconfirm=1

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iplantcollaborative.org/pipermail/iplant-api-dev/attachments/20150302/68904f46/attachment.html