Community-Lab introduction

Diff
Login

Differences From Artifact [d163342981]:

To Artifact [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: