Community-Lab introduction: Diff

Differences From Artifact [d327a8d36a]:

File script.txt — part of check-in [1e2a1f4994] at 2012-09-19 11:02:39 on branch trunk — Mention link info and management data collection for experiments and external services. (user: ivan, size: 12748) [annotate] [blame] [check-ins using]

To Artifact [a8f7ed4cc8]:

File script.txt — part of check-in [ba19604b2a] at 2012-09-19 12:12:48 on branch trunk — Stress cooperation between CN members and Community-Lab. (user: ivan, size: 12578) [annotate] [blame] [check-ins using]

   184    184      programs query sliver properties to decide their behaviour.
   185    185   8. Researchers interact straight with containers if needed (e.g. via SSH) and
   186    186      collect results from them.
   187    187   9. When finished, the researcher tells the server to deactivate and
   188    188      deinstantiate the slice.
   189    189   10. Nodes get the instructions and they stop and remove containers.
   190    190   
   191         -* Community-Lab integration in existing community networks
          191  +* Cooperation between community networks and Community-Lab
   192    192   # CN diagram (buildings and cloud).
   193         -A typical CN looks like this, with most nodes linked using cheap and
   194         -ubiquitous WiFi technology (and less frequently Ethernet, optical fiber or
   195         -others).  The CONFINE project follows three strategies taking into account
   196         -that CNs are production networks with distributed ownership:
          193  +There are different ways.  Given a typical CN like this, with most nodes
          194  +linked using cheap and ubiquitous WiFi technology:
   197    195   
   198    196   # CN diagram extended with CONFINE devices (hover over interesting part).
   199         -- Take an existing node owned by CN members, CONFINE provides a RD and
   200         -  connects it via Ethernet to the CD.  Experiments are restricted to the
   201         -  application layer unless the node owner allows the RD to include a direct
   202         -  interface (i.e. antenna).
   203         -- Extend the CN with complete nodes, CONFINE provides both the CD and the RD
   204         -  and uses a CN member's location.  All but low-level experiments are possible
   205         -  using direct interfaces.
   206         -- Set up a physically separated cloud of nodes, CONFINE extends the CN with a
   207         -  full installation of connected nodes at a site controlled by a partner
   208         -  (e.g. campus).  All kinds of experiments are possible using direct
   209         -  interfaces.  Users are warned about the experimental nature of the network.
          197  +- CN members can provide an existing CD and let CONFINE connect a RD to it via
          198  +  Ethernet.  Experiments are restricted to the application layer unless the
          199  +  node owner allows the RD to include a direct interface (i.e. antenna).
          200  +- CN members can provide a location and let CONFINE set up a complete node
          201  +  there (CD and RD).  All but low-level experiments are possible using direct
          202  +  interfaces.  In this way CONFINE helps extend the CN.
          203  +- CONFINE can also extend the CN by setting up a physically separated cloud of
          204  +  connected nodes at a site controlled by a partner (e.g. campus).  All kinds
          205  +  of experiments are possible using direct interfaces.  Users are warned about
          206  +  the experimental nature of the network.
   210    207   
   211    208   * Recap
   212    209   
   213    210   - Community networks are an emerging field to provide citizens with
   214    211     connectivity in a sustainable and distributed manner in which the owners of
   215    212     the networks are the users themselves.
   216    213   - Research on this field is necessary to support CNs' growth while improving