Hi Narendran,
      Actually there's not a notification system yet. I know you mean to
implement a notification system at the agent side. The method we are
using now is periodically checking the aggregator. The agent sends
GetEvent messages to the aggregator and gets the events happened
in its region or the global Internet. The notification system might not be
a quite urgent job for now. We can add some code to pop-up a small
window for notification.
      I think the routing strategy is a problem needs to be solved. Also
we need to figure out how to form a stable peer network, in which the
peers could dynamically gather into clusters, and bypass the blockage.
Currently the aggregator url and super agent addresses (the entrance
for a new agent) are written into the db of the agent statically.
We still need to think out more ideas for a new peer to find its neighbors
and the super agents. Although we are using a cloud-based aggregator
 to scale our service, we are building a huge network covering the whole
world! So management of peers should be decentralized, by the peers
 themselves or the super agents. Remember the essential task is to
spread the information in a network with blockage. :)

Best Regards.
Alan

On Sun, Mar 25, 2012 at 12:01 PM, Narendran Thangarajan <
[email protected]> wrote:

> Hi,
>  I looked into the reporting mechanism in ICM-desktop agent. I see
> that once the agent logs in, there are three looping calls that
> perform the following :
>   1. Get peer list and populate the peerinfo.
>   2. Schedule tasks and add reports
>   3. Upload the generated reports.
>
>  But I can't find logic, how the peers make use of the
> Website/service reports generated from other peers or aggregator. If
> its available, where should I find the logic? If not, I would like to
> implement a notification system, which notifies the peer user of any
> network / website outages. This tool will be really helpful for
> admins/end users at various scales (On a global level or within a data
> center - thanks to the flexible design of the OpenMonitor system).
> This can be implemented using an evented I/O (say gevent).
>
> Thanks,
> Narendran.
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Umit-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/umit-devel
>



-- 
Zhongjie Wang
Master Candidate
Computer System Architecture
Peking University, China
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Umit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/umit-devel

Reply via email to