Community-Lab introduction

Differences From Artifact [f08065b5aa]:

• File script,lightning.txt — part of check-in [e9ca6e2167] at 2014-01-30 15:20:23 on branch fosdem-2014 — Minor improvements to script. (user: ivan, size: 5932) [annotate] [blame] [check-ins using]

To 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]

    59     59   
    60     60   * Architecture and technologies
    61     61   ** Testbed architecture
    62     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         -  network implemented as an IPv6 overlay.
           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).
    70     70   - Slivers can access the CN via NAT, natively at the network layer, or in an
    71     71     isolated VLAN for routing experiments. *##*
    72     72   
    73     73   ** Technologies