56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
|
stations, etc. to be used by the community. *##*
- In a more sophisticated approach, nodes can also be used to implement cloud
infrastructure provided and managed by the community for the community.
This is the mission of the 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 control
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
|
>
|
|
|
|
|
>
|
<
|
|
>
|
|
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
|
stations, etc. to be used by the community. *##*
- In a more sophisticated approach, nodes can also be used to implement cloud
infrastructure provided and managed by the community for the community.
This is the mission of the Clommunity project. *##*
* Architecture and technologies
** Testbed architecture
- How does the Community-Lab testbed work?
- It 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.
- Then researchers define experiments (the so called slices) in a server.
- And nodes use a REST API to get those definitions from servers and run
several of them simultaneously as VMs (the 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 moderately powerful computers (like this barebone computer)
connected via Ethernet to normal community devices (i.e. routers). *##*
- Nodes run OpenWrt with a control daemon written in Lua. Slivers are
implemented as light 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
|