airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Marru <>
Subject Airavata Workflow Interpreter Emulation Framework
Date Sat, 23 Mar 2013 19:43:17 GMT
Hi Lavanya,

I was pleasantly surprised to see you are still furthering the idea of workflow emulator,
this paper seem to be very recent [1]. We had unfinished workflow emulators which we offered
as GSoC projects last year and we are resurrecting it now. I will advice the students to shamelessly
steal ideas from your paper. 

Hi Shameera,

I was about to re-write Saminda's task description on the emulators, but Lavanya's paper [1]
saved me some time. Why don't you read through the paper and propose back concrete GSoC tasks
you see as applicable to current Airavata Workflow Interpreter. Do not worry to take the approaches
literally and be liberal in your thinking and implementation. But the paper should give you
a good head start. As you explore Airavata, just throw some ideas and we will help you refine


[1]  -

On Mar 23, 2013, at 3:11 PM, "Shameera Rathnayaka (JIRA)" <> wrote:

>    [
> Shameera Rathnayaka commented on AIRAVATA-346:
> ----------------------------------------------
> Hi devs, 
> As I mentioned in dev mailing list I would like to do this as my GSOC project. Saminda/Suresh/devs
can you provide me more details or shall we discuss in improving this project? 
> Thanks,
> Shameera.
>> [GSoC] Framework to run/monitor workflows locally with simulated/dummy BE
>> -------------------------------------------------------------------------
>>                Key: AIRAVATA-346
>>                URL:
>>            Project: Airavata
>>         Issue Type: New Feature
>>           Reporter: Saminda Wijeratne
>>           Assignee: Saminda Wijeratne
>>             Labels: gsoc2012, gsoc2013, mentor
>> It is common to need to test something you've created on a test environment rather
than on a real setup. This is because,
>> 1. The tasks are trivial and it'll be faster to run locally to verify correct flow/execution.
>> 2. It can cost to run them on a real setup at development stage.
>> 3. Proper access to the real setup is not available
>> 4. Unit testing on a real setup is unfeasible
>> Thus it would be easy for the user if there is a way to setup a simulated environment
without much difficulty may be perhaps with some dummy data from the user itself. Effectively
it will be behaving exactly as a GFac server/message box/registry etc but with hard wired
data. As an example ideally it would be like the Azure simulator I guess.
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see:

View raw message