airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amila Jayasekara <thejaka.am...@gmail.com>
Subject Re: [DISCUSS] Airavata Termination Architecture
Date Sat, 20 Apr 2013 16:05:47 GMT
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 <smarru@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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message