You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Saminda Wijeratne (Commented) (JIRA)" <ji...@apache.org> on 2012/04/06 06:11:19 UTC
[jira] [Commented] (AIRAVATA-343) [GSoC] Workflow Debugging
Framework for Airavata
[ https://issues.apache.org/jira/browse/AIRAVATA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248022#comment-13248022 ]
Saminda Wijeratne commented on AIRAVATA-343:
--------------------------------------------
Hasitha,
Until my request for becoming a mentor for ASF was approved through GSoC Melange site please consider the following as few comments on the proposal [1] you've submitted.
i. There are a few spelling & grammar mistakes
ii. While I know what you meant, I feel some of the following areas are a little unclear. Perhaps consider revising those a little?
a. it is not clear why current XBaya debugging cannot be directly associated with a backend execution of the workflow with a simple RMI mechanism.
b. Might be a good idea to mention what you plan do to if you do not have enough time to implement the all the tasks you've mentioned. (Note that it's not crucial for all the tasks you've mentioned to be implemented)
c. How do you plan to carry out the testing phase. A brief description would do.
d. When reading the proposal I see several paragraphs that could have a subheading (for clarity purposes).
iii. If you have time, a simple box diagram would be helpful to others to understand the architecture you are proposing.
Overall I think the proposal looks good.
Saminda
1. http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/hasithaaravinda/1
> [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
Re: [jira] [Commented] (AIRAVATA-343) [GSoC] Workflow Debugging
Framework for Airavata
Posted by Hasitha Aravinda <ma...@gmail.com>.
Hi Saminda,
Thank you for your feedback and it is really helpful. Now i am working on
improving the proposal according to your feedback.
Thank you
Hasitha Aravinda.
On Fri, Apr 6, 2012 at 9:52 AM, Suresh Marru <sm...@apache.org> wrote:
> Saminda,
>
> I posted your message on the proposal comment, so the trace is there as
> well.
>
> Suresh
> On Apr 6, 2012, at 12:11 AM, Saminda Wijeratne (Commented) (JIRA) wrote:
>
> >
> > [
> https://issues.apache.org/jira/browse/AIRAVATA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248022#comment-13248022]
> >
> > Saminda Wijeratne commented on AIRAVATA-343:
> > --------------------------------------------
> >
> > Hasitha,
> >
> > Until my request for becoming a mentor for ASF was approved through GSoC
> Melange site please consider the following as few comments on the proposal
> [1] you've submitted.
> >
> > i. There are a few spelling & grammar mistakes
> > ii. While I know what you meant, I feel some of the following areas are
> a little unclear. Perhaps consider revising those a little?
> > a. it is not clear why current XBaya debugging cannot be directly
> associated with a backend execution of the workflow with a simple RMI
> mechanism.
> > b. Might be a good idea to mention what you plan do to if you do not
> have enough time to implement the all the tasks you've mentioned. (Note
> that it's not crucial for all the tasks you've mentioned to be implemented)
> > c. How do you plan to carry out the testing phase. A brief description
> would do.
> > d. When reading the proposal I see several paragraphs that could have
> a subheading (for clarity purposes).
> > iii. If you have time, a simple box diagram would be helpful to others
> to understand the architecture you are proposing.
> >
> > Overall I think the proposal looks good.
> >
> > Saminda
> >
> > 1.
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/hasithaaravinda/1
> >
> >> [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
> >
> >
>
>
--
--
*Hasitha Aravinda*,
[image: Google Plus] <https://plus.google.com/108359324634256115965/> [image:
LinkedIn] <http://www.linkedin.com/in/hasithaaravinda> [image:
Facebook]<http://www.facebook.com/hasitha27> [image:
Try it now] <http://tryitnw.blogspot.com/> | [image: Skype] hasitha.aravinda
Re: [jira] [Commented] (AIRAVATA-343) [GSoC] Workflow Debugging Framework for Airavata
Posted by Suresh Marru <sm...@apache.org>.
Saminda,
I posted your message on the proposal comment, so the trace is there as well.
Suresh
On Apr 6, 2012, at 12:11 AM, Saminda Wijeratne (Commented) (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/AIRAVATA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248022#comment-13248022 ]
>
> Saminda Wijeratne commented on AIRAVATA-343:
> --------------------------------------------
>
> Hasitha,
>
> Until my request for becoming a mentor for ASF was approved through GSoC Melange site please consider the following as few comments on the proposal [1] you've submitted.
>
> i. There are a few spelling & grammar mistakes
> ii. While I know what you meant, I feel some of the following areas are a little unclear. Perhaps consider revising those a little?
> a. it is not clear why current XBaya debugging cannot be directly associated with a backend execution of the workflow with a simple RMI mechanism.
> b. Might be a good idea to mention what you plan do to if you do not have enough time to implement the all the tasks you've mentioned. (Note that it's not crucial for all the tasks you've mentioned to be implemented)
> c. How do you plan to carry out the testing phase. A brief description would do.
> d. When reading the proposal I see several paragraphs that could have a subheading (for clarity purposes).
> iii. If you have time, a simple box diagram would be helpful to others to understand the architecture you are proposing.
>
> Overall I think the proposal looks good.
>
> Saminda
>
> 1. http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/hasithaaravinda/1
>
>> [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
>
>