Overview
| Comment: | Move section on CN extension after arch and technologies. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | fosdem-2014 |
| Files: | files | file ages | folders |
| SHA1: |
069a82906eee470411125646719c81a4 |
| User & Date: | ivan on 2014-02-02 10:49:44 |
| Other Links: | branch diff | manifest | tags |
Context
|
2014-02-02
| ||
| 10:49 | Move section on CN extension after arch and technologies. Leaf check-in: 069a82906e user: ivan tags: fosdem-2014 | |
| 10:38 | Remove odd reference to technologies and services in slides. check-in: 39aafe9659 user: ivan tags: fosdem-2014 | |
Changes
Modified script,lightning.txt from [0344c1f432] to [5bcf7800bd].
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
..
77
78
79
80
81
82
83
84
85
86
87
88
89
90
|
resources on a best effort basis, and having as few hardwired management mechanisms as possible. - However, it supports the peculiarities of CNs: their distributed ownership, 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. - Now, how does the Community-Lab testbed work? *##* * Architecture and technologies ** Testbed architecture - 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. *##* ................................................................................ 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. - CONFINE also collaborates in events like the Wireless Battle Mesh and the |
|
<
<
<
<
<
<
<
<
<
<
>
>
>
>
>
>
>
>
>
>
|
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
..
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
|
resources on a best effort basis, and having as few hardwired management mechanisms as possible. - However, it supports the peculiarities of CNs: their distributed ownership, 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. - Now let's see how Community-Lab works. *##* * Architecture and technologies ** Testbed architecture - 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. *##* ................................................................................ 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. *##* * 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. *##* * 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 |
Modified slides,lightning.txt from [23452350d0] to [38e08fedca].
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
...
133
134
135
136
137
138
139
140
141
142
143
144
145
146
|
- Heavily customized for CNs:
- Some decentralization
- Fair to other users
(no spying, no low-level, routing & above)
- Simple, tolerant to network failures
- Free software: build your own testbed!
# Community-Lab as community infrastructure
- Extend CNs **[+]**
- Community-Lab for hosting services
- [Clommunity](http://clommunity-project.eu/): community clouds
# … Extend CNs
# Community-Lab as community infrastructure
- Extend CNs (with Community-Lab nodes and links)
- Community-Lab for hosting services
- [Clommunity](http://clommunity-project.eu/): community clouds
# Architecture and technologies (1/6)
# Architecture and technologies (2/6)
................................................................................
# Architecture and technologies (6/6)
# Collaborations
- [OpenWrt](https://openwrt.org/)
- [BMX6](http://bmx6.net/)
- [OLSR](http://olsr.org/)
- [DLEP](https://datatracker.ietf.org/doc/draft-ietf-manet-dlep/)
- [NodeDB](https://github.com/FFM/FFM)
|
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
|
93
94
95
96
97
98
99
100
101
102
103
104
105
106
...
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
|
- Heavily customized for CNs:
- Some decentralization
- Fair to other users
(no spying, no low-level, routing & above)
- Simple, tolerant to network failures
- Free software: build your own testbed!
# Architecture and technologies (1/6)
# Architecture and technologies (2/6)
................................................................................
# Architecture and technologies (6/6)
# Community-Lab as community infrastructure
- Extend CNs **[+]**
- Community-Lab for hosting services
- [Clommunity](http://clommunity-project.eu/): community clouds
# … Extend CNs
# Community-Lab as community infrastructure
- Extend CNs (with Community-Lab nodes and links)
- Community-Lab for hosting services
- [Clommunity](http://clommunity-project.eu/): community clouds
# Collaborations
- [OpenWrt](https://openwrt.org/)
- [BMX6](http://bmx6.net/)
- [OLSR](http://olsr.org/)
- [DLEP](https://datatracker.ietf.org/doc/draft-ietf-manet-dlep/)
- [NodeDB](https://github.com/FFM/FFM)
|