classnames).

a socket on a remote node instead of a local tty device. When using
remotemode, the last argument to capture should be host:port instead
of tty.

power cycle. For those we need to send wakeonlan packets to kick them.
This is complicated by the fact that the laptops take an incredibly
long time to go from poweron to a point where it will listen to a
wakeonlan packet. No idea why. I use StateWait() to find out when the
node hits bootinfo (which sends a PXEBOOTING event). Keep looping
sending more wakeonlan packets until we hear from the node. Time out
the operation after two minutes (probably need something to control
this).

To find the outgoing interface required by tools/whol program, I look
in the interfces table for boss' control network.

The mac address of the target node comes from the interfaces table.

The flag that controls whether a node needs wakeonlan is in the
node_attributes table:

	mysql> insert into node_attributes set
	          attrkey='wakeonlan_afterpower',
		  attrvalue=1, node_id='pcxxx';

creation.  Only runs on the CMU emulab.

from an experiment such as hwdown.

without waiting for nodes to sync with PLC.

easier.

Also add a daily_stats table that will record, you guessed it, the
daily stats, which will be a mucg faster wayt to see what is going on
and even generate some graphs.

way forward for my life.

the new form stuff, but that would have taken way too long.

I think this fixes flyspray bug #51.

this since the newnode ssh reboot fails now that we default to
protocol 2. Good to do anyway.

doc/UPDATING has the instructions for updating the newnode MFS. There
is no need to update the other MFSs since they get the current root
key from tmcd each time they boot.

useful on widearea nodes where we can amortize the time it takes to
copy/hash the necessary filesystems, which takes about 15 minutes.
We would do this when a node first boots (or its image is updated I
guess).

Note that the clone operation (when a vserver is actually created) is very fast
though, taking about 30 seconds.

Currently controlled by local variable $USEHASHIFIED for debugging.

switches.

Add basic test of the event system and program agents.

Fedora 8.

NS file is wrong. Well, worse then that, the query was wrong and it
was setting all the resource records for that experiment to the new NS
file. Highly annoying, probably no way to recover the lost record of
NS files.

It doesn't look promising that I will be back to it this week, sigh...

  endexp <pid>/<eid>
rather than
  endexp <pid> <eid>
which is no longer supported

tables.

Remove the tunnels table since that stuff is now in the
lan_member_attributes table.

Add node_id to the lan_members table. While its nice having that as an
attribute, it makes joins more difficult and slower.

nightly, and make repairs for the common things I see happening.  The
current version repairs most of the errors that have crept in since
the Epoch, and then rebuilds the summary stats table (user_stats,
group_stats, project_stats). My intent is to add a "daily_stats" table
as well since scanning the testbed_stats and experiment_resources
table to generate range data is getting pretty slow as more records
enter the system. We can also use a daily_stats table to generate
graphs on the fly as Jay requested a few weeks ago.

Not done yet, hope to return to it later this week.

script.

(Rob,Mike,Jay) have overflowed an unsigned int.

Some parts very "hacky", lots of XXX / TODOs.
BARELY tested!!!! Don't use on the production system yet.
Need to verify that things didn't break, especially with the automanager,
the bgmon.pl "outage detection stuff", etc...

See code's todos and also the file
flexlab-canonicalization-misc-notes.txe

At this point:
 - mangerclient & automanagerclient did not change.
 - The manager, when a probe request is received, looks at the DB table
   "tool_spec" to retrieve the proper wrapperpath, formal parameter list, etc..
 - The manager assembles a message and sends it out to the appropriate
   path probers, which operate on the request as they have been
   (no major internal changes to the path probers).
 - The path probers call the toolwrapper to run the tests
 - The toolwrappers return a canonical result for that type of metric.
 - The path probers send the result and the actual parameters used by the
   tool to the data collector.
 - The data coll...

arguments and result parsing handled by separate application wrappers.
Currently fping and iperf supported.
Not fully functional at this point: user interface needs extending
to support the generalization, as well as getting the results back
to "opsrecv".

Also merged some of Mike's changes to allow for "private" managers
to use during testing.