1. 03 Aug, 2006 5 commits
    • Kirk Webb's avatar
      · 38c27731
      Kirk Webb authored
      Switch to using GNU tar ('gtar').  This must have been the default tar for
      FBSD 4.X since options are missing from the tar in FBSD 6.X
      38c27731
    • Dan Gebhardt's avatar
      initial checkin · 8cf4bd58
      Dan Gebhardt authored
      8cf4bd58
    • Dan Gebhardt's avatar
      initial checkin. · 3edf8fe1
      Dan Gebhardt authored
      3edf8fe1
    • Russ Fish's avatar
      fb3d6f46
    • Leigh B. Stoller's avatar
      Support for capturing the trace data that is stored in the pcal files · 4ce9c421
      Leigh B. Stoller authored
      into per-experiment databases on ops. Additional support for reconsituting
      those databases back into temporary databases on ops, for post processing.
      
      * This revision relies on the "snort" port (/usr/ports/security/snort)
        to read the pcap files and load them into a database. The schema is
        probably not ideal, but its better then nothing. See the file
        ops:/usr/local/share/examples/snort/create_mysql for the schema.
      
      * For simplicity, I have hooked into loghole, which already had all
        the code for downloading the trace data. I added some new methods to
        the XMLRPC server for loghole to use, to get the users DB password
        and the name of the per-experiment database. There is a new slot in
        the traces table that indicates that the trace should be snorted to
        its DB. In case you forgot, at the end of a run or when the instance
        is swapped out, loghole is run to download the trace data.
      
      * For reconsituting, there are lots of additions to opsdb_control and
        opsdb_control.proxy to create "temporary" databases and load them
        from a dump file that is stored in the archive. I've added a button
        to the Template Record page, inappropriately called "Analyze" since
        right now all it does is reconsitute the trace data into a DB on
        ops.
      
        Currently, the only indication of what has been done (the name of
        the DBs created on ops) is the log email that the user gets. A
        future project is tell the user this info in the web interface.
      
      * To turn on database capturing of trace data, do this in your NS
        file:
      
      	set link0 ...
      	$link0 trace
      	$link0 trace_snaplen 128
      	$link0 trace_db 1
      
         the increase in snaplen is optional, but a good idea if you want
         snort to undertand more then just ip headers.
      
      * Also some changes to the parser to allow plain experiments to take
        advantage of all this stuff. To simple get yourself a per-experiment
        DB, put this in your NS file:
      
      	tb-set-dpdb 1
      
        however, anytime you turn trace_db on for a link or lan, you
        automatically get a per-experiment DB.
      
      * To capture the trace data to the DB, you can run loghole by hand:
      
      	loghole sync -s
      
        the -s option turns on the "post-process" phase of loghole.
      4ce9c421
  2. 02 Aug, 2006 2 commits
  3. 01 Aug, 2006 3 commits
  4. 31 Jul, 2006 1 commit
  5. 28 Jul, 2006 5 commits
  6. 27 Jul, 2006 4 commits
  7. 26 Jul, 2006 6 commits
    • Russ Fish's avatar
    • Kevin Atkinson's avatar
      · 9237c34b
      Kevin Atkinson authored
      Fix syntax error.
      9237c34b
    • Kevin Atkinson's avatar
      · cbf3c5d4
      Kevin Atkinson authored
      swapexp: The previous commit, witch added a message about the recovery
      action when a swap-modify failed to the top of the email, did not
      catch all of the possible cases.  Added the case when the experiment is
      not swapped in.
      
      os_setup: Refactored/rewrote os_setup error summary code.  Distinguish
      the case when nodes fail to properly load the os and when the don't
      boot after loading the os.
      cbf3c5d4
    • Kevin Atkinson's avatar
      · 23a61519
      Kevin Atkinson authored
      Fix bug in libosload when there is an image problem.  The code that checks
      if there is an image problem is part of the code that looks up information
      on the image.  The problem is that this info is catched so that the next
      time this info is looked up the checks are not performed.  Thus, libosload
      will attempt to load the image even though there is a problem with the
      image.  This will often lead to obscure error messages.  Fixed by using a
      special value for when there is a problem with the image.
      
      Fix bug when an experiment has more than 1 image type to load.  Only the
      results from one of the image loads will be properly recognized. The
      others will be ignored.  This is because the the same file handle is being
      used for all the children due to the use of a global file handle glob.
      Fixed by changing the glob to a variable and using "new IO::Handle" to
      create a new handle for each child.
      23a61519
    • Leigh B. Stoller's avatar
      c9415631
    • Leigh B. Stoller's avatar
      b9feabf0
  8. 25 Jul, 2006 8 commits
  9. 22 Jul, 2006 3 commits
  10. 21 Jul, 2006 3 commits