Changes between Version 7 and Version 8 of FeddInfoOperation

Timestamp:

Nov 17, 2011 4:08:57 PM (12 years ago)

Author:

faber

Comment:

--

FeddInfoOperation

@@ -17 +17 @@
 === Info Interface ===
 
-The info interface allows a user to request information from the experiment controller about an existing federated experiment.  The request names the experiment.
+The info interface allows a user to request information from the experiment controller about an existing federated experiment.  The request names the experiment.  The information represents the entire experiment.
 
 The info response is broken into three sections, '''Testbed''', '''Element''', and '''Substrate'''.  The '''Testbed''' section tells which testbeds have given elements to the topology.  They are identified by the name the experiment controller knows them by and include the [FeddAbout#ExperimentServices services] used by the testbed and any operations that the testbed supports.  Similarly the substrate and element sections describe the current state of the object, the testbed(s) to which it is bound and the services and operations it supports.
@@ -67 +67 @@
 === Operation Interface ===
 
-The operation interface names the experiment and object on which the operation to be called, names the operation to be invoked and supplies parameters. It returns a success or failure code.
+The operation interface names the experiment and object(s) on which the operation(s) are to be called, names the operation to be invoked and supplies parameters.  The operations are carried out in order given in the request.  The response is the requests annotated with the success or failure information.
+
+These are requests from the user to take action on one or more elements of the topology.  The experiment controller routes the request to the appropriate sub-experiment, using the interfaces below.  The experiment controller collects the responses into a single response to the user.
 
 
+== Access Control Interfaces ===
 
+These are identical in format to the experiment control interfaces, but pertain only to resources at the controller in question.  The other extension is to add information to the success message when a segment is started that gives experiment status in the new format.