[Commotion-admin] [commotion-dashboard-helper] Mesh testbed Scripts (#6)

[Seamus Tuohy]

Per our recent deployment it has become clear that comprehensive network testing and evaluation must be distributed and run by the nodes themselves. I propose that we use the dashboard-helper to centralize the data collection.
This will include:
- [ ] A new set of controls for the dashboard menu that specify what tests will be allowed to run, and what results will be sent to the dashboard.
- [ ] Descriptions of the type of information collected in each test to warn a user what they are sending to the dashboard.
- [ ] An assessment of existing network needs to create use-case documentation and test-suit types that are accurately split apart for teh varying use-cases and data required by community wireless projects to tune performance, show success', and better serve community needs.
- [ ] A system for a node to query nodes on the network for paired testing, like iperf tests.
- [ ] A system, and configuration interface, for nodes to evaluate their status before approving, putting off, or rejecting test requests from other nodes.
- [ ] A system for receiving and verifying requests from the dashboard for tests between a node and another end-point. This will allow dashboard controller to identify problem areas and query nodes around those areas to check connectivity, etc. to other nodes.
- [ ] Dashboard level features for requesting tests from nodes and viewing the results of tests over time
- [ ] A node level dashboard to show condensed overviews of tests run on a node in the past
- [ ] API reference for the testing suite to allow for easy installation and test creation for other projects


---
Reply to this email directly or view it on GitHub:
https://github.com/opentechinstitute/commotion-dashboard-helper/issues/6
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-admin/attachments/20131014/4e178a6a/attachment.html>