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: |
e9ca6e2167446df5f97d422e4d922945 |
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
Modified script,lightning.txt from [3af26aa0d6] to [f08065b5aa].
45 45 the fairness between their users, and their diversity but also 46 46 their instability. 47 47 - It's important to note that all Community-Lab's software and documentation 48 48 is “free as in freedom” so you can use them to setup your own CONFINE 49 49 testbed. *##* 50 50 51 51 ** Community-Lab as community infrastructure 52 -- Besides supporting experimentation, CONFINE helps physically extend CNs *##* 52 +- Besides supporting experimentation, *##* CONFINE helps physically extend CNs 53 53 not only with new Community-Lab nodes, but also with new links… 54 54 - … and even services hosted in nodes like web servers, video broadcast 55 55 stations, etc. to be used by the community. *##* 56 56 - In a more sophisticated approach, nodes can also be used to implement cloud 57 57 infrastructure provided and managed by the community for the community. 58 - This is the mission of the Clommunity project. *##* 58 + This is the mission of the Clommunity project. 59 59 60 60 * Architecture and technologies 61 61 ** Testbed architecture 62 -- How does the Community-Lab testbed work? 62 +- Now, how does the Community-Lab testbed work? *##* 63 63 - It consists of a set of nodes (managed by CN members) that follow the 64 64 configuration in a set of servers (managed by testbed operators). 65 65 - All components in the testbed become reachable via a dedicated management 66 66 network implemented as an IPv6 overlay. 67 67 - Then researchers define experiments (the so called slices) in a server. 68 68 - And nodes use a REST API to get those definitions from servers and run 69 69 several of them simultaneously as VMs (the so called slivers).