Community-Lab introduction

Check-in [d01b126555]
Login
Overview
Comment:Mention the template on sliver creation.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: d01b126555bf4430b63f3f25dedb05dedb11ddee
User & Date: ivan on 2012-09-18 17:48:09
Other Links: manifest | tags
Context
2012-09-18
22:37
More compact versions of testbed and node architecture and connectivity. check-in: 6f21a57258 user: ivan tags: trunk
17:48
Mention the template on sliver creation. check-in: d01b126555 user: ivan tags: trunk
12:38
Refit CONFINE slices to fit one slice. check-in: 5b33b96f48 user: ivan tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Modified script.txt from [d908ae5804] to [4fedc4f1ce].

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







|
|







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