Community-Lab introduction

Check-in [418b44e23d]
Login
Overview
Comment:Work on Community-Lab as community infrastructure, architecture and technologies.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | fosdem-2014
Files: files | file ages | folders
SHA1: 418b44e23def8241dde3c46f5a2aba0ef1d384ee
User & Date: ivan on 2014-01-23 16:16:44
Other Links: branch diff | manifest | tags
Context
2014-01-24
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
14:32
Extend a bit on community networks. check-in: 36b5514d39 user: ivan tags: fosdem-2014
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Modified script,lightning.txt from [d163342981] to [66c29b38e7].

33
34
35
36
37
38
39




























40
41
42
43
  technologies and services.
- Mostly like PlanetLab: global scale, with experiments sharing resources on a
  best effort basis, and as few hardwired management mechanisms as possible.
- Supporting the peculiarities of CNs: distributed ownership, fairness between
  users, diversity but also instability.
- All Community-Lab's software and documentation is “free as in freedom” so
  you can use it to setup your own CONFINE testbed. *##*





























# Local Variables:
# mode: org
# End:







>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>




33
34
35
36
37
38
39
40
41
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
67
68
69
70
71
  technologies and services.
- Mostly like PlanetLab: global scale, with experiments sharing resources on a
  best effort basis, and as few hardwired management mechanisms as possible.
- Supporting the peculiarities of CNs: distributed ownership, fairness between
  users, diversity but also instability.
- All Community-Lab's software and documentation is “free as in freedom” so
  you can use it to setup your own CONFINE testbed. *##*

** Community-Lab as community infrastructure

- CONFINE can help physically extend CNs with new Community-Lab nodes.
- Nodes can also host services like web servers, video broadcast
  stations, etc.
- Nodes can also be used as infrastructure for cloud infrastructure provided
  and managed by the community for the community: Clommunity project. *##*

* Architecture and technologies
** Testbed architecture
- Community-Lab 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 management network,
  implemented as a VPN IPv6 overlay.
- Researchers define experiments (so called slices) in a server.
- Nodes use a REST API to get those definitions from servers and run several
  of them simultaneously as VMs (so called slivers). *##*

** Technologies
- Nodes are connected via Ethernet to normal community devices.
- Nodes are moderately powerful computers running OpenWrt with a daemon
  written in Lua.  Slivers are implemented as Linux containers.  We are
  working on safe node upgrade using kexec.
- The GUI and REST API in servers are implemented as Django applications.
- The management network overlay is a tinc mesh VPN.
- We use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT) package
  for development and testing.

# Local Variables:
# mode: org
# End:

Modified slides,lightning.txt from [9c7a5a20d3] to [03d8f482fb].

33
34
35
36
37
38
39
40
41
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
    - Global scale
    - Experiments sharing resources
    - Best effort
    - Unbundled management
- Heavily customized for CNs:
    - Some decentralization
    - Fair to other users  
      (no low-level, disruptive experiments, no spying)
    - Simple, tolerant to network failures
- Free software: build your own testbed!

# Community-Lab as community infrastructure

- CONFINE extends CNs with Community-Lab nodes

- Community-Lab for hosting services
- [Clommunity](http://clommunity-project.eu/): community clouds

# Architecture and technologies

- Testbed
- Slices and slivers
- Node hardware (CD and RD)
- Django
- OpenWrt
- LXC
- kexec
- tinc


# Collaborations

- [OpenWrt](https://openwrt.org/)
- [BMX6](http://bmx6.net/)
- [OLSR](http://olsr.org/)
- [DLEP](https://datatracker.ietf.org/doc/draft-ietf-manet-dlep/)







|





|
>





|
|
|
|
|
|
|
|
>







33
34
35
36
37
38
39
40
41
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
67
68
    - Global scale
    - Experiments sharing resources
    - Best effort
    - Unbundled management
- 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 with Community-Lab nodes
<!--- Figure from IS4CWN slide #15 --->
- Community-Lab for hosting services
- [Clommunity](http://clommunity-project.eu/): community clouds

# Architecture and technologies

<!--- testbed architecture diagram --->
- Testbed
    - Nodes, servers, management network
    - Researchers, slices and slivers
<!--- overlay logos on top of diagram --->
- Nodes: OpenWrt, Lua, LXC, kexec
- Servers: Django
- Management network: tinc
- Software development: Git, Redmine, Jenkins, VCT

# Collaborations

- [OpenWrt](https://openwrt.org/)
- [BMX6](http://bmx6.net/)
- [OLSR](http://olsr.org/)
- [DLEP](https://datatracker.ietf.org/doc/draft-ietf-manet-dlep/)