You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Suresh Marru <sm...@iu.edu> on 2013/04/20 15:43:27 UTC
[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
Re: [DISCUSS] Airavata Termination Architecture
Posted by Amila Jayasekara <th...@gmail.com>.
Hi Suresh,
I dont think I clearly understood the problem.
Is this related to canceling a workflow execution after invoking it ?
Thanks
Amila
On Sat, Apr 20, 2013 at 9:43 AM, Suresh Marru <sm...@iu.edu> wrote:
> 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
Re: [DISCUSS] Airavata Termination Architecture
Posted by Suresh Marru <sm...@apache.org>.
Thanks Chris, these are very useful links. I will look at them in Detail.
On Apr 20, 2013, at 12:05 PM, Amila Jayasekara <th...@gmail.com> wrote:
> Is this related to canceling a workflow execution after invoking it ?
Amila, yes this is for canceling the invocation. But not just at the workflow level but all the way through the job. More importantly dealing with side effects of proper notification, intermediate data clean up, properly spinning the state machine and so on.
Suresh
On Apr 20, 2013, at 11:56 AM, "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov> wrote:
> 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: chris.a.mattmann@nasa.gov
> 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 <sm...@iu.edu>
> Reply-To: "dev@airavata.apache.org" <de...@airavata.apache.org>
> Date: Saturday, April 20, 2013 6:43 AM
> To: Airavata Dev <de...@airavata.apache.org>
> 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
>
Re: [DISCUSS] Airavata Termination Architecture
Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.
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: chris.a.mattmann@nasa.gov
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 <sm...@iu.edu>
Reply-To: "dev@airavata.apache.org" <de...@airavata.apache.org>
Date: Saturday, April 20, 2013 6:43 AM
To: Airavata Dev <de...@airavata.apache.org>
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