Community-Lab introduction

Check-in [de73cb8db1]
Login
Overview
Comment:Added slide with zooming for experiment interaction example.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: de73cb8db1293919fc396ae78d4fc913f370178a
User & Date: ivan on 2012-09-23 11:51:59
Other Links: manifest | tags
Context
2012-09-23
11:57
Added interaction example slide with step labels. check-in: d6a3077112 user: ivan tags: trunk
11:51
Added slide with zooming for experiment interaction example. check-in: de73cb8db1 user: ivan tags: trunk
10:45
Added slides for supported experiments. check-in: 23af9cf32a user: ivan tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Modified script.txt from [9d4bab6741] to [dba7698cbe].

163
164
165
166
167
168
169
170
171
172
173
174
175
176

177
178
179
180
181
182
183
that can be used to study the testbed itself, or to implement external
services like node monitoring and selection.

** An example experiment
# Event diagram, hover over components explained.
To show how the testbed works: two slivers which ping each other.

1. The researcher first contacts the server and creates a slice description
   which specifies a template for slivers (e.g. Debian Squeeze) and includes
   data and programs to setup slivers and run experiments.
2. This and all subsequent changes performed by the researcher are stored in
   the registry, which holds the config of all components in the testbed.
3. The researcher chooses two nodes and adds sliver descriptions for them in
   the previous slice.  Each one includes a public interface to the CN.

4. Each of the previous nodes gets a sliver description for it.  If enough
   resources are available, a container is created by applying the sliver
   configuration over the selected template.
5. Once the researcher knows that slivers have been instantiated, the server
   can be commanded to activate the slice.
6. When nodes get instructions to activate slivers they start the containers.
7. Containers execute the setup and run programs provided by the researcher.







|




|
|
>







163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
that can be used to study the testbed itself, or to implement external
services like node monitoring and selection.

** An example experiment
# Event diagram, hover over components explained.
To show how the testbed works: two slivers which ping each other.

1. The researcher first contacts the server and registers a slice description
   which specifies a template for slivers (e.g. Debian Squeeze) and includes
   data and programs to setup slivers and run experiments.
2. This and all subsequent changes performed by the researcher are stored in
   the registry, which holds the config of all components in the testbed.
3. The researcher chooses two nodes and registers sliver descriptions for them
   in the previous slice.  Each one includes a public interface to the CN.
   The researcher tells the server to instantiate the slice.
4. Each of the previous nodes gets a sliver description for it.  If enough
   resources are available, a container is created by applying the sliver
   configuration over the selected template.
5. Once the researcher knows that slivers have been instantiated, the server
   can be commanded to activate the slice.
6. When nodes get instructions to activate slivers they start the containers.
7. Containers execute the setup and run programs provided by the researcher.

Modified slides.svg from [c5240c7153] to [0a223832f7].

cannot compute difference between binary files