Community-Lab introduction

Differences From Artifact [31bfcbf1ed]:

• File script.txt — part of check-in [7e709fd686] at 2012-10-07 23:13:38 on branch trunk — Colorise labels of interactions diagram. (user: ivan, size: 11506) [annotate] [blame] [check-ins using]

To Artifact [62be460f20]:

• File script.txt — part of check-in [0a9f73abee] at 2012-10-07 23:19:05 on branch trunk — Don't zoom over node architecture diagram. (user: ivan, size: 11419) [annotate] [blame] [check-ins using]

   109    109   - Each node is able to run several experiments simultaneously.
   110    110   - An experiment runs in a given node as a sliver which holds a share of its
   111    111     resources (CPU, memory, disk, bandwidth, interfaces…).
   112    112   - Finally, related slivers are grouped in a slice for management purposes.
   113    113   - All these concepts are inspired in PlanetLab. *##*
   114    114   
   115    115   ** Node architecture
   116         -# Axel: More stress on node itself.
   117         -# Ivan: Don't zoom!!
   118    116   allows the realization of these concepts.  *##* A node consists of a CD, a RD
   119         -and a rD connected to the same wired local network. *##*
          117  +and a rD connected to the same wired local network.
   120    118   
   121    119   - The community device
   122    120     - Completely normal CN device, so existing ones can be used.
   123    121     - routes traffic between the CN and the local network (which runs no routing
   124         -    protocol). *##*
          122  +    protocol).
   125    123   - The research device
   126    124     - Usually more powerful than CD, since experiments run here.
   127    125       - Separating the RD from the CD minimizes tampering with CN infrastructure.
   128    126       - Also experiments can't crash CN devices.
   129         -  - runs the versatile, light & free OpenWrt distro, customized by CONFINE. *##*
          127  +  - runs the versatile, light & free OpenWrt distro, customized by CONFINE.
   130    128       - Slivers are implemented as lightweight Linux containers.
   131         -    - So researchers get root access to a familiar environment. *##*
          129  +    - So researchers get root access to a familiar environment.
   132    130     - provides direct interfaces to allow low-level interaction of experiments
   133         -    with the CN bypassing the CD. *##*
          131  +    with the CN bypassing the CD.
   134    132     - runs CONFINE control software
   135    133       - uses LXC tools to manage containers and enforce resource limits,
   136    134         isolation and node stability.
   137    135       - uses traffic control, filtering and anonymization to ensure network
   138         -      stability, isolation and privacy (partialy implemented). *##*
          136  +      stability, isolation and privacy (partialy implemented).
   139    137   - The recovery device (not implemented) can force a remote hardware reboot of
   140    138     the RD in case it hangs.  It also helps with upgrade and recovery. *##*
   141    139   
   142    140   * Experiments support
   143    141   # Axel: Turn around as of mail: from PoV of researcher: 1) testbed through API, choose nodes, 2) login OoB, 3) auto creation, 4) specific interfaces.
   144    142   Researchers can configure slivers with different types of network interfaces
   145    143   depending on the connectivity needs of experiments.  For instance, to *##*