[
https://issues.apache.org/jira/browse/AIRAVATA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248264#comment-13248264
]
Suresh Marru commented on AIRAVATA-343:
---------------------------------------
Suresh April 6, 2012, 12:23 p.m.
Hi Hasitha,
I echo with Chris, great proposal but a bit ambitious. If you are motivated
enough and have good time, you will be able to do all of it, but as you can see
from the OODT jira, these can easliy result in half a dozen significant
sub-tasks. I do not want to discourage you, but caution you to scope your
project well enough. Even you can finish the phase 1, that by itself will be
very helpful for the airavata user community. Airavata workflows are typically
very long running in nature and tapping into existing executions not only assit
the workflow debugging but opens up venue for other exhilerating opportunities
like providing deferred (or just in time binding) of workflow inputs, provide
workflow adaptability and so on. Very encouraging to see you are thinking
beyond the current project.
Few questions and comments:
Why do you propose new debugging server as opposed to enhancing the workflow
interpreter itself?
You have a very elaborative development plan but a week testing plan, please
try and elaborate on your test cases as well.
You have a good granular details in the implementation section, but your
schedule section is very course grained. Can you submit a more fine grained
schedule?
Over all, good proposal and an important topic. These capabilities not only
improve airavata, but also saves valuable computational time on lage super
computers and should have a very broad impact. Me and others in airavata
community will be happy to guide you through out the project.
Good luck with the proposal,
Suresh
> [GSoC] Workflow Debugging Framework for Airavata
> ------------------------------------------------
>
> Key: AIRAVATA-343
> URL: https://issues.apache.org/jira/browse/AIRAVATA-343
> Project: Airavata
> Issue Type: New Feature
> Components: Workflow Interpreter
> Reporter: Saminda Wijeratne
> Priority: Minor
> Labels: gsoc2012, mentor
>
> The backend of Airavata should support workflow debugging. It should expose
> some API that will enable users to connect &
> 1. Receive workflow execution data, current state data
> 2. Send commands to manipulate execution life cycle
> (pause/resume/restart/stop etc.)
> 3. Modify workflow data on the fly
> The API should be intuitive, language independent & supports remote debugging.
> The specifics for the task & the level of debugging is open for discussion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
