You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2013/03/23 16:55:15 UTC
[jira] [Updated] (AIRAVATA-343) [GSoC] Workflow Debugging Framework
for Airavata
[ https://issues.apache.org/jira/browse/AIRAVATA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated AIRAVATA-343:
---------------------------------------
Labels: gsoc2012 gsoc2013 mentor (was: gsoc2012 mentor)
> [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, gsoc2013, mentor
> Attachments: debuggerModule_midterm_eval.patch, Xbaya_debugger_support_20_08_2012.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira