[
https://issues.apache.org/jira/browse/AIRAVATA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241051#comment-13241051
]
Hasitha Aravinda commented on AIRAVATA-343:
-------------------------------------------
I went through your description and things mentioned by Surresh in mailing
list. I have couple of questions regarding the scope of this feature.
1) is this feature targeting on a debugging module that integrated in backend
of Airavata ( in Workflow Interpreter) or debugging module in XBaya GUI ?
According to my understanding it should contains both of them to provide better
debugging framework.
2) This feature covers lots of debugging functionalities and I feel, time
constraints will be a problem to address all these things. So what would be the
initial requirements that fit for a GSOC project? So we can set a milestone
plan.
Any suggestions are very much appreciated.
> [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
