TODO 2.11 KB
Newer Older
1
URGENT => Name ideas :
2
    resnet ( for Resiliable NET ) : i prefere resinet
3
    rsnet ( Resiliable Scalable NET )
4

Ulysse Beaugnon's avatar
Ulysse Beaugnon committed
5
To be done :
Guillaume Bury's avatar
Guillaume Bury committed
6 7
    Use an algorithm to choose which connections to keep and/or establish
    instead of pure randomness
8
        number of routes / tunnel
Ulysse Beaugnon's avatar
Ulysse Beaugnon committed
9 10
        favorise most used roads

Guillaume Bury's avatar
Guillaume Bury committed
11
    Write docstrings for all class/methods/functions
Guillaume Bury's avatar
Guillaume Bury committed
12

Guillaume Bury's avatar
Guillaume Bury committed
13 14
    Handle corrupt peers DB gracefully

15

16
To be discussed:
Guillaume Bury's avatar
Guillaume Bury committed
17 18 19 20 21 22 23
    U : Babel seems to be very long to establish the routes : maybe we should
        tell him thant we are not on a wired network but on a mobile network ?
    G : babel establish routes quickly enough i'd say. There are two new
        options : hello and wireless, for hello_interval and treating all
        interfaces as wireless. However, treating an interface as wireless
        doesn't lessen the hello_interval, it only changes how babel estimates
        quality link, and cost.
Guillaume Bury's avatar
Guillaume Bury committed
24
    U : from babel web page : "When the Babel daemon detects a wired network,
25
        it will use a larger interval between hellos".
Guillaume Bury's avatar
Guillaume Bury committed
26 27
        Moreover, it seems that the wireless option only means
        "hostile environment" which seems best for a resilient network.
28 29
        30 sec of hello interval seams also too much. The default value for
        babel is 4 sec (from babel man page).
Guillaume Bury's avatar
Guillaume Bury committed
30
        According to raphael's stats on the nexedi's server downtime,
Ulysse Beaugnon's avatar
Ulysse Beaugnon committed
31 32 33
        45% of the problems dont last more than 2 minutes, 55% no more than
        3 minutes If it takes 2 min to detect a dead connection, then we wont be
        solving many problems with our overlay network
34 35 36 37 38 39
    G : ok, so babel hello-interval should be set to a lower value,
        we should do some tests to pinpoint the best compromise between
        speed and bandwith usage.
        Btw, is there a doc ( pdf, image, file ) resuming Raphael's stats
        on nexedi's server downtime ? it could be useful for the internship
        rapport
Ulysse Beaugnon's avatar
Ulysse Beaugnon committed
40
    G : It takes babel between 3 times and 4 times the hello interval to
41
        reestablish connection, if a direct link is cut
42 43
    U : So we have to reduce the hello interval. 2min to detect a dead link is
        far too much.
Guillaume Bury's avatar
Guillaume Bury committed
44
    G : k