1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
..
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
..
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
#+title: Community-Lab: A Community Networking Testbed for the Future Internet
* Introduction
** Community networks
- Origins: In spite of the importance of the Internet, companies left behind
people and regions of little economic interest for them. Some groups
started coordinating the deployment of their own networks for
self-provision.
- Characteristics: Open participation, open and transparent management,
distributed ownership, works and grows according to users' interests.
- Prospective: Strategic importance for the expansion of broadband access
throughout Europe (as stated in the European Digital Agenda).
- A challenge: How to support the growth and sustainability of community
networks by providing the means to conduct experimentally driven research.
................................................................................
- Internet: PlanetLab, planet-scale testbed with resource sharing on nodes.
Main inspiration for Community-Lab.
** Community-Lab: a testbed for community networks
- The testbed developed by CONFINE.
- Integrates and extends three Community Networks: guifi.net, FunkFeuer, AWMN.
# Node maps here for CNs with captures from node DBs.
- Also nodes in participating research institutions.
- Linked together over FEDERICA.
* Challenges and requirements
** Simple management vs. Distributed node ownership
- In contrast with esp. indoors testbeds that belong wholly to the same
entity.
** Features vs. Lightweight, low cost (free & open)
................................................................................
** Heterogeneity vs. Compatibility
- Lots of different devices (disparate connectivity and software openness).
- Lots of different link technologies (wireless, wired, fiber).
* Community-Lab testbed architecture
** Overall architecture
This architecture applies to all testbeds using the CONFINE software. Since
all CONFINE software and documentation is released under Free licenses, anyone
can setup a CONFINE testbed.
# Move over overlay diagram less overlay connections plus overlay network.
- A testbed consists of a set of nodes managed by the same server.
- Server managed by testbed admins.
- Network and node managed by node admins (usually node owners).
- Node admins must adhere to a set of conditions.
- Solves management vs. ownersip problem.
- All components in testbed reachable via management network (tinc mesh VPN).
|
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
..
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
..
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
#+title: Community-Lab: A Community Networking Testbed for the Future Internet
* Introduction
** Community networks
- Origins: In spite of the importance of the Internet, companies and
governments left behind people and regions of little economic interest for
them. Thus some groups started coordinating the deployment of their own
networks for self-provision.
- Characteristics: Open participation, open and transparent management,
distributed ownership, works and grows according to users' interests.
- Prospective: Strategic importance for the expansion of broadband access
throughout Europe (as stated in the European Digital Agenda).
- A challenge: How to support the growth and sustainability of community
networks by providing the means to conduct experimentally driven research.
................................................................................
- Internet: PlanetLab, planet-scale testbed with resource sharing on nodes.
Main inspiration for Community-Lab.
** Community-Lab: a testbed for community networks
- The testbed developed by CONFINE.
- Integrates and extends three Community Networks: guifi.net, FunkFeuer, AWMN.
# Node maps here for CNs with captures from node DBs.
- Also nodes in participating research centres.
- Linked together over the FEDERICA backbone.
- All its software and documentation is released under Free licenses, anyone
can setup a CONFINE testbed like Community-Lab.
* Challenges and requirements
** Simple management vs. Distributed node ownership
- In contrast with esp. indoors testbeds that belong wholly to the same
entity.
** Features vs. Lightweight, low cost (free & open)
................................................................................
** Heterogeneity vs. Compatibility
- Lots of different devices (disparate connectivity and software openness).
- Lots of different link technologies (wireless, wired, fiber).
* Community-Lab testbed architecture
** Overall architecture
This architecture applies to all testbeds using the CONFINE software.
# Move over overlay diagram less overlay connections plus overlay network.
- A testbed consists of a set of nodes managed by the same server.
- Server managed by testbed admins.
- Network and node managed by node admins (usually node owners).
- Node admins must adhere to a set of conditions.
- Solves management vs. ownersip problem.
- All components in testbed reachable via management network (tinc mesh VPN).
|