Community-Lab introduction

Differences From Artifact [ef39386d13]:

• File script.txt — part of check-in [29ee45c594] at 2012-10-07 18:06:29 on branch trunk — Applied some suggestions by Axel. (user: ivan, size: 11543) [annotate] [blame] [check-ins using]

To Artifact [1a6ed75dc5]:

• File script.txt — part of check-in [695af32b2b] at 2012-10-07 18:24:31 on branch trunk — Don't zoom all over the testbed architecture, introduce CN, nodes and admins. (user: ivan, size: 11550) [annotate] [blame] [check-ins using]

    80     80   - CNs suffer from IPv4 scarcity and incompatible addressing besides little
    81     81     IPv6 support.
    82     82   - support testbed spanning different CNs? *##*
    83     83   
    84     84   * Community-Lab testbed architecture
    85     85   ** Overall architecture
    86     86   This is the architecture developed by the CONFINE project to handle the
    87         -previous challenges.  It applies to all testbeds using CONFINE software. *##*
           87  +previous challenges.  It applies to all testbeds using CONFINE software.
    88     88   
    89         -# Axel: Introduce scenario: CNs, nodes, admins.
    90         -# Ivan: Don't zoom.
    91         -- A testbed consists of a set of nodes managed by the same server. *##*
           89  +Here you see two CNs with several nodes connected to them, all managed by
           90  +their respective admins.
           91  +
           92  +- A testbed consists of a set of nodes managed by the same server.
    92     93     - Server managed by testbed admins.
    93     94     - Network and nodes managed by CN members.
    94     95     - Node admins must adhere to testbed terms and conditions.
    95         -  - This decouples testbed management from infrastructure ownership & mgmt. *##*
           96  +  - This decouples testbed management from infrastructure ownership & mgmt.
    96     97   - Testbed management traffic uses a tinc mesh VPN:
    97     98     - Avoids problems with firewalls and private networks in nodes.
    98     99     - Uses IPv6 to avoid address scarcity and incompatibility between CNs.
    99         -  - Mgmt connections are short-lived to tolerate link instability. *##*
          100  +  - Mgmt connections are short-lived to tolerate link instability.
   100    101   - Gateways are entry points to the mgmt network.
   101    102     - They help extend it over multiple CNs by external means (e.g. FEDERICA, the
   102    103       Internet).
   103         -  - They can also route the management network to the Internet. *##*
          104  +  - They can also route the management network to the Internet.
   104    105   - Researchers run experiments in slices spread over several nodes (as
   105    106     slivers). *##*
   106    107   
   107    108   ** Slices, slivers and nodes
   108    109   # Axel: Reverse, from PoV of researcher: select nodes, run as slivers, gruop in slices.
   109    110   - These concepts are inspired in PlanetLab.
   110    111   - A slice is a management concept that groups a set of related slivers.