1. 14 Feb, 2008 2 commits
  2. 13 Feb, 2008 4 commits
  3. 12 Feb, 2008 4 commits
  4. 11 Feb, 2008 5 commits
  5. 09 Feb, 2008 2 commits
    • Leigh Stoller's avatar
      Bump pnode/vnode duration counters to floats since several users · 1d57505c
      Leigh Stoller authored
      (Rob,Mike,Jay) have overflowed an unsigned int.
      1d57505c
    • Dan Gebhardt's avatar
      Some very basic infrastructure for generalized tools was added. · 639758e6
      Dan Gebhardt authored
      Some parts very "hacky", lots of XXX / TODOs.
      BARELY tested!!!! Don't use on the production system yet.
      Need to verify that things didn't break, especially with the automanager,
      the bgmon.pl "outage detection stuff", etc...
      
      See code's todos and also the file
      flexlab-canonicalization-misc-notes.txe
      
      At this point:
       - mangerclient & automanagerclient did not change.
       - The manager, when a probe request is received, looks at the DB table
         "tool_spec" to retrieve the proper wrapperpath, formal parameter list, etc..
       - The manager assembles a message and sends it out to the appropriate
         path probers, which operate on the request as they have been
         (no major internal changes to the path probers).
       - The path probers call the toolwrapper to run the tests
       - The toolwrappers return a canonical result for that type of metric.
       - The path probers send the result and the actual parameters used by the
         tool to the data collector.
       - The data collector uses the toolname and actual parameters to get an
         idx number. This idx is stored in the "measured_by" field of this
         measurement's entry in the "pair_data" table.
      639758e6
  6. 07 Feb, 2008 2 commits
  7. 06 Feb, 2008 9 commits
  8. 05 Feb, 2008 2 commits
  9. 04 Feb, 2008 9 commits
  10. 02 Feb, 2008 1 commit
    • Dan Gebhardt's avatar
      Checking in Mike's changes: · 322dbb59
      Dan Gebhardt authored
      - latency measurements under 2 second intervals now operate in "continuous"
        mode: a single "ping" process runs per destination, versus the "normal"
        approach of forking a new fping process for each measurement instance.
      
      - Note, that I found a bug which is not fixed in this checkin: if a latency
        test is running in continuous mode and another latency measurement request
        is received with a shorter interval, the "continuous" ping process is not
        re-initialized with the new, shorter interval.
      322dbb59