a bootstatus field to the nodes table. os_setup sets this to one of
okay, failed, unknown. This is to be used with the still to be defined
method of specifying certain nodes that can fail reboot on experiment
creation. Right now sharks are wired to this, and this information is
presented in the web page. Its also essential for the batch system,
which needs to consider nodes that failed to reboot, or else batch
experiments would never end. Might still need a way for an experiment
to tell the batch system its done though.

commit.

sharks and delay nodes.

per-experiment level DB redirect. This makes it easier to tolerate
testing harness failures.

its hardwired to the shark type, but needs to come from DB somehow
later. Mail is sent to the user (CC'ed to testbed-ops) when a node
fails but the experiment continues setup.

easily allows tests to be shared across sets.

sessions. (advanced use only)

Made test failure messages more meaningful.

customization for the log paths. Also added an increase of max
connections to 200.

Minor cleanups in os_setup, and move some code to libdb.

a development tree.

node_reboot fail oddly cause the kill -TERM was killing the shell
process but not the ssh!

directly-connected nodes, rather than guessing from IP subnet

NOTE: -p not yet implemented ifdef UDPTEST

intead of NULL.

listed publicly by emulab, as per Jay request.

Add some addslashes calls.
Call mkacct-ctrl for updating user info and password.

who is active.

who is active.

Usage: dhcpd_makeconf [-h] [-v] <templatefile>
templatefile should be a skeleton dhcp.conf file, without entires for each node.
The string '%%nodetype=<type>' will be expanded to entries for all nodes of type
<type> in the following form:
host $ip {
	hardware ethernet $mac;
	option host-name '$node_id';
	fixed_address $ip;
}

The generated dhcp conf file is printed on stdout.

The -v option causes dhcpd_makeconf to use virtual names, rather than
physical ones, for hostnames.

appropriate.

and vname updating in assign_wrapper.

days and days.  New one implies quick! (help me watch the list
and check people out, Leigh and Mac.)

mkacct and rmacct.

all the nodes in an experiment.

Rob and I noticed that when we need to do maintainance to a node, its hard
to grab it when it gets freed before it gets taken again. So this will allow
admins to set up nodes so that when the current owner frees them, they
immediately are moved into another experiment. For instance, if I need to do
an upgrade on all the machines in the testbed, I can do:

sched_reserve testbed down pc1 pc2 pc3 [...] pc40

and it will immediately reserve any free nodes, skip any that are already
in testbed/down, and add an entry to the next_reserve table for any nodes
that are already reserved. Then nfree checks for entries in the next_reserve
table before it lets any nodes go (much like it does for the reloads table),
and moves them into the expt before it can get reserved again. So we can
guarantee that the next time a node is freed, it will be saved for us.

Note that this can also be useful to accumulate nodes for a large experiment,
since you can make sure you get them as soon as the current owner is done.

Added info about capture.rc, thanks to Rob. I'm not sure if the stuff about proxyDHCP is up to date, since someone might have made that come from the database instead.

for this test to fail.  More a test of the testing infrastructure than
anything else.