[INFO] Airavata GFac GRAM implementation .. SUCCESS [
0.713 s]
[INFO] Airavata GFac BES implementation ... FAILURE [
1.917 s]
[INFO] Airavata Security Implementation ... SKIPPED
[INFO] Airavata Credential Store Service .. SKIPPED
Hello,
I am sorry, I am bit late on this thread. But when reading through this
thread I simply got lost, what this thread is discussing. I have few
questions.
1. @Shameera : Is XWF actually a language to define workflow ? To my
understanding it was an intermediate representation to convert
Hi Amila,
Please see my comments inline.
On Mon, Oct 20, 2014 at 3:04 PM, Amila Jayasekara thejaka.am...@gmail.com
wrote:
Hello,
I am sorry, I am bit late on this thread. But when reading through this
thread I simply got lost, what this thread is discussing. I have few
questions.
1.
Hi Shameera,
I think the whole point of introducing thrift is to support language
bindings for gateway developers and I do not think we should limit this
freedom by introducing a python client just to build a workflow. I propose
to represent a workflow as a thrift data-structure (I think by using
Hi Shameera,
Thanks for the reply.
I wouldnt call XWF a language. It is not a language in any sense but an
intermediate representation of a workflow graph.
To my understanding what you need is not a language but an efficient
portable intermediate representation. Seems you also have realized it.
