[Battlemesh] Result documentation RFC

[Jenny Ryan]

Just a quick note to say how much I admire and appreciate the thoroughness,
organization, and elegant beauty of this documentation work. Very helpful
as I compose my posts on the conference. Bravo! Truly impressed.

Jenny

Help open a people-powered common space in Oakland, California!
https://omnicommons.org/donate

`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
"Technology is the campfire around which we tell our stories."
-Laurie Anderson

"Storytelling reveals meaning without committing the error of defining it."
 -Hannah Arendt

"To define is to kill. To suggest is to create."
-Stéphane Mallarmé
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`

On Sat, Aug 22, 2015 at 9:15 AM, Nemesis <nemesis at ninux.org> wrote:

> Quick update
>
>    - I added a (draft) page to explain the duplicated packets problem we
>    encountered, anyone could help me write a proper description?
>
>    http://battlemesh-test-docs.readthedocs.org/v8/about-duplicated-packets.html
>
>    - I added a "Lessons learned" page:
>    http://battlemesh-test-docs.readthedocs.org/v8/lessons-learned.html
>
>    - I added a draft Credits page, feel free to add missing names or
>    correct wrong names/descriptions, links to
>    community/project/company/university, ecc:
>    http://battlemesh-test-docs.readthedocs.org/v8/credits.html
>
> Federico
>
>
>
> On 08/21/2015 07:47 PM, Nemesis wrote:
>
> Hi everybody,
>
> this is a request for feedback: comments, suggestions and pull requests.
>
> See here:
> http://battlemesh-test-docs.readthedocs.org/v8/index.html
>
> Before starting to work on it I exchanged a few ideas via chat with
> Amadeus and Henning.
>
> Here's a quick recap:
>
>    - having all the results on one page would have made it quite hard to
>    read
>    - so the tests have been split in 3 pages
>       - mesh of adversity: one single stream from client (connected to A)
>       to server (connected to K)
>       - reboot
>          - ping
>          - ping + iperf
>       - crossed streams jeopardy: two streams, client A to server K and
>       node D to node H
>       - 10 mbit iperf streams
>          - 100 mbit iperf streams
>       - blowing up the network: tests performed with Flent by Toke
>          - Realtime Response Under Load (RRUL)
>          - Realtime Response Under Load Best Effort (RRUL_BE)
>          - 8-stream download test
>          - TCP upload
>          - TCP download
>
> As you can see, there are quite a few things that can be improved!
>
>    - some graphs are missing (some purposely and some I was not able to
>    generate properly)
>    - english needs to be checked
>    - it would be good to provide some additional explanation to the graphs
>    - shall we add a conclusion section to each page? if yes, anybody
>    willing to propose a conclusion?
>    - shall we add a last "lessons learned" page with all the things that
>    went wrong and the proposed solutions for the next edition?
>    - we are not forced to host it on readthedocs.org, we might also host
>    the sphinx build files ourselves
>
> The github repo is here:
> https://github.com/battlemesh/battlemesh-test-docs
>
> Looking forward to hear your feedback!
>
> Federico
>
>
>
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20150901/8e1cefa3/attachment-0001.html>