[
https://issues.apache.org/jira/browse/AIRAVATA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243195#comment-13243195
]
Saminda Wijeratne commented on AIRAVATA-343:
--------------------------------------------
Sorry I could not get back to responding to your comment (or my promise) much
earlier.
1. Currently we already have a debugging feature at XBaya side. But this is
limited to executing the workflow at the XBaya only. If the workflow was
executed at the server XBaya cannot debug that execution. So the debugging
module should be implemented at the backend Airavata & the XBaya GUI should be
able to connect with it.
2. Lets have a priority set of features listed. I feel following are MUST HAVE.
* The debugging client (eg: XBaya GUI) should be able to connect with the
backend debugging module in Airavata server.
* The debugging client will provide a topic id & the breakpoint nodes to the
backend.
* Backend will pause and notify the debugging client whenever it reaches the
breakpoint node of the workflow instance (that's being executed at the server)
which corresponds to the topic id
* Client should be able to retrieve & expose the current status & data of
the workflow execution (eg: what are the inputs to the breakpoint node)
* Client should be able to tell the server to execute next node & pause
again (step)
* Client should be able to tell the server to continue execution (resume)
* Client should be able to tell the server to stop the execution of the
workflow (terminate)
Allowing modification of data on the stack while debugging is something that is
common in debugging frameworks. But we'll leave it for now if it is not going
to fit in to the time span.
There is
> [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
