Community-Lab introduction

Check-in [151c95892d]
Login
Overview
Comment:Minor corrections, timed to 11 minutes.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | fosdem-2014
Files: files | file ages | folders
SHA1: 151c95892d517136fcbb20e1ad1889cf2ebb4b70
User & Date: ivan on 2014-01-30 15:03:21
Other Links: branch diff | manifest | tags
Context
2014-01-30
15:20
Minor improvements to script. check-in: e9ca6e2167 user: ivan tags: fosdem-2014
15:03
Minor corrections, timed to 11 minutes. check-in: 151c95892d user: ivan tags: fosdem-2014
12:50
Remove unnecessary ellipsis in title. check-in: 5cd089a660 user: ivan tags: fosdem-2014
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Modified script,lightning.txt from [0a81b0f647] to [3af26aa0d6].

    45     45     the fairness between their users, and their diversity but also
    46     46     their instability.
    47     47   - It's important to note that all Community-Lab's software and documentation
    48     48     is “free as in freedom” so you can use them to setup your own CONFINE
    49     49     testbed. *##*
    50     50   
    51     51   ** Community-Lab as community infrastructure
    52         -
    53     52   - Besides supporting experimentation, CONFINE helps physically extend CNs *##*
    54     53     not only with new Community-Lab nodes, but also with new links…
    55     54   - … and even services hosted in nodes like web servers, video broadcast
    56     55     stations, etc. to be used by the community. *##*
    57     56   - In a more sophisticated approach, nodes can also be used to implement cloud
    58     57     infrastructure provided and managed by the community for the community.
    59     58     This is the mission of the Clommunity project. *##*
................................................................................
    68     67   - Then researchers define experiments (the so called slices) in a server.
    69     68   - And nodes use a REST API to get those definitions from servers and run
    70     69     several of them simultaneously as VMs (the so called slivers).
    71     70   - Slivers can access the CN via NAT, natively at the network layer, or in an
    72     71     isolated VLAN for routing experiments. *##*
    73     72   
    74     73   ** Technologies
    75         -- Nodes are moderately powerful computers (like this barebone computer)
    76         -  connected via Ethernet to normal community devices (i.e. routers). *##*
           74  +- Nodes are moderately powerful hosts (like this barebone computer) connected
           75  +  via Ethernet to normal community devices (i.e. routers). *##*
    77     76   - Nodes run OpenWrt with a control daemon written in Lua.  Slivers are
    78         -  implemented as light Linux containers.  We are working on safe node upgrade
    79         -  using kexec. *##*
           77  +  implemented as light Linux containers.  We are also working on safe node
           78  +  upgrade using kexec. *##*
    80     79   - The GUI and REST API in servers are implemented as Django applications.
    81     80   - The IPv6 overlay used for the management network is a tinc mesh VPN. *##*
    82         -- We use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT) package
    83         -  for development and testing. *##*
           81  +- Finally, we use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT)
           82  +  package for development and testing. *##*
    84     83   
    85     84   * Collaborations
    86     85   - CONFINE actively collaborates to the development of several Free software
    87     86     projects: the OpenWrt router distro, the BMX6 and OLSR mesh routing
    88     87     protocols, the DLEP protocol for collecting link characteristics, the NodeDB
    89     88     for describing CN nodes, the lower-level Wibed testbed, and the quick mesh
    90     89     project distro.
................................................................................
    94     93   * Future
    95     94   - In the near future we plan to work further on the testing, stabilization and
    96     95     documentation of the testbed to make it more maintainable and usable for the
    97     96     long term.
    98     97   - We will also start work on federating CONFINE testbeds between themselves
    99     98     and with PlanetLab-like testbeds using the Slice-based
   100     99     Federation Architecture.
   101         -- We will be gradually opening the Community-Lab testbed to all kinds of
   102         -  external users in the networking and academic communities. *##*
          100  +- Finally, we will be gradually opening the Community-Lab testbed to all kinds
          101  +  of external users in the networking and academic communities. *##*
   103    102   
   104    103   * Participate!
   105    104   - So this was a very schematic summary about community networks, the CONFINE
   106    105     project and its Community-Lab testbed.
   107    106   - For more information you can visit these links or meet us in person in the
   108    107     CONFINE stand in the K building.
   109    108   
   110    109   (Questions? Thanks!)
   111    110   
   112    111   # Local Variables:
   113    112   # mode: org
   114    113   # End: