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 Unified Diffs Ignore Whitespace Patch

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

45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
..
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
..
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
  the fairness between their users, and their diversity but also
  their instability.
- It's important to note that all Community-Lab's software and documentation
  is “free as in freedom” so you can use them to setup your own CONFINE
  testbed. *##*

** Community-Lab as community infrastructure

- Besides supporting experimentation, CONFINE helps physically extend CNs *##*
  not only with new Community-Lab nodes, but also with new links…
- … and even services hosted in nodes like web servers, video broadcast
  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. *##*
................................................................................
- 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
  for describing CN nodes, the lower-level Wibed testbed, and the quick mesh
  project distro.
................................................................................
* Future
- In the near future we plan to work further 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 kinds 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:







<







 







|
|

|
|


|
|







 







|
|












45
46
47
48
49
50
51

52
53
54
55
56
57
58
..
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
..
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
  the fairness between their users, and their diversity but also
  their instability.
- It's important to note that all Community-Lab's software and documentation
  is “free as in freedom” so you can use them to setup your own CONFINE
  testbed. *##*

** Community-Lab as community infrastructure

- Besides supporting experimentation, CONFINE helps physically extend CNs *##*
  not only with new Community-Lab nodes, but also with new links…
- … and even services hosted in nodes like web servers, video broadcast
  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. *##*
................................................................................
- 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 hosts (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 also 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. *##*
- Finally, 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.
................................................................................
* Future
- In the near future we plan to work further 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.
- Finally, we will be gradually opening the Community-Lab testbed to all kinds
  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: