[Commotion-dev] Fwd: [Builders] AutoNOC - here we go

[Outback Dingo]

Im actually quite skeptical around all this, so far it all sounds good, but
its just context, no viable
deployment, or code shown anywhere, no github.... to me ....... its a
watcher, but there have been
many that came before and had ideas that never panned out to anything
viable... im getting a sense
this might just be one of them.


On Mon, Jun 2, 2014 at 1:13 AM, Ben West <ben at gowasabi.net> wrote:

> Here is more info that I could find about AutoNOC / FreedomNOC:
> https://commons.thefnf.org/index.php/AutoNOC
>
> https://thefnf.org/look-inside-freenetworkfoundation-network-operations-center/
> https://chili.thefnf.org/projects/freedomnoc
>
> Note that links under freenetworkfoundation.org I think are now located
> under thefnf.org .
>
> P.S. Is OTI still building or planning to build their own mesh dashboard?
>
>
> On Sat, May 31, 2014 at 11:01 AM, Dan Staples <
> danstaples at opentechinstitute.org> wrote:
>
>> FYI, looks like an interesting project.
>>
>>
>> -------- Original Message --------
>> Subject: [Builders] AutoNOC - here we go
>> Date: Fri, 30 May 2014 10:47:24 -0500
>> From: Charles N Wyble <charles at knownelement.com>
>> Reply-To: FNF Development/hacking list <builders at lists.thefnf.org>
>> Organization: Free Network Foundation
>> To: builders at thefnf.org
>>
>> Hey everybody,
>>
>> I wanted to kick off the development/integration work around AutoNOC.
>> AutoTunnel 0.1 has been released. It still needs love of course, and
>> I'll be focusing on getting community development underway in the near
>> future.
>>
>> Internally we now need to think about AutoNOC and getting a 0.1 of that
>> released.
>>
>> So what is AutoNOC?
>>
>> AutoNOC is a network security monitoring and management suite. It will
>> allow operators to
>>
>> 1) Push out firmware to radios
>> 2) Push out configuration changes network wide (opkg deployment, snmp
>> community changes, that sort of thing).
>> 3) Monitor availability and performance of radios,switches,routers,
>> links, protocol updates etc.
>> 4) Graph availability and performance data of radios,switches,routers,
>> links, protocol updates etc.
>> 5) Feed 12 hour samples of the above data to guifi.us if the community
>> desires it (will be off by default, and they'll have to opt in).
>>
>> Components of AutoNOC
>>
>> A custom Zenosss plugin that listens to BMX/batman-adv protocol updates
>> and adds new items to Zenoss (this needs to be written).
>> Zenoss is the core. It covers
>> monitoring/alerting/graphing/reporting/dashboards etc.
>> Rundeck will be used for command dispatch to all the systems.
>> Slack will be used for configuration (/etc/config) file distribution and
>> continuous compliance
>>
>> The above tools are ones that I'm personally very familiar with and I
>> know they will scale and are trivial to deploy and get productive with
>> quickly.
>>
>> I'd estimate about 100 developer hours to have a fully
>> integrated/tested/proven appliance (a full 1.0 release).
>>
>> 30 hours for writing the zenoss plugin
>> 20 hours for integrating everything into a comprehensive whole
>> 10 hours for documentation
>> 20 hours for SNMP work (query/traps) (as that's the core of the
>> monitoring/alerting/thresholding system)
>> 20 hours for overages/misc
>>
>> The prototype is already underway in the FNF lab. I'd need about 10 dev
>> hours for a 0.1 release. Add the above 100 on top of that for the full
>> schedule.
>>
>> Thoughts?
>>
>>
>> --
>> Charles N Wyble
>> CTO/cofounder of thefnf.org
>> charles at knownelement.com 818 280 7059
>>
>> _______________________________________________
>> Builders mailing list
>> Builders at lists.thefnf.org
>> https://lists.thefnf.org/listinfo/builders
>>
>> !DSPAM:5388a8103651673011648!
>>
>>
>>
>> _______________________________________________
>> Commotion-dev mailing list
>> Commotion-dev at lists.chambana.net
>> https://lists.chambana.net/mailman/listinfo/commotion-dev
>>
>
>
>
> --
> Ben West
> http://gowasabi.net
> ben at gowasabi.net
> 314-246-9434
>
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20140602/dfc39272/attachment.html>