Differences From Artifact [f9cea8dd3d]:
- File script.txt — part of check-in [fceec24142] at 2013-01-16 14:47:15 on branch trunk — Remove extra slide transition from presentation script. (user: ivan, size: 11245) [annotate] [blame] [check-ins using]
To Artifact [8dd7b92f2f]:
- File
script.txt
— part of check-in
[e6eeda4b22]
at
2013-02-20 16:20:35
on branch trunk
— Replace "instantiate" and "activate" with "deploy" and "start".
Only happening in example interaction diagram and description. (user: ivan, size: 11219) [annotate] [blame] [check-ins using]
176 176 data and programs to setup slivers and run experiments. 177 177 178 178 The researcher chooses two nodes and registers sliver descriptions for them 179 179 in the previous slice. Each one includes a public interface to the CN. 180 180 181 181 This and all subsequent changes performed by the researcher are stored in 182 182 the registry, which holds the config of all components in the testbed. 183 -2. The researcher tells the server to instantiate the slice. 183 +2. The researcher tells the server to deploy the slice. 184 184 185 185 Each of the previous nodes gets a sliver description for it. If enough 186 186 resources are available, a container is created by applying the sliver 187 187 configuration over the selected template. 188 -3. Once the researcher knows that slivers have been instantiated, the server 189 - can be commanded to activate the slice. 188 +3. Once the researcher knows that slivers have been deployed, the server can 189 + be commanded to start the slice. 190 190 191 - When nodes get instructions to activate slivers they start containers. 191 + When nodes get instructions to start slivers they start containers. 192 192 193 193 Containers execute the setup & run programs provided by the researcher. 194 194 4. Researchers interact straight with containers if needed (e.g. via SSH) and 195 195 collect results from them. 196 -5. When finished, the researcher tells the server to deactivate the slice. 197 -6. And also to deinstantiate it. 196 +5. When finished, the researcher tells the server to stop the slice. 197 +6. And also to undeploy it. 198 198 199 199 Nodes get instructions and they stop and remove containers, respectively. 200 200 7. If the researcher wants to, the slice itself can be removed. 201 201 202 202 This was a view of the testbed from a research perspective. From the 203 203 community perspective, *##* 204 204