GitLab

Reorg last tmcd checkin a bit and fix a potential problem.

interface  on a node in an Emulab experiment. Assumes the name of
the 'Internet' LAN is 'planetc'.

to check in earlier.

Changes to support reporting back the port elvind bound to in the
management slice, and also sending this back to non-MS slivers.

delay osid so that they don't get a delay node that can't load their
OS.

Note, I can't do this when the user does not ask for a specific delay
OSID, since then the OSID is dependant on the node type.

vnodes.

1) When aborting run cause of timeout, do not throw away results
   generated so far.

2) Indicate in the email that the run timed out.

A few other minor cleanups too.

never unmap the link, so make sure we don't try to map it a second
time.

Ripping out crope and replacing (almost) all cropes, char*s and
strings with fstring

Beginnings of XML parser support (not built by default yet).

Significant re-org of code.

Should now compile with the latest gcc.

Putting link information in stored solutions.

Support for fixing interfaces.

change stub-monitor.c to work with the new stubd
fixed one typo in stub-pcap.c

make changes. Also set the umask to 0002 for the loghole run.

is putting it (into the archive).

How we get this value to the nodes in general is still a question,
but we use this currently to pass to per-experiment firewalls so that
they can be use it in rules.

application directly.

Add a new script, instrument.sh, that runs your app with libnetmon,
which will connect to netmond, and thus to the monitor.

Change both to allow them to be run from arbitrary directories - you
no longer have to cd into the monitor directory to run them.

   both directions at the same time again. I had put in a delay, attempting
   to see if that might help the packet loss problems; I do not think it
   does. So, loss tests will complete faster.

2) Changed the duration for the bw tests as we discussed. I did a quickie
   trial, and ended up with:

	    x > 33Mbs	3 seconds
    33Mbs > x > 10Mbs	5 seconds
    10Mbs > x > 64Kbs   7 seconds

   Then add 3 seconds if the loss if over 10%

   The above numbers are very conservative; we can probably do better, but
   it would take a longer set of trials (across a variety bw/delay
   products). Remember, all bw tests ran for 10 seconds (in each direction).

3) Add in the ethernet/ip/udp overhead to the bw results; Much nicer. I
   reduced the allowed error factor fom 6% to 2%, although its actually
   within less then 1% most of the time.

4) Allow BW checks when there is loss on the link; previously linktest
   skipped any link with loss on it. Since we UDP for the tests, we
   can fairly well estimate what the BW will be. This is not perfect
   yet, especially with low BW, high loss links. We need to run some
   trials to see where accuracy falls off too far, or how to
   compensate for it.

5) Added some more time stamps.

Parse the NS file with the real NS parser so we can make sure linktest is
doing the "right" thing.

	* configure, configure.in: Add tbsetup/nsverify files.

	* tbsetup/GNUmakefile.in: Add nsverify subdir.

	* tbsetup/tbprerun.in: Run verify-ns on the experiments NS file.

	* tbsetup/ns2ir/nstb_compat.tcl: Bring up-to-date with the current
	world.

	* tbsetup/nsverify/GNUmakefile.in: Makefile.

	* tbsetup/nsverify/ns-2.27.patch: Patch file for NS version 2.27.

	* tbsetup/nsverify/nstbparse.in: Wrapper for the NS parser.

	* tbsetup/nsverify/tb_compat.tcl: Different version of
	tb_compat.tcl that is used to verify linktest parameters.

	* tbsetup/nsverify/verify-ns.in: Script that runs on boss and
	verifies that the testbed parser worked correctly.

	* tbsetup/ns2ir/parse-ns.in, tbsetup/ns2ir/parse.proxy.in: Tweaked
	a bit so parse.proxy can be used to run the regular NS parser in
	addition to the testbed one.