Changes between Version 4 and Version 5 of FeddMultiSwapExample

Timestamp:

Sep 21, 2011 2:34:14 PM (13 years ago)

Author:

faber

Comment:

--

FeddMultiSwapExample

@@ -106 +106 @@
 
 {{{
-localname: faber-multi
-fedid: b4339d8a339097e87ed5624a36b584fe95b0ea0d
-status: active
+$ fedd_multistatus.py 
+faber-multi:b4339d8a339097e87ed5624a36b584fe95b0ea0d:active
 }}}
 
-Experiments can also be "failed" which means it will not come up, and a couple other states.
+Experiments can also be "failed" which means it will not come up, and a couple other self-explanatory states.
 
 Because creation takes a while, users want to see what's going on, even if it is somewhat cryptic.  There are several ways to do this.  The [FeddCommands#fedd_spewlog.py fedd_spewlog.py] command prints the fedd swapin log to stdout and terminates when the experiment fails or activates.  For example:
@@ -140 +139 @@
 21 Sep 11 14:05:10 fedd.experiment_control.faber-multi Waiting for sub threads (it has been 8 mins)
 }}}
+
+Once the DETER experiments begin to swap in, you can watch the activity logs on the [http://www.isi.deterlab.net DETER web interface] to see what the individual experiments are doing.  In this example, you would look at SAFER/faber-multi-b and TIED/faber-multi-a.  The projects come from knowing the projects to which each sub-part was assigned; the experiment names come from the log.
+
+The fedd logs are also world-readable on users.isi.deterlab.net.  To watch a multi-party swap-in, the following logs may be interesting:
+
+{{{
+/var/log/fedd.log                           # the main experiment controller log
+/var/log/fedd.deter.log                     # the log for the DETER testbed access controller (the component swapping experiments)
+/var/log/fedd.internal.log                  # the log for the access controller handing out VLANs to interconnect on DETER
+}}}
+
+The easiest way to view them is:
+{{{
+$ tail -f /var/log/fedd.log
+}}}
+
+== Experiment Status ==
+
+Once the experiment is started you can look at and control the individual pieces using standard DETER interfaces.  You can get the topology from the [FeddCommands#fedd_ftopo.py fedd_ftopo.py] command.
+
+{{{
+$ fedd_ftopo.py --experiment_name faber-multi
+d:pc027.isi.deterlab.net:deter/b
+e:pc020.isi.deterlab.net:deter/b
+a:pc009.isi.deterlab.net:deter/a
+b:pc044.isi.deterlab.net:deter/a
+c:pc022.isi.deterlab.net:deter/b
+}}}
+
+You can manipulate the various parts by logging into the machines or using SEER.