Community-Lab introduction

Differences From Artifact [ebb632a7b6]:

• File script,lightning.txt — part of check-in [908a6d1f8b] at 2014-01-30 15:34:19 on branch fosdem-2014 — Show slices and slivers in additional step in arch diagram animation. (user: ivan, size: 5937) [annotate] [blame] [check-ins using]

To Artifact [0344c1f432]:

• File script,lightning.txt — part of check-in [33d4d26491] at 2014-01-30 15:36:14 on branch fosdem-2014 — Minor tweak to slide change in script. (user: ivan, size: 5937) [annotate] [blame] [check-ins using]

    52     52   - Besides supporting experimentation, *##* CONFINE helps physically extend CNs
    53     53     not only with new Community-Lab nodes, but also with new links…
    54     54   - … and even services hosted in nodes like web servers, video broadcast
    55     55     stations, etc. to be used by the community. *##*
    56     56   - In a more sophisticated approach, nodes can also be used to implement cloud
    57     57     infrastructure provided and managed by the community for the community.
    58     58     This is the mission of the Clommunity project.
           59  +- Now, how does the Community-Lab testbed work? *##*
    59     60   
    60     61   * Architecture and technologies
    61     62   ** Testbed architecture
    62         -- Now, how does the Community-Lab testbed work? *##*
    63     63   - It consists of a set of nodes (managed by CN members) that follow the
    64     64     configuration in a set of servers (managed by testbed operators).
    65     65   - All components in the testbed become reachable via a dedicated management
    66     66     network implemented as an IPv6 overlay. *##*
    67     67   - Then researchers define experiments (the so called slices) in a server.
    68     68   - And nodes use a REST API to get those definitions from servers and run
    69     69     several of them simultaneously as VMs (the so called slivers).