Differences From
Artifact [66c29b38e7]:
46 46 - Nodes can also be used as infrastructure for cloud infrastructure provided
47 47 and managed by the community for the community: Clommunity project. *##*
48 48
49 49 * Architecture and technologies
50 50 ** Testbed architecture
51 51 - Community-Lab consists of a set of nodes (managed by CN members) that follow
52 52 the configuration in a set of servers (managed by testbed operators).
53 -- All components in the testbed become reachable via a management network,
54 - implemented as a VPN IPv6 overlay.
53 +- All components in the testbed become reachable via a dedicated management
54 + network implemented as an IPv6 overlay.
55 55 - Researchers define experiments (so called slices) in a server.
56 56 - Nodes use a REST API to get those definitions from servers and run several
57 - of them simultaneously as VMs (so called slivers). *##*
57 + of them simultaneously as VMs (so called slivers).
58 +- Slivers can access the CN via NAT, natively at the network layer, or in an
59 + isolated VLAN for routing experiments. *##*
58 60
59 61 ** Technologies
60 62 - Nodes are connected via Ethernet to normal community devices.
61 63 - Nodes are moderately powerful computers running OpenWrt with a daemon
62 64 written in Lua. Slivers are implemented as Linux containers. We are
63 65 working on safe node upgrade using kexec.
64 66 - The GUI and REST API in servers are implemented as Django applications.
65 -- The management network overlay is a tinc mesh VPN.
67 +- The IPv6 overlay used for the management network is a tinc mesh VPN.
66 68 - We use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT) package
67 - for development and testing.
69 + for development and testing. *##*
70 +
71 +* Collaborations
72 +- CONFINE actively collaborates to the development of several Free software
73 + projects: the OpenWrt router distro, the BMX6 and OLSR mesh routing
74 + protocols, the DLEP protocol for collecting link characteristics, the NodeDB
75 + for describing CN nodes, the lower-level Wibed testbed, and the quick mesh
76 + project distro.
77 +- CONFINE also collaborates in events like the Wireless Battle Mesh and the
78 + International Summit for Community Wireless Netwroks. *##*
79 +
80 +* Future
81 +- In the near future we plan to work on the testing, stabilization and
82 + documentation of the testbed to make it more maintainable and usable for the
83 + long term.
84 +- We will also start work on federating CONFINE testbeds between themselves
85 + and with PlanetLab-like testbeds using the Slice-based
86 + Federation Architecture.
87 +- We will be gradually opening the Community-Lab testbed to all kind of
88 + external users in the networking and academic communities. *##*
89 +
90 +* Participate!
91 +- So this was a very schematic summary about community networks, the CONFINE
92 + project and its Community-Lab testbed.
93 +- For more information you can visit these links or meet us in person in the
94 + CONFINE stand in the K building.
95 +
96 +(Questions? Thanks!)
68 97
69 98 # Local Variables:
70 99 # mode: org
71 100 # End: