<div dir="ltr">Im actually quite skeptical around all this, so far it all sounds good, but its just context, no viable<div>deployment, or code shown anywhere, no github.... to me ....... its a watcher, but there have been</div>
<div>many that came before and had ideas that never panned out to anything viable... im getting a sense</div><div>this might just be one of them.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 2, 2014 at 1:13 AM, Ben West <span dir="ltr"><<a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Here is more info that I could find about AutoNOC / FreedomNOC:<br><a href="https://commons.thefnf.org/index.php/AutoNOC" target="_blank">https://commons.thefnf.org/index.php/AutoNOC</a><br>
<a href="https://thefnf.org/look-inside-freenetworkfoundation-network-operations-center/" target="_blank">https://thefnf.org/look-inside-freenetworkfoundation-network-operations-center/</a><br>
<a href="https://chili.thefnf.org/projects/freedomnoc" target="_blank">https://chili.thefnf.org/projects/freedomnoc</a><br><br></div><div>Note that links under <a href="http://freenetworkfoundation.org" target="_blank">freenetworkfoundation.org</a> I think are now located under <a href="http://thefnf.org" target="_blank">thefnf.org</a> .<br>
</div><div><br></div>P.S. Is OTI still building or planning to build their own mesh dashboard?<br></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Sat, May 31, 2014 at 11:01 AM, Dan Staples <span dir="ltr"><<a href="mailto:danstaples@opentechinstitute.org" target="_blank">danstaples@opentechinstitute.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">FYI, looks like an interesting project.<br>
<br>
<br>
-------- Original Message --------<br>
Subject: [Builders] AutoNOC - here we go<br>
Date: Fri, 30 May 2014 10:47:24 -0500<br>
From: Charles N Wyble <<a href="mailto:charles@knownelement.com" target="_blank">charles@knownelement.com</a>><br>
Reply-To: FNF Development/hacking list <<a href="mailto:builders@lists.thefnf.org" target="_blank">builders@lists.thefnf.org</a>><br>
Organization: Free Network Foundation<br>
To: <a href="mailto:builders@thefnf.org" target="_blank">builders@thefnf.org</a><br>
<br>
Hey everybody,<br>
<br>
I wanted to kick off the development/integration work around AutoNOC.<br>
AutoTunnel 0.1 has been released. It still needs love of course, and<br>
I'll be focusing on getting community development underway in the near<br>
future.<br>
<br>
Internally we now need to think about AutoNOC and getting a 0.1 of that<br>
released.<br>
<br>
So what is AutoNOC?<br>
<br>
AutoNOC is a network security monitoring and management suite. It will<br>
allow operators to<br>
<br>
1) Push out firmware to radios<br>
2) Push out configuration changes network wide (opkg deployment, snmp<br>
community changes, that sort of thing).<br>
3) Monitor availability and performance of radios,switches,routers,<br>
links, protocol updates etc.<br>
4) Graph availability and performance data of radios,switches,routers,<br>
links, protocol updates etc.<br>
5) Feed 12 hour samples of the above data to <a href="http://guifi.us" target="_blank">guifi.us</a> if the community<br>
desires it (will be off by default, and they'll have to opt in).<br>
<br>
Components of AutoNOC<br>
<br>
A custom Zenosss plugin that listens to BMX/batman-adv protocol updates<br>
and adds new items to Zenoss (this needs to be written).<br>
Zenoss is the core. It covers<br>
monitoring/alerting/graphing/reporting/dashboards etc.<br>
Rundeck will be used for command dispatch to all the systems.<br>
Slack will be used for configuration (/etc/config) file distribution and<br>
continuous compliance<br>
<br>
The above tools are ones that I'm personally very familiar with and I<br>
know they will scale and are trivial to deploy and get productive with<br>
quickly.<br>
<br>
I'd estimate about 100 developer hours to have a fully<br>
integrated/tested/proven appliance (a full 1.0 release).<br>
<br>
30 hours for writing the zenoss plugin<br>
20 hours for integrating everything into a comprehensive whole<br>
10 hours for documentation<br>
20 hours for SNMP work (query/traps) (as that's the core of the<br>
monitoring/alerting/thresholding system)<br>
20 hours for overages/misc<br>
<br>
The prototype is already underway in the FNF lab. I'd need about 10 dev<br>
hours for a 0.1 release. Add the above 100 on top of that for the full<br>
schedule.<br>
<br>
Thoughts?<br>
<br>
<br>
--<br>
Charles N Wyble<br>
CTO/cofounder of <a href="http://thefnf.org" target="_blank">thefnf.org</a><br>
<a href="mailto:charles@knownelement.com" target="_blank">charles@knownelement.com</a> <a href="tel:818%20280%207059" value="+18182807059" target="_blank">818 280 7059</a><br>
<br>
_______________________________________________<br>
Builders mailing list<br>
<a href="mailto:Builders@lists.thefnf.org" target="_blank">Builders@lists.thefnf.org</a><br>
<a href="https://lists.thefnf.org/listinfo/builders" target="_blank">https://lists.thefnf.org/listinfo/builders</a><br>
<br>
!DSPAM:5388a8103651673011648!<br>
<br>
<br>
<br>
_______________________________________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net" target="_blank">Commotion-dev@lists.chambana.net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
</blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>
<a href="tel:314-246-9434" value="+13142469434" target="_blank">314-246-9434</a><br>
</div>
</font></span></div>
<br>_______________________________________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
<br></blockquote></div><br></div>