Changes In Branch fosdem-2014 Through [07f607dbef] Excluding Merge-Ins
This is equivalent to a diff from e6eeda4b22 to 07f607dbef
|
2014-01-24
| ||
| 15:59 | Improve readability of script (introduction part). check-in: 67a12d22c5 user: ivan tags: fosdem-2014 | |
| 15:16 | Completed script and review of slide points. check-in: 07f607dbef user: ivan tags: fosdem-2014 | |
|
2014-01-23
| ||
| 16:16 | Work on Community-Lab as community infrastructure, architecture and technologies. check-in: 418b44e23d user: ivan tags: fosdem-2014 | |
|
2014-01-21
| ||
| 18:02 | Create new branch named "fosdem-2014" check-in: a76c9efc87 user: ivan tags: fosdem-2014 | |
|
2013-04-17
| ||
| 11:15 | Create new branch named "battle-mesh-2013" check-in: 12047cbf52 user: ivan tags: battle-mesh-2013 | |
|
2013-02-20
| ||
| 16:20 |
Replace "instantiate" and "activate" with "deploy" and "start".
Only happening in example interaction diagram and description. Leaf check-in: e6eeda4b22 user: ivan tags: trunk, vienna-2013-1.0.0 | |
| 16:03 | Update subtitle for plenary meeting, remove "soon" from API experiments. check-in: cb602605b9 user: ivan tags: trunk | |
Added script,lightning.txt version [57bdd13a6d].
1 +#+title: Community-Lab: Exploring the Future Internet on Community Networks 2 + 3 +* Introduction 4 +Hello, I'm (Speaker) from (organization), I work at the CONFINE project and 5 +I'm going to talk you about Community-Lab, a community networking testbed for 6 +the future Internet. *##* 7 + 8 +** Community networks 9 +- Infrastructure deployed by organized groups of people for self-provision of 10 + broadband networking that works and grows according to their own interests. 11 +- Like some Free software projects: based on open participation, open and 12 + transparent management, distributed ownership (a big step beyond private and 13 + state-owned infrastructures). 14 +- These also translate into open, free (as in freedom) and neutral networks, 15 + values akin to the Free software movement. Some have mutual agreement texts 16 + similar to Free software liceses. 17 +- The EU in its Digital Agenda regards CNs as fundamental for the 18 + universalization of broadband networking. *##* 19 + 20 +** The CONFINE project 21 +- EU-financed project with several partners: CNs, research institutions and 22 + supporting NGOs. 23 +- Mission: support the sustainable growth of CNs by providing the means to 24 + conduct experimentally driven research. 25 +- Supports other projects advancing or extending CNs via financed Open Calls 26 + (now closed). 27 +- Provides a testbed and associated tools and knowledge for researchers to 28 + experiment on real CNs. *##* 29 + 30 +** Community-Lab 31 +- CONFINE's testbed: an environment built with real hardware taking part in 32 + real community networks to allow realistic experimental research on network 33 + technologies and services. 34 +- Mostly like PlanetLab: global scale, with experiments sharing resources on a 35 + best effort basis, and as few hardwired management mechanisms as possible. 36 +- Supporting the peculiarities of CNs: distributed ownership, fairness between 37 + users, diversity but also instability. 38 +- All Community-Lab's software and documentation is “free as in freedom” so 39 + you can use it to setup your own CONFINE testbed. *##* 40 + 41 +** Community-Lab as community infrastructure 42 + 43 +- CONFINE can help physically extend CNs with new Community-Lab nodes. 44 +- Nodes can also host services like web servers, video broadcast 45 + stations, etc. 46 +- Nodes can also be used as infrastructure for cloud infrastructure provided 47 + and managed by the community for the community: Clommunity project. *##* 48 + 49 +* Architecture and technologies 50 +** Testbed architecture 51 +- Community-Lab consists of a set of nodes (managed by CN members) that follow 52 + the configuration in a set of servers (managed by testbed operators). 53 +- All components in the testbed become reachable via a dedicated management 54 + network implemented as an IPv6 overlay. 55 +- Researchers define experiments (so called slices) in a server. 56 +- Nodes use a REST API to get those definitions from servers and run several 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. *##* 60 + 61 +** Technologies 62 +- Nodes are connected via Ethernet to normal community devices. 63 +- Nodes are moderately powerful computers running OpenWrt with a daemon 64 + written in Lua. Slivers are implemented as Linux containers. We are 65 + working on safe node upgrade using kexec. 66 +- The GUI and REST API in servers are implemented as Django applications. 67 +- The IPv6 overlay used for the management network is a tinc mesh VPN. 68 +- We use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT) package 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!) 97 + 98 +# Local Variables: 99 +# mode: org 100 +# End:
Added slides,lightning.txt version [410b8c2bec].
1 +% Community-Lab: Exploring the Future Internet on Community Networks 2 +% Ivan Vilata-i-Balaguer <ivan@pangea.org> (Pangea/CONFINE project) 3 +% FOSDEM 2014 4 + 5 +# Community networks (CNs) 6 + 7 +- Broadband self-provision 8 +- Similar to Free software: 9 + - Open participation & management, 10 + distributed ownership 11 + <!--- private / public / community ---> 12 + - Open, Free, neutral networks 13 + - Mutual agreement texts 14 +- Key for EU Digital Agenda 15 + 16 +# The CONFINE project 17 + 18 +- Partners: 19 + - CNs: guifi.net, Funkfeuer, AWMN 20 + - Research: UPC, FKIE, iMinds 21 + - NGOs: Pangea, OPLAN 22 +<!--- logos ---> 23 +- Support sustainable growth of CNs via research 24 + (technologies & services) 25 +- Help other projects boost CNs (Open Calls) 26 +<!--- OC1 & OC2 project listing ---> 27 +- Provide a testbed for CNs: Community-Lab 28 + 29 +# Community-Lab 30 + 31 +- A testbed built on community networks 32 +- Like PlanetLab: 33 + - Global scale 34 + - Experiments sharing resources 35 + - Best effort 36 + - Unbundled management 37 +- Heavily customized for CNs: 38 + - Some decentralization 39 + - Fair to other users 40 + (no spying, no low-level, routing & above) 41 + - Simple, tolerant to network failures 42 +- Free software: build your own testbed! 43 + 44 +# Community-Lab as community infrastructure 45 + 46 +- Extend CNs with Community-Lab nodes 47 +<!--- Figure from IS4CWN slide #15 ---> 48 +- Community-Lab for hosting services 49 +- [Clommunity](http://clommunity-project.eu/): community clouds 50 + 51 +# Architecture and technologies 52 + 53 +<!--- testbed architecture diagram ---> 54 +- Testbed 55 + - Nodes, servers, management network 56 + - Researchers, slices and slivers 57 + - Sliver connectivity: NAT, native L3, isolated L2 58 +<!--- overlay CD and RD pictures ---> 59 +<!--- overlay logos on top of diagram ---> 60 +- Nodes: OpenWrt, Lua, LXC, kexec 61 +- Servers: Django 62 +- Management network: tinc 63 +- Software development: Git, Redmine, Jenkins, VCT 64 + 65 +# Collaborations 66 + 67 +- [OpenWrt](https://openwrt.org/) 68 +- [BMX6](http://bmx6.net/) 69 +- [OLSR](http://olsr.org/) 70 +- [DLEP](https://datatracker.ietf.org/doc/draft-ietf-manet-dlep/) 71 +- [NodeDB](https://github.com/FFM/FFM) 72 +- [Wibed](http://wiki.confine-project.eu/wibed:start) 73 +- quick mesh project ([qMp](http://qmp.cat/)) 74 +- Wireless Battle of the Mesh ([BattleMesh](http://battlemesh.org/)) 75 +- International Summit for Community Wireless Networks 76 + ([IS4CWN](http://wirelesssummit.org/)) 77 + 78 +# Future 79 + 80 +- Stabilization, maintainability, usability 81 +- Federation with other testbeds 82 + - PlanetLab & others (SFA) 83 + - CONFINE / CONFINE 84 +- Open Community-Lab to external users 85 + - Community members 86 + - Networking developers 87 + - Internship students… 88 + 89 +# Thank you! 90 + 91 +Meet us at the CONFINE stand in the K building! 92 + 93 +More info: 94 + 95 +- <http://community-lab.net/> 96 +- <http://confine-project.eu/> 97 + 98 +© 2014 The CONFINE project 99 +[Creative Commons Attribution-ShareAlike][cc-by-sa] 100 + 101 +[cc-by-sa]: http://creativecommons.org/licenses/by-sa/4.0/ 102 + "Creative Commons — Attribution-ShareAlike 4.0 International — CC BY-SA 4.0"