Changes between Version 18 and Version 19 of NewAPI

Timestamp:

May 1, 2015 5:11:06 PM (9 years ago)

Author:

faber

Comment:

--

NewAPI

@@ -17 +17 @@
  Libraries::
   groups of experiments that provide logical organization of experiments into classes or collect experiments with similar scope of interest
+ Realizations::
+  an experiment in progress and its binding to resources.
  
 
@@ -128 +130 @@
  * Storing the experiment specification for repeated use
  * Sharing the experiment specification between users subject to [wiki:NewPolicy policy]
- * Constructing an experiment's environment by calling out through teh Containers SPI
 
 We call the process of constructing the experiment's environment ''realizing'' the experiment.
 
-In order to support experiments that are making minimal use of experiment control systems, the API allows a user to manipulate a realized experiment, including
-
- * viewing topology and state of containers
- * low-level operations on containers (start, shutdown, reconfigure)
-
-These interfaces use filtering and graph analysis to present useful views of large experiments.
+
+=== Libraries ===
+
+A library is a group of related experiments analogous to a circle or project being a group of related users.  Libraries make relationships between experiments explicit so that users can operate on related experiments easily.  As with users, projects, and experiments, libraries have profiles attached that store human-readable metadata about their contents.
+
+Libraries allow researchers and testbed administrators to group similar experiments and make them easy to find.  For example, a library of experiments for new testbed users can be maintained by testbed administrators.  A library of experiments for new members of a class or a research group can be maintained by the instructor or principal investigator.
+
+Access to libraries is controlled using circles as above, so once created, administration of a library can be flexible.  Different libraries will have different policies.
+
+As with experiments, the names of libraries are unique and scoped by a user or project name.  Only users delegated the explicit permission to create a library in the project name space may do so.  Project owners and managers may use this permission to vet libraries.
+
+=== Realizations ===
+
+A realization of an experiment is a binding of experiment description to [wiki:NewAPI#Resources resources] - it is an experiment in progress.  Realizations are made in the context of a circle that determines which researchers can manipulate the realization's resources.  Members of that circle can log into computers, manipulate the orchestration tools, etc.
+
+Realizations are explicit objects because an experiment may be in progress more than once and used by different groups of researchers.
+
+The realization API is primarily concerned with constructing an experiment's environment by calling out through the Containers SPI
+
+We call the process of constructing the experiment's environment ''realizing'' the experiment.
 
 When realizing the experiment, the testbed uses the containers API to configure and control the hardware and software that create the environment.
-
-=== Libraries ===
-
-A library is a group of related experiments analogous to a circle or project being a group of related users.  Libraries make relationships between experiments explicit so that users can operate on related experiments easily.  As with users, projects, and experiments, libraries have profiles attached that store human-readable metadata about their contents.
-
-Libraries allow researchers and testbed administrators to group similar experiments and make them easy to find.  For example, a library of experiments for new testbed users can be maintained by testbed administrators.  A library of experiments for new members of a class or a research group can be maintained by the instructor or principal investigator.
-
-Access to libraries is controlled using circles as above, so once created, administration of a library can be flexible.  Different libraries will have different policies.
-
-As with experiments, the names of libraries are unique and scoped by a user or project name.  Only users delegated the explicit permission to create a library in the project name space may do so.  Project owners and managers may use this permission to vet libraries.
 
 == The Containers API ==