Community-Lab introduction

Differences From Artifact [c9593ab5d1]:

• File script.txt — part of check-in [47e4dbffde] at 2012-10-07 22:48:21 on branch trunk — Don't hover along experiment example, just show the labelled version. (user: ivan, size: 11552) [annotate] [blame] [check-ins using]

To Artifact [31bfcbf1ed]:

• File script.txt — part of check-in [7e709fd686] at 2012-10-07 23:13:38 on branch trunk — Colorise labels of interactions diagram. (user: ivan, size: 11506) [annotate] [blame] [check-ins using]

   172    172   through an API that can be used to study the testbed itself, or to implement
   173    173   external services like node monitoring and selection.
   174    174   
   175    175   ** An example experiment
   176    176   to show how the testbed works.  We'll create two slivers which ping each
   177    177   other. *##*
   178    178   
   179         -# Use summary diagram, maybe colorise labels.
   180    179   1. The researcher first contacts the server and registers a slice description
   181    180      which specifies a template for slivers (e.g. Debian Squeeze) and includes
   182    181      data and programs to setup slivers and run experiments.
   183    182   
   184    183      The researcher chooses two nodes and registers sliver descriptions for them
   185    184      in the previous slice.  Each one includes a public interface to the CN.
   186    185