Community-Lab introduction

Check-in [e9ca6e2167]
Login
Overview
Comment:Minor improvements to script.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | fosdem-2014
Files: files | file ages | folders
SHA1: e9ca6e2167446df5f97d422e4d922945885416ba
User & Date: ivan on 2014-01-30 15:20:23
Other Links: branch diff | manifest | tags
Context
2014-01-30
15:34
Show slices and slivers in additional step in arch diagram animation. check-in: 908a6d1f8b user: ivan tags: fosdem-2014
15:20
Minor improvements to script. check-in: e9ca6e2167 user: ivan tags: fosdem-2014
15:03
Minor corrections, timed to 11 minutes. check-in: 151c95892d user: ivan tags: fosdem-2014
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Modified script,lightning.txt from [3af26aa0d6] to [f08065b5aa].

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
  the fairness between their users, and their diversity but also
  their instability.
- It's important to note that all Community-Lab's software and documentation
  is “free as in freedom” so you can use them to setup your own CONFINE
  testbed. *##*

** Community-Lab as community infrastructure
- Besides supporting experimentation, CONFINE helps physically extend CNs *##*
  not only with new Community-Lab nodes, but also with new links…
- … and even services hosted in nodes like web servers, video broadcast
  stations, etc. to be used by the community. *##*
- In a more sophisticated approach, nodes can also be used to implement cloud
  infrastructure provided and managed by the community for the community.
  This is the mission of the Clommunity project. *##*

* Architecture and technologies
** Testbed architecture
- How does the Community-Lab testbed work?
- It 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 dedicated management
  network implemented as an IPv6 overlay.
- Then researchers define experiments (the so called slices) in a server.
- And nodes use a REST API to get those definitions from servers and run
  several of them simultaneously as VMs (the so called slivers).







|





|



|







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
  the fairness between their users, and their diversity but also
  their instability.
- It's important to note that all Community-Lab's software and documentation
  is “free as in freedom” so you can use them to setup your own CONFINE
  testbed. *##*

** Community-Lab as community infrastructure
- Besides supporting experimentation, *##* CONFINE helps physically extend CNs
  not only with new Community-Lab nodes, but also with new links…
- … and even services hosted in nodes like web servers, video broadcast
  stations, etc. to be used by the community. *##*
- In a more sophisticated approach, nodes can also be used to implement cloud
  infrastructure provided and managed by the community for the community.
  This is the mission of the Clommunity project.

* Architecture and technologies
** Testbed architecture
- Now, how does the Community-Lab testbed work? *##*
- It 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 dedicated management
  network implemented as an IPv6 overlay.
- Then researchers define experiments (the so called slices) in a server.
- And nodes use a REST API to get those definitions from servers and run
  several of them simultaneously as VMs (the so called slivers).