[Interop-dev] A survey of community network management solutions

[Ben West]

Thank you for sharing this spreadsheet.

Of possibly tangential relevance to node monitoring tools, I've been using
an inelegant hodgepodge of centralized syslog gathering from OpenWRT AA and
BB-based nodes, which I feed to a host in the Cloud running syslog-ng.  I
can then issue email alerts based on regex patterns applied to the log
traffic gathered.  The log traffic is also retained in a database, with log
entries indexed per nodes' hostname, and pruned out after a month.

This is indeed drinking from a firehose, but the syslog traffic gathered
over any wireless links still travels as UDP, so it's a leaky firehose.
Also, it should coexist fine with any of the management solutions mentioned
in Mitar's spreadsheet.

This approach has proven quite useful for debugging purposes (e.g. ability
to scroll back in time to observe events leading up to wifi driver crash),
although it's definitely a bit log-heavy for "production" use.  My vague
goal, at any rate, had been to drop this syslog gatherer and migrate to a
more elegant monitoring approach.  But, I'd still be happy to share a
write-up about it, if list members find interesting.


On Thu, May 21, 2015 at 7:17 AM, Nemesis <(spam-protected)> wrote:

> The new version of nodeshot has something interesting that is not
> mentioned in that table which is a notification system so that users can
> know of what happens around them if they want to.
>
> There are also a few other modules like a simple CMS to write content
> pages, login with social networks, a tool to contact a subset or all the
> users and so on.
>
> The curious thing, which I often ask myself why, is that most of those
> programs are written in python but do not share any common library.
>
> That's why in the new nodeshot we are develping the topology parser in a
> separate pure python library hoping that more communities will join
> forces: https://github.com/ninuxorg/netdiff
>
> I believe a similar approach could be used also for generating
> configurations.
>
> Federico
>
>
>
> On 05/21/2015 01:41 PM, Mitar wrote:
> > Hi!
> >
> > Please help us fill in the spreadsheet of community network management
> > solutions out there. We filled in those we know about, but even those
> > only partially. So if in your network you are using some solutions for
> > network management, please fill it in:
> >
> > https://goo.gl/JbD4VC
> >
> > As we are working on nodewatcher v3 we are trying to keep up with
> > developments of others. We will also use this data in the paper we are
> > writing about managing community networks. Feel free to use the data as
> > well. If you strongly feel that some column is missing, add it, but
> > remember that it has to be filled for all rows to be really useful.
> >
> > Spreadsheet is CC0.
> >
> >
> > Mitar
> >
>
>
>
> _______________________________________________
> Interop-dev mailing list
> (spam-protected)
> https://lists.funkfeuer.at/mailman/listinfo/interop-dev
>



-- 
Ben West
http://gowasabi.net
(spam-protected)
314-246-9434
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.funkfeuer.at/pipermail/interop-dev/attachments/20150521/2e693aad/attachment.html>