Community-Lab introduction

- Nodes can also be used as infrastructure for cloud infrastructure provided
  and managed by the community for the community: Clommunity project. *##*

* Architecture and technologies
** Testbed architecture
- Community-Lab consists of a set of nodes (managed by CN members) that follow
  the configuration in a set of servers (managed by testbed operators).
- All components in the testbed become reachable via a management network,
  implemented as a VPN IPv6 overlay.
- Researchers define experiments (so called slices) in a server.
- Nodes use a REST API to get those definitions from servers and run several
  of them simultaneously as VMs (so called slivers). *##*



** Technologies
- Nodes are connected via Ethernet to normal community devices.
- Nodes are moderately powerful computers running OpenWrt with a daemon
  written in Lua.  Slivers are implemented as Linux containers.  We are
  working on safe node upgrade using kexec.
- The GUI and REST API in servers are implemented as Django applications.
- The management network overlay is a tinc mesh VPN.
- We use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT) package
  for development and testing.




























# Local Variables:
# mode: org
# End:

- Nodes can also be used as infrastructure for cloud infrastructure provided
  and managed by the community for the community: Clommunity project. *##*

* Architecture and technologies
** Testbed architecture
- Community-Lab consists of a set of nodes (managed by CN members) that follow
  the configuration in a set of servers (managed by testbed operators).
- All components in the testbed become reachable via a dedicated management
  network implemented as an IPv6 overlay.
- Researchers define experiments (so called slices) in a server.
- Nodes use a REST API to get those definitions from servers and run several
  of them simultaneously as VMs (so called slivers).
- Slivers can access the CN via NAT, natively at the network layer, or in an
  isolated VLAN for routing experiments. *##*

** Technologies
- Nodes are connected via Ethernet to normal community devices.
- Nodes are moderately powerful computers running OpenWrt with a daemon
  written in Lua.  Slivers are implemented as Linux containers.  We are
  working on safe node upgrade using kexec.
- The GUI and REST API in servers are implemented as Django applications.
- The IPv6 overlay used for the management network is a tinc mesh VPN.
- We use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT) package
  for development and testing. *##*

* Collaborations
- CONFINE actively collaborates to the development of several Free software
  projects: the OpenWrt router distro, the BMX6 and OLSR mesh routing
  protocols, the DLEP protocol for collecting link characteristics, the NodeDB
  for describing CN nodes, the lower-level Wibed testbed, and the quick mesh
  project distro.
- CONFINE also collaborates in events like the Wireless Battle Mesh and the
  International Summit for Community Wireless Netwroks. *##*

* Future
- In the near future we plan to work on the testing, stabilization and
  documentation of the testbed to make it more maintainable and usable for the
  long term.
- We will also start work on federating CONFINE testbeds between themselves
  and with PlanetLab-like testbeds using the Slice-based
  Federation Architecture.
- We will be gradually opening the Community-Lab testbed to all kind of
  external users in the networking and academic communities. *##*

* Participate!
- So this was a very schematic summary about community networks, the CONFINE
  project and its Community-Lab testbed.
- For more information you can visit these links or meet us in person in the
  CONFINE stand in the K building.

(Questions? Thanks!)

# Local Variables:
# mode: org
# End:

# Architecture and technologies

<!--- testbed architecture diagram --->
- Testbed
    - Nodes, servers, management network
    - Researchers, slices and slivers


<!--- overlay logos on top of diagram --->
- Nodes: OpenWrt, Lua, LXC, kexec
- Servers: Django
- Management network: tinc
- Software development: Git, Redmine, Jenkins, VCT

# Collaborations
................................................................................
Meet us at the CONFINE stand in the K building!

More info:

- <http://community-lab.net/>
- <http://confine-project.eu/>

© 2014 Associació Pangea  
[Creative Commons Attribution-ShareAlike][cc-by-sa]

[cc-by-sa]: http://creativecommons.org/licenses/by-sa/4.0/
    "Creative Commons — Attribution-ShareAlike 4.0 International — CC BY-SA 4.0"

# Architecture and technologies

<!--- testbed architecture diagram --->
- Testbed
    - Nodes, servers, management network
    - Researchers, slices and slivers
    - Sliver connectivity: NAT, native L3, isolated L2
<!--- overlay CD and RD pictures --->
<!--- overlay logos on top of diagram --->
- Nodes: OpenWrt, Lua, LXC, kexec
- Servers: Django
- Management network: tinc
- Software development: Git, Redmine, Jenkins, VCT

# Collaborations
................................................................................
Meet us at the CONFINE stand in the K building!

More info:

- <http://community-lab.net/>
- <http://confine-project.eu/>

© 2014 The CONFINE project  
[Creative Commons Attribution-ShareAlike][cc-by-sa]

[cc-by-sa]: http://creativecommons.org/licenses/by-sa/4.0/
    "Creative Commons — Attribution-ShareAlike 4.0 International — CC BY-SA 4.0"