Changes between Version 2 and Version 3 of FeddMultiSwapExample

Timestamp:

Sep 21, 2011 1:41:58 PM (13 years ago)

Author:

faber

Comment:

--

FeddMultiSwapExample

@@ -1 +1 @@
 = Multi-Party Experiment Creation Example =
 
-This example walks through creating a multiparty experiment from a single experiment description.  That description may have been created from [wiki:FeddMulti#ComposingFragments a compostion program] or created by hand.  We describe the key elements of the experiment description and walk through the creation.
+This example walks through creating a multiparty experiment from a single experiment topology description.  That description may have been created from [wiki:FeddMulti#ComposingFragments a compostion program] or created by hand.  We describe the key elements of the experiment description and walk through the creation.
 
 == Experiment Description ==
 
-The ns-2 description of our example is (topdl version is [attachment:multi-swap-example.xml attached])
+The ns-2 description of our example is ([wiki:FeddPluginArchitecture#TopologyDescriptionLanguage topdl] version is [attachment:multi-swap-example.xml attached])
 
 {{{
@@ -64 +64 @@
 
 }}}
+
+This is an experiment topology containing 5 computers connected mostly by links, but with a single LAN.  The computers are named with the letters a-e, and allocated to 2 parties.  The party names appear in the {{{tb-set-node-testbed}}} commands (and as {{{testbed}}} attributes in the topdl).  Overall the topology looks like (generated by [wiki:FeddCommands#fedd_image.py fedd_image.py] --group testbed --file multi-swap-example.xml --out multi.png):
+
+[[Image(multi.png)]]
+
+The individual topologies are configured using the SERVICE directives in the comments of the ns-2 description.  They can also be given on the command line of [FeddCommands#fedd_create.py fedd_create.py] using '''--service'''.   Currently that is the only way to specify them when starting a topdl experiment.  The format of the line and the '''--service''' option are the same.  Services in general are described [FeddAbout#ExperimentServices elsewhere] as well.
+
+Briefly, the first two lines set the DETER project that will be used to configure each party's area.  The deter/a area will be an experiment owned by the TIED project; deter/b will be configured by the SAFER project.  The '''project_export''' service exports the user configuration and filesystem named by the '''project''' (project=TIED) attribute.
+
+The next three lines configure the SEER experiment control system.  The '''local_seer''' service will add a node named '''control''' to each experiment that is effictively invisible outside the party's area.  Computers will treat that as a SEER controller, and experimenters can connect to it directly to see and manipulate their areas.  The '''seer_master''' service adds a node named seer-master to the experiment that each area's controller will also connect to.  Connecting to the seer-master controller allows thw whole experiment to be viewed and manipulated.
+