Community-Lab introduction

Differences From Artifact [d163342981]:

• File script,lightning.txt — part of check-in [36b5514d39] at 2014-01-23 14:32:42 on branch fosdem-2014 — Extend a bit on community networks. (user: ivan, size: 2031) [annotate] [blame] [check-ins using]

To Artifact [66c29b38e7]:

• File script,lightning.txt — part of check-in [418b44e23d] at 2014-01-23 16:16:44 on branch fosdem-2014 — Work on Community-Lab as community infrastructure, architecture and technologies. (user: ivan, size: 3406) [annotate] [blame] [check-ins using]

    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: