Changes between Version 4 and Version 5 of FeddMultiSwapExample


Ignore:
Timestamp:
Sep 21, 2011 2:34:14 PM (8 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FeddMultiSwapExample

    v4 v5  
    106106
    107107{{{
    108 localname: faber-multi
    109 fedid: b4339d8a339097e87ed5624a36b584fe95b0ea0d
    110 status: active
     108$ fedd_multistatus.py
     109faber-multi:b4339d8a339097e87ed5624a36b584fe95b0ea0d:active
    111110}}}
    112111
    113 Experiments can also be "failed" which means it will not come up, and a couple other states.
     112Experiments can also be "failed" which means it will not come up, and a couple other self-explanatory states.
    114113
    115114Because 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:
     
    14013921 Sep 11 14:05:10 fedd.experiment_control.faber-multi Waiting for sub threads (it has been 8 mins)
    141140}}}
     141
     142Once 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.
     143
     144The fedd logs are also world-readable on users.isi.deterlab.net.  To watch a multi-party swap-in, the following logs may be interesting:
     145
     146{{{
     147/var/log/fedd.log                           # the main experiment controller log
     148/var/log/fedd.deter.log                     # the log for the DETER testbed access controller (the component swapping experiments)
     149/var/log/fedd.internal.log                  # the log for the access controller handing out VLANs to interconnect on DETER
     150}}}
     151
     152The easiest way to view them is:
     153{{{
     154$ tail -f /var/log/fedd.log
     155}}}
     156
     157== Experiment Status ==
     158
     159Once 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.
     160
     161{{{
     162$ fedd_ftopo.py --experiment_name faber-multi
     163d:pc027.isi.deterlab.net:deter/b
     164e:pc020.isi.deterlab.net:deter/b
     165a:pc009.isi.deterlab.net:deter/a
     166b:pc044.isi.deterlab.net:deter/a
     167c:pc022.isi.deterlab.net:deter/b
     168}}}
     169
     170You can manipulate the various parts by logging into the machines or using SEER.