into flyspray DB and send out email to everyone on the notifications
list. This is all done in perl, not php of course.

trying to start two runs at a times. Nothing special, only one
operation at a time.

Yes, I grepped for it everywhere this time!

(initial) parameters for a new run. Three choices right now; from the
template itself, from the instance, or from the previous run. On the
web interface this is presented as three buttons. On ops, it is the
the -y option, which takes one of template,instance,lastrun as its
argument (you can of course combine the -y option with an XML file to
override specific params).

At present, there is no default. Lets give it a chance to sink in
before I pick something that will annoy 50% of the people 75% of the
time.

Change the way vnode_setup handles plab nodes a bit to avoid a couple of
buggy situations.

  * Don't try vnodesetup -h on plab nodes

This can hang, or even fail.  Since nothing useful is conveyed by this
step, just skip it, set the node's state to SHUTDOWN, and ask pl_conf
on the node to remove the vserver.

  * Set plab node's alloc state to TBDB_ALLOCSTATE_RES_INIT_DIRTY after
    instantiation.

This avoids a bug where Emulab cluster nodes fail to come up, and so
os_setup never waits on the plab vnodes (now that they are started in
parallel with physical node setup).  Previously their alloc state made
them look clean, and so the vservers would not be reaped during
teardown.

we will never be called if not.

README also provided. Logs generated by Kirk have also been checked in. The
script has been tested for all the log types.

README also provided. Logs generated by Kirk have also been checked in.

README also provided.

Fix up argument processing.

graph. These were the latest Emulab numbers provided by Kirk.

middleman_values.txt contains the numbers of Planetlab.
synulab_values.txt contains the numbers of Emulab

blocksize for the synth app.

These are picked up by the monitor via the environment.

The values for these can be extracted from the environment so they can
be changed between Template runs.

Fixed a bug in how bufferFull was calculated (it was erroneously true most of the time). Changed LeastSquares to require both a buffer full and increasing delays to consider a measurement authoritative.

time a run starts. This info is stored in the DB forever, but a file
in the archive is a nice thing too.

apps/protocols that use X cpu on PlanetLab can also add network artifacts.

sfmiddleman sits in the middle as a compute-intensive proxy.  sfsender
sends the middleman n "messages" each composed of m "blocks", and can
pause for t1 and t2 times at microsecond granularity after each block send
and msg send.  sfmiddleman reads blocks and does operations on them
(default is decrypt/encrypt, can also do only encrypt), then forwards them
to all connected receivers.  You guessed it, sfreceiver connects to
sfmiddleman and reads blocks and prints timestamps.  For each op on a
block, sfmiddleman notes the number of microseconds taken by the crypto
ops, and the timestamp when it/they finished, and prints those.

There is one known bug.  I'll fix it in the morning.  If there are others,
I'll get them then too.

template world:
	set no_plab to 1
	set use_dbmonitor to 1
	put enough nodes in the plabnodes list
	use start-run and stop-run to do it

An unexpected exit code will cause the __all_programs HALT event to
fail and cause "Stop Run" to fail.