1. 07 Jul, 2002 1 commit
  2. 25 Jun, 2002 1 commit
  3. 13 Jun, 2002 1 commit
  4. 22 May, 2002 1 commit
    • Leigh B. Stoller's avatar
      Two performance additions. 1) Use the -e option to mysqldump to turn · c2602c3e
      Leigh B. Stoller authored
      of "fast insert" mode. That option plus a couple of others makes
      duplicating the DB 3-4x faster.
      Add a DB table of tables to prune out of the copy before creating the
      clean DB. There is a lot of stuff in the DB that is not needed for the
      testsuite, and the constant copies churn the DB for little reason.
  5. 16 May, 2002 1 commit
  6. 15 May, 2002 1 commit
  7. 15 Apr, 2002 1 commit
    • Leigh B. Stoller's avatar
      Add static routing support: · d881770b
      Leigh B. Stoller authored
      	# Turn on manual routing.
      	$ns rtproto Manual
      	# Set manual routes
      	$nodeA add-route $nodeC $nodeB
      	$nodeC add-route $nodeA $nodeB
      results in this information being returned from the tmcd routing
      		NEXTHOP= COST=0
      The reason for DESTTYPE and DESTMASK is so that we can also support
      routing to links and lans, since doing it on a per host basis if not
      only hugely tedious, but plain impossible if the destination node has
      multiple links; the add-route syntax takes a node, but we need the IP
      of the relevant link in order to run the route add commands on the
      nodes. So, I've "extended" the syntax of add-route so that you can
      give it a Link or a Lan as the dest:
      	$nodeA add-route $link0 $nodeB
      	$nodeA add-route [$ns link $nodeB $nodeC] $nodeB
      In this case, the DESTTYPE=net, and the netmask is no longer ignored;
      it is used in the route add command. Currently, the mask is hardwired
      in the DB to, but by providing it in the tmcd command,
      we change it later if needed.
      I did not implement add-route-to-adj-node since that is not really
      useful in our context, and we definitely do not want the user to
      change the default routes on his nodes. But, its easy to add if we
      need to.
      The client side stuff is not done yet.
  8. 14 Apr, 2002 2 commits
  9. 04 Apr, 2002 1 commit
  10. 25 Mar, 2002 1 commit
  11. 22 Mar, 2002 1 commit
  12. 18 Mar, 2002 1 commit
  13. 11 Mar, 2002 2 commits
    • Leigh B. Stoller's avatar
      Initial version of RED/GRED support. Chris is going to have to finish · f35ce7e3
      Leigh B. Stoller authored
      this off, but here is what I did.
      Parser: Allow for the following syntax
      	set link0  [$ns duplex-link $nodeA $nodeB 100Mb 0ms RED]
      	set queue0 [[$ns link $nodeA $nodeB] queue]
      	$queue0 set gentle_ 1
      	$queue0 set queue-in-bytes_ 0
      	$queue0 set limit_ 50
      	$queue0 set maxthresh_ 20
      	$queue0 set thresh_ 7
      	$queue0 set linterm_ 11
      	$queue0 set q_weight_ 0.004
          NB: This differs from the NS syntax (and is the part that Chris
          needs to fix) in that there is just a single queue object per
          duplex link, thus the parameters cannot be set asymmetrically.
          Note, the delay node *does* use a RED/GRED queue in each
          direction, but its params are the same. These TCL hacks took a
          long time for me to get right!
          Also note that I have no idea how this stuff relates to LANS! I
          do not allow LANS to be created with RED queues (another item for
          Chris to work on perhaps?).
      assign_wrapper: A horrible hack to pass the new fields added to
      virt_lans onto the delays table setup. Also another minor hack ensure
      that a delay node is added when a RED queue is used (for the case when
      no other traffic shaping is done). At the moment, the virt_lans table
      has a single set of fields, while the delays table has the double set;
      one for each direction of the pipe. Here is a listing.
          alter table delays add q0_limit int default 0 after lossrate0;
          alter table delays add q0_maxthresh int default 0 after q0_limit;
          alter table delays add q0_minthresh int default 0 after q0_maxthresh;
          alter table delays add q0_weight float default 0.0 after q0_minthresh;
          alter table delays add q0_linterm int default 0 after q0_weight;
          alter table delays add q0_qinbytes tinyint default 0 after q0_linterm;
          alter table delays add q0_bytes tinyint default 0 after q0_qinbytes;
          alter table delays add q0_meanpsize int default 0 after q0_bytes;
          alter table delays add q0_wait int default 0 after q0_meanpsize;
          alter table delays add q0_setbit int default 0 after q0_wait;
          alter table delays add q0_droptail int default 0 after q0_setbit;
          alter table delays add q0_red tinyint default 0 after q0_droptail;
          alter table delays add q0_gentle tinyint default 0 after q0_red;
      tmcd/tmcd.c: Change dodelays to pass back all of these fields (for
      both pipes; there are equiv q1 fields in the delays table). Yikes! Its
      done in a backwards compatable manner though, so existing delay nodes
      will continue to work just fine.
      tmcd/freebsd/liblocsetup.pm: Change the delays configuration script to
      get all these fields and do something useful with. Of course, our
      delay nodes cannot use a lot of these fields, but the information is
      sent through for the eventuality that we have more sophisticated
      delays nodes.
      Test Suite: Add red test dir that has the above syntax as its test.
    • Leigh B. Stoller's avatar
      Add --disable-events for testsuite since the lack of TG source breaks · 0e6d5c06
      Leigh B. Stoller authored
      it. Worry about it later.
  14. 25 Feb, 2002 1 commit
  15. 25 Jan, 2002 1 commit
  16. 22 Jan, 2002 1 commit
    • Robert Ricci's avatar
      More work on getting the testsute to run on the mini-testbed. Many · 2edf2943
      Robert Ricci authored
      tests still didn't work on the mini-testbed. The less important tests
      have been removed - a few others just modified to work with fewer
      The tbcmd test is an important one, which would lose something by being
      smaller. So, I've made a copy of it which tests a slightly smaller set
      of functionality, but will run on the mini-testbed.
  17. 17 Jan, 2002 1 commit
  18. 16 Jan, 2002 1 commit
  19. 11 Jan, 2002 2 commits
  20. 08 Jan, 2002 3 commits
  21. 03 Jan, 2002 5 commits
  22. 30 Nov, 2001 1 commit
  23. 18 Oct, 2001 1 commit
    • Mac Newbold's avatar
      Add 'update users set admin=1 where uid='flest';' to the dumped db so that... · 0e0653a8
      Mac Newbold authored
      Add 'update users set admin=1 where uid='flest';' to the dumped db so that flest is set as admin for its runs. Gives it magical powers to clear out all the expts. We may want to someday change this to be UID instead of 'flest', so that whoever is running it becomes admin. But for now, I think everyone who runs the test suite already is an admin.
  24. 19 Sep, 2001 2 commits
  25. 28 Aug, 2001 1 commit
    • Leigh B. Stoller's avatar
      Cleanup of the Chris' TB scripts. Cosmetic in principle, but reworked · c874636d
      Leigh B. Stoller authored
      to use the DB library access routines, which also changed in response
      to what the tb scripts needed. Added some functions and mor constants.
      Removed the -nologfile option from all the scripts (startexp and
      endexp too), since there is no reason for these scripts to worry about
      log files. Thats handled in the wrappers. Tested with the testsuite
      and live in my own tree.
  26. 26 Aug, 2001 1 commit
  27. 09 Aug, 2001 1 commit
  28. 31 Jul, 2001 1 commit
  29. 24 Jul, 2001 1 commit
    • Christopher Alfeld's avatar
      This commit contains two signifcant changes: · 210aa1ec
      Christopher Alfeld authored
      1. 'tb-set-hardware ... shark' and 'tb-set-hardware ... dnard' are now
      functionally identical.  Previously only the former worked but both passed
      the parser.
      2. Assign will now exit very quickly in the case that, for a given virtual
      nodes, there are no physical nodes that could match in type.  This should
      never happen as the parser and assign_wrapper have checks that usually
      prevent this.  However, in the case of problems in the code (such as #1)
      this'll make it easier to debug.  In addition, as we add more types of
      nodes and our estimates becoming increasingly inaccurate cases where this
      might occur could slip in.  All calling code treats this identically to an
      'insufficient resources' failure.
  30. 20 Jul, 2001 1 commit