Differences From
Artifact [0344c1f432]:
42 42 resources on a best effort basis, and having as few hardwired management
43 43 mechanisms as possible.
44 44 - However, it supports the peculiarities of CNs: their distributed ownership,
45 45 the fairness between their users, and their diversity but also
46 46 their instability.
47 47 - It's important to note that all Community-Lab's software and documentation
48 48 is “free as in freedom” so you can use them to setup your own CONFINE
49 - testbed. *##*
50 -
51 -** Community-Lab as community infrastructure
52 -- Besides supporting experimentation, *##* CONFINE helps physically extend CNs
53 - not only with new Community-Lab nodes, but also with new links…
54 -- … and even services hosted in nodes like web servers, video broadcast
55 - stations, etc. to be used by the community. *##*
56 -- In a more sophisticated approach, nodes can also be used to implement cloud
57 - infrastructure provided and managed by the community for the community.
58 - This is the mission of the Clommunity project.
59 -- Now, how does the Community-Lab testbed work? *##*
49 + testbed.
50 +- Now let's see how Community-Lab works. *##*
60 51
61 52 * Architecture and technologies
62 53 ** Testbed architecture
63 54 - It consists of a set of nodes (managed by CN members) that follow the
64 55 configuration in a set of servers (managed by testbed operators).
65 56 - All components in the testbed become reachable via a dedicated management
66 57 network implemented as an IPv6 overlay. *##*
................................................................................
77 68 implemented as light Linux containers. We are also working on safe node
78 69 upgrade using kexec. *##*
79 70 - The GUI and REST API in servers are implemented as Django applications.
80 71 - The IPv6 overlay used for the management network is a tinc mesh VPN. *##*
81 72 - Finally, we use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT)
82 73 package for development and testing. *##*
83 74
75 +* Community-Lab as community infrastructure
76 +- Besides supporting experimentation, *##* CONFINE helps physically extend CNs
77 + not only with new Community-Lab nodes, but also with new links…
78 +- … and even services hosted in nodes like web servers, video broadcast
79 + stations, etc. to be used by the community. *##*
80 +- In a more sophisticated approach, nodes can also be used to implement cloud
81 + infrastructure provided and managed by the community for the community.
82 + This is the mission of the Clommunity project. *##*
83 +
84 84 * Collaborations
85 85 - CONFINE actively collaborates to the development of several Free software
86 86 projects: the OpenWrt router distro, the BMX6 and OLSR mesh routing
87 87 protocols, the DLEP protocol for collecting link characteristics, the NodeDB
88 88 for describing CN nodes, the lower-level Wibed testbed, and the quick mesh
89 89 project distro.
90 90 - CONFINE also collaborates in events like the Wireless Battle Mesh and the