Index: diagrams/interactions.dia ================================================================== --- diagrams/interactions.dia +++ diagrams/interactions.dia @@ -982,16 +982,16 @@ - + - #(2) Instantiate + #(2) Deploy slice# @@ -1055,16 +1055,16 @@ - + - #(2) Instantiate# + #(2) Deploy# @@ -1094,16 +1094,16 @@ - + - #(3) Activate + #(3) Start slice# @@ -1134,16 +1134,16 @@ - + - #(3) Activate# + #(3) Start# @@ -1330,16 +1330,16 @@ - + - #(5) Deactivate + #(5) Stop slice# @@ -1370,16 +1370,16 @@ - + - #(6) Deinstantiate# + #(6) Undeploy# @@ -1521,16 +1521,16 @@ - + - #(6) Deinstantiate + #(6) Undeploy slice# @@ -1561,16 +1561,16 @@ - + - #(5) Deactivate# + #(5) Stop# Index: script.txt ================================================================== --- script.txt +++ script.txt @@ -178,25 +178,25 @@ The researcher chooses two nodes and registers sliver descriptions for them in the previous slice. Each one includes a public interface to the CN. This and all subsequent changes performed by the researcher are stored in the registry, which holds the config of all components in the testbed. -2. The researcher tells the server to instantiate the slice. +2. The researcher tells the server to deploy the slice. 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. -3. Once the researcher knows that slivers have been instantiated, the server - can be commanded to activate the slice. +3. Once the researcher knows that slivers have been deployed, the server can + be commanded to start the slice. - When nodes get instructions to activate slivers they start containers. + When nodes get instructions to start slivers they start containers. Containers execute the setup & run programs provided by the researcher. 4. Researchers interact straight with containers if needed (e.g. via SSH) and collect results from them. -5. When finished, the researcher tells the server to deactivate the slice. -6. And also to deinstantiate it. +5. When finished, the researcher tells the server to stop the slice. +6. And also to undeploy it. Nodes get instructions and they stop and remove containers, respectively. 7. If the researcher wants to, the slice itself can be removed. This was a view of the testbed from a research perspective. From the Index: slides.svg ================================================================== --- slides.svg +++ slides.svg cannot compute difference between binary files