[
https://issues.apache.org/jira/browse/AIRAVATA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248271#comment-13248271
]
Saminda Wijeratne commented on AIRAVATA-343:
--------------------------------------------
Looks really great Hasitha. Nice job.
Few more tips from my side.
i. a few formatting tips to improve the look n feel more,
* try to see if you can justify alignments of a paragraph
* see if you can indent bullet points
* get rid of redundant sentences (eg: Backend debugging module will be
implemented in Airavata Server and will capable to do following task.)
ii. for the purpose of newbies to the Airavata architecture perhaps it would be
useful to add a simple terminology index at the end of the proposal that
explains (very briefly) some words used in Airavata domain,
eg:
topic id - represents <something>
backend/airavata server - <something> which does <something>
...
> [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
