You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Amila Jayasekara <th...@gmail.com> on 2013/04/20 18:05:47 UTC

Re: [DISCUSS] Airavata Termination Architecture

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