airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierce, Marlon" <>
Subject Re: [GSoC Proposal] Apache Airavata Monitoring Module
Date Thu, 24 Mar 2016 14:34:22 GMT
Hi Sidd,

This is a well written proposal. Some comments:

* The monitoring component doesn’t need to directly communicate with GFAC. There can be
multiple GFACs, so the original GFAC that submitted the request may no longer be running.
 Also, other components may want to receive updates, including external subscribers.  GFAC
subscribers can pick up the message and act.  There is the issue of managing race conditions
between multiple GFACs and other distributed computing issues. If a GFAC instance picks up
the message and wants to act on it but then becomes unresponsive, how do we handle this situation?
This is my opinion, anyway. It is harder to implement than the direct approach.

* You still need your high level architecture diagram and other figures where you have placeholders

* You need 2 week deliverables in your timeline. Add discussion of risk and risk mitigation,
as I mentioned in my general email earlier today.


From: Siddharth Jain <<>>
Reply-To: "<>" <<>>
Date: Wednesday, March 23, 2016 at 12:52 AM
To: "<>" <<>>
Subject: Re: [GSoC Proposal] Apache Airavata Monitoring Module

Correction, the<> link is:[GSoC+Proposal]+Apache+Airavata+Monitoring+Module

On Tue, Mar 22, 2016 at 6:35 PM, Siddharth Jain <<>>
Hello all,
I have the first draft of my GSoC proposal on Apache Airavata Monitoring Module ready. I will
appreciate if you could give any comments or suggestions to improve this proposal.

The proposal is available on:


The<> link points to what it will actually look
like, the google docs version is just for convenience of commenting.

Best regards,
Siddharth Jain

View raw message