This was an interesting thread title! :) My thoughts are for you guys to take a look at the way this is done in Apache OODT, by starting at:
Workflow Task [Workflow Manager, stopWorkflow method] TaskJob [Workflow Manager implementation of OODT Resource Manager Job] Job [Resource Manager killJob method] That should probably be a good start! Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Suresh Marru <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Saturday, April 20, 2013 6:43 AM To: Airavata Dev <[email protected]> Subject: [DISCUSS] Airavata Termination Architecture >Hi All, > >Can we discuss architectural solutions to implement Termination features >within Airavata? I will set some context here by illustrating the flow. > >Airavata Client -> Workflow Interpreter -> GFac API (GFac Provider) -> >Remote Compute Machine. > >We need a solution to traverse through this chain to terminate an >invocation. The side effects have to be properly encountered so a >terminate request can change the status of an invocation to Cancel state >and all of the invocation chain can gracefully react to this state. > >Thoughts on how we can implement these capabilities? > >Cheers, >Suresh
