Community-Lab introduction

Check-in [07f607dbef]
Login
Overview
Comment:Completed script and review of slide points.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | fosdem-2014
Files: files | file ages | folders
SHA1:07f607dbefd1e0cc3cc6a686dbc23bff45f720ef
User & Date: ivan on 2014-01-24 15:16:58
Other Links: manifest | tags
Context
2014-01-24
15:59
Improve readability of script (introduction part). check-in: 67a12d22c5 user: ivan tags: fosdem-2014
15:16
Completed script and review of slide points. check-in: 07f607dbef user: ivan tags: fosdem-2014
2014-01-23
16:16
Work on Community-Lab as community infrastructure, architecture and technologies. check-in: 418b44e23d user: ivan tags: fosdem-2014
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

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

    46     46   - Nodes can also be used as infrastructure for cloud infrastructure provided
    47     47     and managed by the community for the community: Clommunity project. *##*
    48     48   
    49     49   * Architecture and technologies
    50     50   ** Testbed architecture
    51     51   - Community-Lab consists of a set of nodes (managed by CN members) that follow
    52     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.
           53  +- All components in the testbed become reachable via a dedicated management
           54  +  network implemented as an IPv6 overlay.
    55     55   - Researchers define experiments (so called slices) in a server.
    56     56   - Nodes use a REST API to get those definitions from servers and run several
    57         -  of them simultaneously as VMs (so called slivers). *##*
           57  +  of them simultaneously as VMs (so called slivers).
           58  +- Slivers can access the CN via NAT, natively at the network layer, or in an
           59  +  isolated VLAN for routing experiments. *##*
    58     60   
    59     61   ** Technologies
    60     62   - Nodes are connected via Ethernet to normal community devices.
    61     63   - Nodes are moderately powerful computers running OpenWrt with a daemon
    62     64     written in Lua.  Slivers are implemented as Linux containers.  We are
    63     65     working on safe node upgrade using kexec.
    64     66   - The GUI and REST API in servers are implemented as Django applications.
    65         -- The management network overlay is a tinc mesh VPN.
           67  +- The IPv6 overlay used for the management network is a tinc mesh VPN.
    66     68   - We use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT) package
    67         -  for development and testing.
           69  +  for development and testing. *##*
           70  +
           71  +* Collaborations
           72  +- CONFINE actively collaborates to the development of several Free software
           73  +  projects: the OpenWrt router distro, the BMX6 and OLSR mesh routing
           74  +  protocols, the DLEP protocol for collecting link characteristics, the NodeDB
           75  +  for describing CN nodes, the lower-level Wibed testbed, and the quick mesh
           76  +  project distro.
           77  +- CONFINE also collaborates in events like the Wireless Battle Mesh and the
           78  +  International Summit for Community Wireless Netwroks. *##*
           79  +
           80  +* Future
           81  +- In the near future we plan to work on the testing, stabilization and
           82  +  documentation of the testbed to make it more maintainable and usable for the
           83  +  long term.
           84  +- We will also start work on federating CONFINE testbeds between themselves
           85  +  and with PlanetLab-like testbeds using the Slice-based
           86  +  Federation Architecture.
           87  +- We will be gradually opening the Community-Lab testbed to all kind of
           88  +  external users in the networking and academic communities. *##*
           89  +
           90  +* Participate!
           91  +- So this was a very schematic summary about community networks, the CONFINE
           92  +  project and its Community-Lab testbed.
           93  +- For more information you can visit these links or meet us in person in the
           94  +  CONFINE stand in the K building.
           95  +
           96  +(Questions? Thanks!)
    68     97   
    69     98   # Local Variables:
    70     99   # mode: org
    71    100   # End:

Modified slides,lightning.txt from [03d8f482fb] to [410b8c2bec].

    50     50   
    51     51   # Architecture and technologies
    52     52   
    53     53   <!--- testbed architecture diagram --->
    54     54   - Testbed
    55     55       - Nodes, servers, management network
    56     56       - Researchers, slices and slivers
           57  +    - Sliver connectivity: NAT, native L3, isolated L2
           58  +<!--- overlay CD and RD pictures --->
    57     59   <!--- overlay logos on top of diagram --->
    58     60   - Nodes: OpenWrt, Lua, LXC, kexec
    59     61   - Servers: Django
    60     62   - Management network: tinc
    61     63   - Software development: Git, Redmine, Jenkins, VCT
    62     64   
    63     65   # Collaborations
................................................................................
    89     91   Meet us at the CONFINE stand in the K building!
    90     92   
    91     93   More info:
    92     94   
    93     95   - <http://community-lab.net/>
    94     96   - <http://confine-project.eu/>
    95     97   
    96         -© 2014 Associació Pangea  
           98  +© 2014 The CONFINE project  
    97     99   [Creative Commons Attribution-ShareAlike][cc-by-sa]
    98    100   
    99    101   [cc-by-sa]: http://creativecommons.org/licenses/by-sa/4.0/
   100    102       "Creative Commons — Attribution-ShareAlike 4.0 International — CC BY-SA 4.0"