Community-Lab introduction

Check-in [0628c0f2b2]
Login
Overview
Comment:Missing slide transition in script.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 0628c0f2b2bd9f7cf78e63f79ac15780ce343638
User & Date: ivan on 2013-01-16 14:40:28
Other Links: manifest | tags
Context
2013-01-16
14:47
Remove extra slide transition from presentation script. check-in: fceec24142 user: ivan tags: trunk, clommunity-1.0.0
14:40
Missing slide transition in script. check-in: 0628c0f2b2 user: ivan tags: trunk
14:13
Change IBBT by iMinds in presentation script. check-in: aa146bc48f user: ivan tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Modified script.txt from [e8744e009a] to [43e85ca7aa].

37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
  Main inspiration for Community-Lab. *##*

** Community-Lab: a testbed for community networks
- Community-Lab is the testbed developed by CONFINE.
- Integrates and extends the participating community networks.
- Using the FEDERICA research backbone for interconnection. *##*
- All Community-Lab's software and documentation is “free as in freedom” so
  people can use it to setup their own CONFINE testbed.

* Requirements and challenges
A testbed has requirements that are challenged by the unique characteristics
of CNs.  For instance, how to *##*

** Simple management vs. Distributed node ownership
- manage devices belonging to diverse owners? *##*







|







37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
  Main inspiration for Community-Lab. *##*

** Community-Lab: a testbed for community networks
- Community-Lab is the testbed developed by CONFINE.
- Integrates and extends the participating community networks.
- Using the FEDERICA research backbone for interconnection. *##*
- All Community-Lab's software and documentation is “free as in freedom” so
  people can use it to setup their own CONFINE testbed. *##*

* Requirements and challenges
A testbed has requirements that are challenged by the unique characteristics
of CNs.  For instance, how to *##*

** Simple management vs. Distributed node ownership
- manage devices belonging to diverse owners? *##*