automatically.

Now automatically determines the number of peers in the experiment.

run-monitor-libnetmon.sh automatically generates the IP mapping file
now.

Auto-create /local/logs if it doesn't exist (it doesn't on our
devbox image)

Add two new 'auto' scripts - these are intended to be run as part
of the automatic experiments. They properly wait for the stubs
to start before starting the monitors, etc. They log the outputs
of the stub and monitor to /local/logs, where loghole can pick
them up. They also kill their children if they are killed (to be
used with the program agent)

The auto-* scripts need a little more work in term of properly waiting
for their children to exit.

security-level.

tag snmpit error messages as being hardware errors.

Don't export the snmpitFatal and snmpitWarn functions - these are
really supposed to be internal, and I've tweaked their meaning a
bit. Nothing else calls them.

were any WARNings (which usually mean failure) during the run.

to commit it.

Pass experiment description through to Planetlab as the slice description
when creating a slice.  Also mention the Planetlab AUP and importance of
providing an accurate slice description in the documentation.  The ez
interface also briefly mentions the importance of the slice description.

Database to make it usable for emulab.

Remove the driver install and cache clearing options, make an interface map for use during Mini-Setup.

hour from crontab.

timeline to __ns_teardown so the evproxies unsubscribe from the
experiment.

the image-test directory

the whole project.

Added standalone support for multiple streams. Added a logging infrastructure. Added a trivial application for testing purposes (dumb-client and dumb-server). Added the capability for running the standalone stub with a tcpdump replay. Added support for changing buffer sizes. Added shell files for experiment management, reset.sh which is to reset the dummynet settings between runs and run-iperf.sh which encapsulates a set of options to iperf.

and libraries.

which are stored in /proj/$pid/images since they cannot go directly
to boss. They need to be copied back of course, but only admins
can create global images anyway.

Use a file to manage the list of ignored/allowed nodes instead of hard coding
them into the source.  The files are:

@prefix@/etc/plab/{IGNOREDNODES|ALLOWEDNODES}

Added inline POD documentation of libtblog.

TODO: Automatically generate HTML page from and and have it installed
with the other HTML docs.

being taken.

The basic strategy is to have node_reboot (when -p option supplied)
invoke a special command on the node that will cause the shutdown
procedure to run prepare as it goes single user, but before the
network is turned off and the machine rebooted. The output of the
prepare run is capture and send back via the tmcd BOOTLOG command and
stored in the DB, so that create_image can dump that to the logfile
(so that the person taking the image can know for certain that the
prepare ran and finished okay).

On linux this is pretty easy to arrange since reboot is actually
shutdown and shutdown runs the K scripts in /etc/rc.d/rc6.d, and at
the end the node is basically single user mode. I just added a new
script to run prepare and send back the output.

On FreeBSD this is a lot harder since there are no decent hooks.
Instead, I had to hack up init (see tmcd/freebsd/init/{4,5,6}) with
some simple code that looks for a command to run instead of going to a
single user shell. The command (script) runs prepare, sends the output
back to tmcd, and then does a real reboot.

Okay, so how to get -p passed to node_reboot? I hacked up the
libadminmfs code slightly to do that, with new 'prepare' argument
option. This may not be the best approach; might have to do this as a
real state transition if problems develop. I will wait and see.

Also, I changed www/loadimage.php3 to spew the output of the
create_image to the browser.

being taken.

The basic strategy is to have node_reboot (when -p option supplied)
invoke a special command on the node that will cause the shutdown
procedure to run prepare as it goes single user, but before the
network is turned off and the machine rebooted. The output of the
prepare run is capture and send back via the tmcd BOOTLOG command and
stored in the DB, so that create_image can dump that to the logfile
(so that the person taking the image can know for certain that the
prepare ran and finished okay).

On linux this is pretty easy to arrange since reboot is actually
shutdown and shutdown runs the K scripts in /etc/rc.d/rc6.d, and at
the end the node is basically single user mode. I just added a new
script to run prepare and send back the output.

On FreeBSD this is a lot harder since there are no decent hooks.
Instead, I had to hack up init (see tmcd/freebsd/init/{4,5,6}) with
some simple code that looks for a command to run instead of going to a
single user shell. The command (script) runs prepare, sends the output
back to tmcd, and then does a real reboot.

Okay, so how to get -p passed to node_reboot? I hacked up the
libadminmfs code slightly to do that, with new 'prepare' argument
option. This may not be the best approach; might have to do this as a
real state transition if problems develop. I will wait and see.

Also, I changed www/loadimage.php3 to spew the output of the
create_image to the browser.

 * admin MFS is larger and had more problems with simultaneous reboots

 * power command did not support batching anyway (only node_reboot), so
   power ons were performed enmasse, exacerbating problems

sincd adding Cluster Expansion Phase II pics.

a bit more, then hack it into the testbed.