1. 10 Aug, 2006 7 commits
    • Jonathon Duerig's avatar
    • Robert Ricci's avatar
      Add the timestamp at which the connect() occurs for Jon. Uses a new, · 10fa9140
      Robert Ricci authored
      function, fprintTime() which will be used to standardize the time
      format.
      
      Also added const to some declarations to keep the compiler happy.
      10fa9140
    • Robert Ricci's avatar
      Use the C99 standard · c4e21e5a
      Robert Ricci authored
      c4e21e5a
    • Leigh B. Stoller's avatar
      Okay, now we can view graphs from the historical data (template record). · 0c1b1a23
      Leigh B. Stoller authored
      A couple of things to note:
      
      * When requesting a graph, we have to have a checkout of the archive
        (the DB dump file) so that we can create a temporary DB with the data.
        This is done on demand, and the DB is left in place since its a
        fairly time consuming operation to do the checkout and the dbload.
        I do not delete the DBs though; we will need to age them out as needed.
      
      * Even so, when returning to a page we end up getting the graphs
        again, and that still takes more time then I like to wait. Perhaps
        add a refresh button so that the user has to force a redraw. Might
        need to add a time/date stamp to the graph.
      0c1b1a23
    • 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.
      5f413b47
    • Mike Hibler's avatar
      Minor tweaks: · 4c5005da
      Mike Hibler authored
      * add getopt processing
      * adjust delay to be one way before calling tevc
      4c5005da
    • Leigh B. Stoller's avatar
      Next checkpoint of graphing code. On a currently active template · 79ae0bfe
      Leigh B. Stoller authored
      instance there are graphs on the instance show page and on the
      individual run show pages. On the run pages, the graphs select just
      the packets between start and stop of the run. I also added drop down
      menus to select particular source and destination vnodes.
      79ae0bfe
  2. 09 Aug, 2006 15 commits
  3. 08 Aug, 2006 8 commits
  4. 07 Aug, 2006 3 commits
  5. 04 Aug, 2006 2 commits
    • Kirk Webb's avatar
      · 19616c33
      Kirk Webb authored
      bah, fix to the fix.
      19616c33
    • Kirk Webb's avatar
      · 4b477246
      Kirk Webb authored
      A few little things:
      
      * Minor bugfix to node_type_attributes mod.
      * When we don't recognize the gateway, set type to "*Unknown*".  Should
        have always been doing this.
      * Add NLR gateway - new nodes detected here will be set to pcplabinet2,
        but this could easily be changed.
      4b477246
  6. 03 Aug, 2006 5 commits