Community-Lab introduction

** An example experiment
to show how the testbed works.  We'll create two slivers which ping each
other. *##*

# Use summary diagram, maybe colorise labels.
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.



   Then 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 containers. *##*

7. Containers execute the setup & run programs provided by the researcher. *##*
8. Researchers interact straight with containers if needed (e.g. via SSH) and
   collect results from them. *##*
9. When finished, the researcher tells the server to deactivate and
   deinstantiate the slice. *##*

10. Nodes get the instructions and they stop and remove containers. *##*


This is a summary of all the previous steps. *##*



* Cooperation between community networks and Community-Lab
can take different forms.  Given a typical CN like this, with most nodes
linked using cheap and ubiquitous WiFi technology: *##*

- CN members can provide an existing CD and let CONFINE connect a RD to it via
  Ethernet.  Experiments are restricted to the application layer unless the

** An example experiment
to show how the testbed works.  We'll create two slivers which ping each
other. *##*

# Use summary diagram, maybe colorise labels.
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.



   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.

   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.

   When nodes get instructions to activate 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.

   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
community perspective, *##*

* Cooperation between community networks and Community-Lab
can take different forms.  Given a typical CN like this, with most nodes
linked using cheap and ubiquitous WiFi technology: *##*

- CN members can provide an existing CD and let CONFINE connect a RD to it via
  Ethernet.  Experiments are restricted to the application layer unless the