Community-Lab introduction

Differences From Artifact [d908ae5804]:

• File script.txt — part of check-in [a0f6c29ca9] at 2012-09-18 09:01:04 on branch trunk — Minor corrections after reading. (user: ivan, size: 12755) [annotate] [blame] [check-ins using]

To Artifact [4fedc4f1ce]:

• File script.txt — part of check-in [d01b126555] at 2012-09-18 17:48:09 on branch trunk — Mention the template on sliver creation. (user: ivan, size: 12789) [annotate] [blame] [check-ins using]

   168    168      nodes, users, slices, slivers, etc.
   169    169   3. The researcher chooses a couple of nodes and creates sliver descriptions
   170    170      for them belonging to the previous slice.  Both sliver descriptions include
   171    171      a public interface to the CN and user-defined properties for telling apart
   172    172      the source sliver from the target one.  Sliver descriptions go to the
   173    173      registry.
   174    174   4. Each of the previous nodes gets a sliver description for it.  If enough
   175         -   resources are available, a container is created with the desired
   176         -   configuration.
          175  +   resources are available, a container is created by applying the desired
          176  +   configuration over the selected template.
   177    177   5. Once the researcher knows that slivers have been instantiated, the server
   178    178      can be commanded to activate the slice.  The server updates the registry.
   179    179   6. When nodes get instructions to activate slivers they start the containers.
   180    180   7. Containers run the experiment setup program and the run program.  The
   181    181      programs query sliver properties to decide their behaviour.
   182    182   8. Researchers interact straight with containers if needed (e.g. via SSH) and
   183    183      collect results from them.