Chopped out explanation text about slothd and the XP boot process into the knowledge base.  Add refs to them here.

linkdelays cannot be controlled, so that user sees the error.

of the record. Basically, record them in the XML file, then remove
them before the import, and restore them after. Did I mention that
this was totally bogus?

On modify, create the repo, but add checks to make sure that we do not
bother with operations on branches that do not exist cause they
predate the repo creation. This allows you to move forward after a
modifying an existing template. Also add checks for instantiating a
old template that has no repo at all cause it has not been modified since
adding the repo support.

A few other fixes to make sure that instances are cleaned up after errors.

  DB alongside the resource records. Previously, we stored only the
  nsfiles for current experiments, and purged them when the experiment
  was terminated. The new approach saves them forever using the resource
  record ID. Note that we do not store copies of NS files, but reference
  them indirectly instead so that we can MD5 them and avoid the dups.

  I put a "compressed" bit into the table cause at some point we will
  start compressing the data before storing them into the DB. Or maybe
  we bag this and start using GFS!

  Also note that this addresses the problem of losing the NS file
  history when using swapmod, since the NS file is overwritten.

* Add a pmapping table stores the nodes (and their types) used by an
  experiment. This data is also saved forever, alongside the resource
  records, so that we can more accurately replay an experiment. As Rob
  points out, the node names can also be used in conjunction with the
  ptop files that are saved, to get a 100% accurate remap of resources.

Python's TemporaryFile.mkstemp() may now put dashes in the generated filenames, causing batchexp to fail when invoked through XMLRPC.

flexdatasrv:
Added a new option for meastype 'both' that checks for both lat and bw
measurements.

goodnodes.pl:
Added options for specifying meastype and searchtype

Someone ( Mike ? ) seems to have accidentally commented out loghole archive code in
stop-experiment.

The beginnings of a script that will gather tcpdump logs from synchronous iperfs to the same destination.

cvs repo from the template show page.

Updated felexdatasrv with new algorithm based on maximal clique. Also
added two new options:
 * specifying size=0 returns maximal clique
 * one can specify 'lat' or 'bw' as measurement types to consider
   (default is lat if not supplied)

figured out how to make it much simpler by creating a .app from my
little applescript widget. This bypasses a bug in Firefox wrt how
helper apps are invoked.

run, to store the original attributes, owner, group, and mtime/ctime/atime.

killed when the STOP event is received.

Also fix a couple of minor nits.

the delay setup!  Previously it was just killing it.

highest revision on the branch (or trunk) of the magic .template file,
since doing otherwise would seem to indicate an inconsistency in
what the user is doing. Why? Templates are modified via a tag
operation of the .template file, but splitting off can only be done
via a branch operation. Subsequent mods after a branch have to happen
along a straight line.

Also allow for tag moving to initiate a template modify since the
above implied error can be corrected by doing a cvs update, and then a
retag with the -F option to move the tag.

for each delegated slice we create, we set the 'delegations' attribute to
'utah_nmcontrol', the name of our nm-controller slice that has permissions
to talk to the NM.

Also, a few other fixes.

the run. Includes the bindings for the run and the metadata name/value
pairs. This is the same data that is dumped by template export, so
at this point template_export has been completely superceded by the
CVS repo.

  * Prior to this commit, libplab depended on db state to create slivers
    and slices.  Now it can be done using the regular command line tools
    without the metadata in the db.  This makes development and debugging
    much easier and allows us to use the command-line tools even if state has
    been cleared out of the db (i.e., for sliver garbage collection).
  * Add support for sliver start/stop/restart via the v4 NM.
  * Some support for sliver garbage collection.
  * Various other improvements and cleanup.

where the current stuff goes (datastore, nsfile, etc.). The other
subdir is called "records" and will be populated with stuff that we
currently put into the archive (the contents of the experiment
directory).

There is a record for each run, currently named XXX,YY where XXX is
the instance ID and YY is the run number. I plan to add an XML file to
map these to the symbolic names, but these are not required to be
unique, which is why the directories are not named with them.