[CUWiN-Dev] Existing CUWiN monitoring tools and proposed work for monitoring tools

[dan blah]

On 8/9/06, Ross Musselman <rgmussel at cuwireless.net> wrote:
> Just to fill in the gap for those who want more context....
>
> This work is part of the CRI grant that we are working on with Jennifer
> Hou of UIUC. The link for the CRI RFP is here:
> http://www.nsf.gov/pubs/2004/nsf04588/nsf04588.htm
> The idea is to create a suite of monitoring and administration tools
> that can be used on a CUWiN network, and there is a particular emphasis
> on the management of a test bed, since that is one of the big
> deliverables on the grant.
>
> Dan, I don't think it's fair to say that there are no tools. It is
as it is now, i dont know of any monitoring tools that are included
with cuwin.  anyone can compile 3rd party software in on their own...
but we dont now.

> better to say that there are no integrated tools. What our suite needs
> to do is integrate the tools to provide better monitoring and
> administration, right. The proposal will need to flesh out the idea that
> the suite is significantly better than the sum of its parts.
>
> As far as the actual functions of the suite, your list looks good to me
> (but what do I know).
>
> Ross
>
> dan blah wrote:
> > i have to have this *formalized* by tomorrow.  any additions,
> > subtractions, edits let me know.
> >
> > existing tools...
> > none <insert tool here>
> >
> > proposed work...
> > monitoring of network service status (inetd, zebra, hslsd, dhcpselect,
> > wdogctl, etc)
> > monitoring of node recourses (processor load, disk and memory usage,
> > running processes, network load)
> > monitoring of environmental factors such as node temperature
> > monitoring of system state changes (network interface changes,
> > configuration file add/delete/changes, file/drive permission changes)
> > list of node clients with basic client information
> > web interface for viewing current network status, problem history, log
> > file (/var/log/daemon, /var/log/messages), application and kernel
> > routes
> > web interface visible nodes (parsing of /var/db/linkstates, routeviz)
> > web interface authorization
> > ability to define event handler to be run during service of host
> > events for proactive problem resolution and self healing nodes
> > contact notification when service of host problems occur and get
> > resolved via email
> > local node engine viewable from local httpd or console with the
> > ability to be queried from a remote management engine
>
>
>


-- 
Daniel