Community-Lab introduction

Check-in [542baf991d]
Login
Overview
Comment:Put all challenges as "testbed requirement vs. CN characteristic/requirement".
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 542baf991dd6fa4e98abe7fad37e8ae15875cf2b
User & Date: ivan on 2012-09-25 19:16:09
Other Links: manifest | tags
Context
2012-09-25
22:02
Some changes suggested by Axel Neumann.

- Rewording of intro to challenges slide (also reversed title). - Indicate interesting features of OpenWrt. - Mention root access to containers. - LXC is used to manage containers. - Change title of experiments slide. - Indicate minimum layer available to experiments. - Mention IEEE P2P'12 demos. - Indicate that DLEP and API experiments don't require slices. - Also, API experiments will soon be supported, but not yet. check-in: a413d4ac9a user: ivan tags: trunk

19:16
Put all challenges as "testbed requirement vs. CN characteristic/requirement". check-in: 542baf991d user: ivan tags: trunk
10:38
Replaced OPLAN logo with vectorized one provided by Malcolm Matson plus footer text. check-in: 5f565bb838 user: ivan tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Modified script.txt from [dba7698cbe] to [2552d02c56].

    47     47   
    48     48   ** Simple management vs. Distributed node ownership
    49     49   - manage devices belonging to diverse owners?
    50     50   
    51     51   ** Features vs. Lightweight, low cost
    52     52   - support devices ranging from PCs to embedded boards?
    53     53   
    54         -** Heterogeneity vs. Compatibility
           54  +** Compatibility vs. Heterogeneity
    55     55   - work with devices which allow little customization?
    56     56   - support diverse connectivity and link technologies (wireless, wired, fiber)?
    57     57   
    58     58   ** Familiarity & flexibility vs. System stability
    59     59   - Researchers prefer a familiar Linux env with root access.
    60     60   - isolate experiments that share the same node?
    61     61   - keep nodes stable to avoid in-place maintenance?  Accessing node locations
................................................................................
    67     67   - allow interaction at the lowest possible layer of the CN while not
    68     68     disrupting or overusing it?
    69     69   
    70     70   ** Traffic collection vs. Privacy of CN users
    71     71   - allow experiments performing traffic collection and characterization?
    72     72   - avoid researchers spying on users' data?
    73     73   
    74         -** Link instability vs. Management robustness
           74  +** Management robustness vs. Link instability
    75     75   - deal with frequent network outages in the CN when managing nodes?
    76     76   
    77     77   ** Reachability vs. IP address provisioning
    78     78   - We have IPv4 scarcity and incompatibility between CNs, lack of IPv6 support.
    79     79   - support testbed spanning different CNs?
    80     80   
    81     81   * Community-Lab testbed architecture

Modified slides.svg from [8ad7d26ef4] to [0e2fe8a887].

cannot compute difference between binary files