Community-Lab introduction

Modified script,lightning.txt from [d163342981] to [66c29b38e7].

    33     33     technologies and services.
    34     34   - Mostly like PlanetLab: global scale, with experiments sharing resources on a
    35     35     best effort basis, and as few hardwired management mechanisms as possible.
    36     36   - Supporting the peculiarities of CNs: distributed ownership, fairness between
    37     37     users, diversity but also instability.
    38     38   - All Community-Lab's software and documentation is “free as in freedom” so
    39     39     you can use it to setup your own CONFINE testbed. *##*
           40  +
           41  +** Community-Lab as community infrastructure
           42  +
           43  +- CONFINE can help physically extend CNs with new Community-Lab nodes.
           44  +- Nodes can also host services like web servers, video broadcast
           45  +  stations, etc.
           46  +- Nodes can also be used as infrastructure for cloud infrastructure provided
           47  +  and managed by the community for the community: Clommunity project. *##*
           48  +
           49  +* Architecture and technologies
           50  +** Testbed architecture
           51  +- Community-Lab consists of a set of nodes (managed by CN members) that follow
           52  +  the configuration in a set of servers (managed by testbed operators).
           53  +- All components in the testbed become reachable via a management network,
           54  +  implemented as a VPN IPv6 overlay.
           55  +- Researchers define experiments (so called slices) in a server.
           56  +- Nodes use a REST API to get those definitions from servers and run several
           57  +  of them simultaneously as VMs (so called slivers). *##*
           58  +
           59  +** Technologies
           60  +- Nodes are connected via Ethernet to normal community devices.
           61  +- Nodes are moderately powerful computers running OpenWrt with a daemon
           62  +  written in Lua.  Slivers are implemented as Linux containers.  We are
           63  +  working on safe node upgrade using kexec.
           64  +- The GUI and REST API in servers are implemented as Django applications.
           65  +- The management network overlay is a tinc mesh VPN.
           66  +- We use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT) package
           67  +  for development and testing.
    40     68   
    41     69   # Local Variables:
    42     70   # mode: org
    43     71   # End:

Modified slides,lightning.txt from [9c7a5a20d3] to [03d8f482fb].

    33     33       - Global scale
    34     34       - Experiments sharing resources
    35     35       - Best effort
    36     36       - Unbundled management
    37     37   - Heavily customized for CNs:
    38     38       - Some decentralization
    39     39       - Fair to other users  
    40         -      (no low-level, disruptive experiments, no spying)
           40  +      (no spying, no low-level, routing & above)
    41     41       - Simple, tolerant to network failures
    42     42   - Free software: build your own testbed!
    43     43   
    44     44   # Community-Lab as community infrastructure
    45     45   
    46         -- CONFINE extends CNs with Community-Lab nodes
           46  +- Extend CNs with Community-Lab nodes
           47  +<!--- Figure from IS4CWN slide #15 --->
    47     48   - Community-Lab for hosting services
    48     49   - [Clommunity](http://clommunity-project.eu/): community clouds
    49     50   
    50     51   # Architecture and technologies
    51     52   
           53  +<!--- testbed architecture diagram --->
    52     54   - Testbed
    53         -- Slices and slivers
    54         -- Node hardware (CD and RD)
    55         -- Django
    56         -- OpenWrt
    57         -- LXC
    58         -- kexec
    59         -- tinc
           55  +    - Nodes, servers, management network
           56  +    - Researchers, slices and slivers
           57  +<!--- overlay logos on top of diagram --->
           58  +- Nodes: OpenWrt, Lua, LXC, kexec
           59  +- Servers: Django
           60  +- Management network: tinc
           61  +- Software development: Git, Redmine, Jenkins, VCT
    60     62   
    61     63   # Collaborations
    62     64   
    63     65   - [OpenWrt](https://openwrt.org/)
    64     66   - [BMX6](http://bmx6.net/)
    65     67   - [OLSR](http://olsr.org/)
    66     68   - [DLEP](https://datatracker.ietf.org/doc/draft-ietf-manet-dlep/)