1. 06 Dec, 2006 1 commit
  2. 01 Dec, 2006 1 commit
  3. 09 Nov, 2006 1 commit
  4. 08 Oct, 2006 1 commit
  5. 29 Sep, 2006 1 commit
  6. 15 Sep, 2006 1 commit
    • Mike Hibler's avatar
      Mostly cleanup. · cde74d7a
      Mike Hibler authored
      * generate the initial conditions for monitors to pass into the stubs
        (must use -i to start-experiment to do this)
      * make sure install-tarball does not return til tarballs are installed!
        (or til timeout)
      * move ip mapping and initial conditions files to /local/logs so they
        become part of the record
      * fix up exit status' returned by auto-* stubs so program-agent
        can detect real failures
  7. 21 Aug, 2006 1 commit
    • Mike Hibler's avatar
      Tweaks to make auto-* work correctly with BSD /bin/sh · 9b8d05a3
      Mike Hibler authored
      Change dbmonitor to, by default, use the latest of A->B and B->A
      values when setting characteristics on site A.  Do this for both latency
      and bandwidth values, though should probably allow BW values to continue
      to be asymmetric.
  8. 16 Aug, 2006 1 commit
  9. 12 Aug, 2006 1 commit
  10. 11 Aug, 2006 1 commit
  11. 10 Aug, 2006 1 commit
    • Mike Hibler's avatar
      First crack at surviving down planetlab nodes. If the master barrier sync · 5f413b47
      Mike Hibler authored
      node sits in the stub or monitor barrier sync for more than the SYNCTIMO
      timeout value in common-env.sh, it will send a HUP to syncd which will
      knock all the other nodes out of their barrier sync.  If that happens,
      all nodes will print a warning message and continue.
      All nodes wait for both a stub sync and a monitor sync, so if one plab node
      is down, they will timeout on both barrier syncs.  Race conditions?  Sure.
      If for example everyone times out on the stub barrier due to a slow node,
      and then that node reaches the barrier, it will hang there while everyone
      else waits on the monitor barrier.  When the latter times out, it will
      kick the slow node out of the stub sync and it will then proceed to hang
      in the monitor sync until the experiment is stopped.  Got that?
      As an aside, it would be nice if the initializer of a barrier could specify
      a timeout value, and return a special error code to everyone if it timed out,
      but that would require an incompatible change to the sync protocol.
  12. 09 Aug, 2006 1 commit
  13. 14 Apr, 2006 2 commits
  14. 10 Apr, 2006 1 commit
  15. 05 Apr, 2006 1 commit
  16. 17 Mar, 2006 1 commit
    • Robert Ricci's avatar
      More work on the framework for running the monitor and stub · c8bbc432
      Robert Ricci authored
      Now automatically determines the number of peers in the experiment.
      run-monitor-libnetmon.sh automatically generates the IP mapping file
      Auto-create /local/logs if it doesn't exist (it doesn't on our
      devbox image)
      Add two new 'auto' scripts - these are intended to be run as part
      of the automatic experiments. They properly wait for the stubs
      to start before starting the monitors, etc. They log the outputs
      of the stub and monitor to /local/logs, where loghole can pick
      them up. They also kill their children if they are killed (to be
      used with the program agent)
      The auto-* scripts need a little more work in term of properly waiting
      for their children to exit.
  17. 23 Feb, 2006 1 commit
  18. 16 Feb, 2006 1 commit
  19. 03 Feb, 2006 3 commits