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: |
de73cb8db1293919fc396ae78d4fc913 |
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
Modified script.txt from [9d4bab6741] to [dba7698cbe].
163 163 that can be used to study the testbed itself, or to implement external 164 164 services like node monitoring and selection. 165 165 166 166 ** An example experiment 167 167 # Event diagram, hover over components explained. 168 168 To show how the testbed works: two slivers which ping each other. 169 169 170 -1. The researcher first contacts the server and creates a slice description 170 +1. The researcher first contacts the server and registers a slice description 171 171 which specifies a template for slivers (e.g. Debian Squeeze) and includes 172 172 data and programs to setup slivers and run experiments. 173 173 2. This and all subsequent changes performed by the researcher are stored in 174 174 the registry, which holds the config of all components in the testbed. 175 -3. The researcher chooses two nodes and adds sliver descriptions for them in 176 - the previous slice. Each one includes a public interface to the CN. 175 +3. The researcher chooses two nodes and registers sliver descriptions for them 176 + in the previous slice. Each one includes a public interface to the CN. 177 + The researcher tells the server to instantiate the slice. 177 178 4. Each of the previous nodes gets a sliver description for it. If enough 178 179 resources are available, a container is created by applying the sliver 179 180 configuration over the selected template. 180 181 5. Once the researcher knows that slivers have been instantiated, the server 181 182 can be commanded to activate the slice. 182 183 6. When nodes get instructions to activate slivers they start the containers. 183 184 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