Changes between Version 12 and Version 13 of OldFeddAbout

Timestamp:

Jun 5, 2010 11:13:25 AM (14 years ago)

Author:

faber

Comment:

--

OldFeddAbout

@@ -168 +168 @@
 = Experiments =
 
-A federated experiment exports a master testbed's runtime environment
-into the other testbeds.  The resulting experiment exports the shared
-file space of the home testbed, though a different filesystem, SMB, is
-used to export it.  Emulab events can be sent to nodes throughout the
-federated experiment, though some naming slight-of-hand may be required.
-Users who want to reboot nodes or links in federated testbeds will need
-to access those testbeds directly using the credentials provided by
-fedd.
-
-Currently experiments are described in the same ns2 syntax that DETER
+A federated experiment combines resources from multiple independently administered testbeds into a cohesive environment for experimentation.  Earlier versions of fedd enforced a Master/Slave relationship with one emulab project exporting its environment to others.  While this model remains viable, current fedd implementations allow compositions of the services and views of the facilities as well as their resources.
+
+Currently experiments can be described in the same ns2 syntax that DETER
 and Emulab use, except that additional annotations for the testbed on
-which to place each node have been ad dded.  (The extension is
-set-node-testbed, and described elsewhere.)  The testbed name here is a
+which to place each node have been added.  (The extension is
+set-node-testbed, and described elsewhere.)  Most users will specify experiments in this format, initially. The testbed name here is a
 local string meaningful to the experimenter.  Each fedd knows some set
 of such strings, and experimenters can also inform fedd of the
 appropriate mapping between local testbed name and fedd address to
 contact.
+
+Fedd also understands experiments expressed in the [FeddPluginArchitecture#TopologyDescriptionLanguage topdl] language that it uses to communicate with facilities.
 
 An experimenter creates an experiment by presenting it to a fedd that
@@ -196 +191 @@
 projects that map into different global testbed-scoped projects.
 
-Once created the user receives the various keys under which he or she
-can access the sub-experiment services and a local and global name by
-which the experiment can be referenced.  (Experiments are identified by
+Once created the user can gather information on the resources allocated to the experiment and where to access them.  (Experiments are identified by
 fedids).  The local name is mnemonic and can be used locally to access
 information about the experiment and to terminate it.  The experimenter