Community-Lab introduction

Check-in [38cde6816a]
Login
Overview
Comment:Use stacked diagrams for testbed architecture and logos, update script.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | fosdem-2014
Files: files | file ages | folders
SHA1: 38cde6816a1663761ba1aab11d74feb733f3c511
User & Date: ivan on 2014-01-30 12:07:56
Other Links: branch diff | manifest | tags
Context
2014-01-30
12:32
Add slices, slivers and sliver connectivity to testbed architecture diagram. check-in: 6b3bdebd64 user: ivan tags: fosdem-2014
12:07
Use stacked diagrams for testbed architecture and logos, update script. check-in: 38cde6816a user: ivan tags: fosdem-2014
11:50
More small rearrangements to logos in testbed diagram. check-in: 347300a58e user: ivan tags: fosdem-2014
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Modified Makefile from [898a0ad0e5] to [3dc5bf7852].

     1      1   IMGS = imgs/network-public.png imgs/network-private.png imgs/network-community.png \
     2         -	imgs/confine-partners.png imgs/extend-network.png
            2  +	imgs/confine-partners.png imgs/extend-network.png \
            3  +	imgs/testbed.png imgs/testbed-cd-rd.png \
            4  +	imgs/testbed-logos-node.png imgs/testbed-logos-mgmt.png imgs/testbed-logos-devel.png
     3      5   IMGS_BEAMER = imgs/confine,background.pdf
     4      6   
     5      7   
     6      8   .PHONY:	clean
     7      9   
     8     10   all:	slides,lightning.pdf
     9     11   
................................................................................
    29     31   
    30     32   imgs/confine-partners.png:	logos/confine-partners.svg
    31     33   	inkscape -z -C -e $@ -w 1024 $<
    32     34   
    33     35   imgs/extend-network.png:	diagrams/extend-network.svg
    34     36   	inkscape -z -C -e $@ -w 1024 $<
    35     37   
           38  +imgs/testbed.png:	diagrams/testbed-logos.dia
           39  +	dia -e $@ -L testbed -s 1024x $<
           40  +
           41  +imgs/testbed-cd-rd.png:	diagrams/testbed-logos.dia
           42  +	dia -e $@ -L testbed,cd-rd -s 1024x $<
           43  +
           44  +imgs/testbed-logos-node.png:	diagrams/testbed-logos.dia
           45  +	dia -e $@ -L testbed,cd-rd,logos-node -s 1024x $<
           46  +
           47  +imgs/testbed-logos-mgmt.png:	diagrams/testbed-logos.dia
           48  +	dia -e $@ -L testbed,cd-rd,logos-node,logos-mgmt -s 1024x $<
           49  +
           50  +imgs/testbed-logos-devel.png:	diagrams/testbed-logos.dia
           51  +	dia -e $@ -L testbed,cd-rd,logos-node,logos-mgmt,logos-devel -s 1024x $<
           52  +
    36     53   
    37     54   clean:
    38     55   	rm -f $(IMGS) $(IMGS_BEAMER) slides,lightning.pdf slides,lightning.html

Modified script,lightning.txt from [2be8593ac1] to [0a81b0f647].

    56     56     stations, etc. to be used by the community. *##*
    57     57   - In a more sophisticated approach, nodes can also be used to implement cloud
    58     58     infrastructure provided and managed by the community for the community.
    59     59     This is the mission of the Clommunity project. *##*
    60     60   
    61     61   * Architecture and technologies
    62     62   ** Testbed architecture
    63         -- Community-Lab consists of a set of nodes (managed by CN members) that follow
    64         -  the configuration in a set of servers (managed by testbed operators).
           63  +- How does the Community-Lab testbed work?
           64  +- It consists of a set of nodes (managed by CN members) that follow the
           65  +  configuration in a set of servers (managed by testbed operators).
    65     66   - All components in the testbed become reachable via a dedicated management
    66     67     network implemented as an IPv6 overlay.
    67         -- Researchers define experiments (so called slices) in a server.
    68         -- Nodes use a REST API to get those definitions from servers and run several
    69         -  of them simultaneously as VMs (so called slivers).
           68  +- Then researchers define experiments (the so called slices) in a server.
           69  +- And nodes use a REST API to get those definitions from servers and run
           70  +  several of them simultaneously as VMs (the so called slivers).
    70     71   - Slivers can access the CN via NAT, natively at the network layer, or in an
    71     72     isolated VLAN for routing experiments. *##*
    72     73   
    73     74   ** Technologies
    74         -- Nodes are connected via Ethernet to normal community devices.
    75         -- Nodes are moderately powerful computers running OpenWrt with a control
    76         -  daemon written in Lua.  Slivers are implemented as Linux containers.  We are
    77         -  working on safe node upgrade using kexec.
           75  +- Nodes are moderately powerful computers (like this barebone computer)
           76  +  connected via Ethernet to normal community devices (i.e. routers). *##*
           77  +- 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. *##*
    78     80   - The GUI and REST API in servers are implemented as Django applications.
    79         -- The IPv6 overlay used for the management network is a tinc mesh VPN.
           81  +- The IPv6 overlay used for the management network is a tinc mesh VPN. *##*
    80     82   - We use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT) package
    81     83     for development and testing. *##*
    82     84   
    83     85   * Collaborations
    84     86   - CONFINE actively collaborates to the development of several Free software
    85     87     projects: the OpenWrt router distro, the BMX6 and OLSR mesh routing
    86     88     protocols, the DLEP protocol for collecting link characteristics, the NodeDB

Modified slides,lightning.txt from [9f954ade3b] to [2819b0bc48].

   109    109   
   110    110   # Community-Lab as community infrastructure
   111    111   
   112    112   - Extend CNs (with Community-Lab nodes and links)
   113    113   - Community-Lab for hosting services
   114    114   - [Clommunity](http://clommunity-project.eu/): community clouds
   115    115   
   116         -# Architecture and technologies
          116  +# Architecture and technologies (1/5)
          117  +
          118  +![CONFINE testbed architecture](imgs/testbed.png)
          119  +
          120  +# Architecture and technologies (2/5)
          121  +
          122  +![CONFINE testbed architecture](imgs/testbed-cd-rd.png)
          123  +
          124  +# Architecture and technologies (3/5)
          125  +
          126  +![CONFINE testbed architecture](imgs/testbed-logos-node.png)
          127  +
          128  +# Architecture and technologies (4/5)
          129  +
          130  +![CONFINE testbed architecture](imgs/testbed-logos-mgmt.png)
          131  +
          132  +# Architecture and technologies (5/5)
   117    133   
   118         -<!--- testbed architecture diagram --->
   119         -- Testbed
   120         -    - Nodes, servers, management network
   121         -    - Researchers, slices and slivers
   122         -    - Sliver connectivity: NAT, native L3, isolated L2
   123         -<!--- overlay CD and RD pictures --->
   124         -<!--- overlay logos on top of diagram --->
   125         -- Nodes: OpenWrt, Lua, LXC, kexec
   126         -- Servers: Django
   127         -- Management network: tinc
   128         -- Software development: Git, Redmine, Jenkins, VCT
          134  +![CONFINE testbed architecture](imgs/testbed-logos-devel.png)
   129    135   
   130    136   # Collaborations
   131    137   
   132    138   - [OpenWrt](https://openwrt.org/)
   133    139   - [BMX6](http://bmx6.net/)
   134    140   - [OLSR](http://olsr.org/)
   135    141   - [DLEP](https://datatracker.ietf.org/doc/draft-ietf-manet-dlep/)