without waiting for nodes to sync with PLC.

now, this is keyed off nodetype.  Lots of hardcoded constants and config
stuff moved to attributes in the db.  You can now set per-PLC and
per-slice attributes, so you can (for instance) use different auth info
whenever you want.  Experiments can use preexisting slices if somebody
sets up the db before swapin.  Also, we no longer have to rely on
slices.xml to sync up nodes/sites with PLC... can use xmlrpc instead.

Lots of code cleanup, improved some abstractions, etc.

in libplab.  Parallelize plabhttpd and make it take command line args.
Increase parallelization in plabdist.

Also make plabmonitord dist out the rootball and restart thttpd on plab
service slivers that it has just resurrected.

tested at once) gets negative and too many processes get forked.

This is ridiculously hard to do with CVS.

I haven't removed the sshdport column from the nodes table yet, in
case I need to go back quickly.

during rollout.

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.

  * 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.

processing the node_history table, but that is *way* too slow to do on
the fly (say, from the web interface) cause of the number of records,
so the summary info is stored in the new node_utilization table. I
generate the summary info as new entries are added to node_history (in
SetNodeHistory) but if that becomes too messy, we can just as easily
shift to processing the table on a nightly basis.

Note that I added a new "inception" date field to the nodes table,
which will get set on new nodes, but for existing nodes I have to
derive it from the first entry in the node_history table, or else the
numbers will not make sense.

changed slightly, change parsing a bit).  The iperf bw
measurement src seems to have gone missing, so we're just not getting
these anymore.  They could come from flexlab if we ever care.

nodehist metrics to their own table for the same reason.

Also add plabnodehistmetrics, which ranks plab nodes using
libplabnodehist, writes the ranks and metadata to
/share/planetlab/reliable_nodes, and inserts a '+unavail' weight into
node_features for planetlab nodes.

(i.e., when plab nodes are up and down a lot for short periods of time).
See the comments to figure out how it works.  It's not quite done yet, but
is good enough for now.

recently.  Reduce plab_nodehist logging to get rid of implicit
redundancies.  Remove some debug code.

table... thus it no longer starts over every time it gets restarted.

last three days remain.  Saves cleaned rows to a logfile for future use.

times to give the vserver a chance to settle after creation via xmlrpc.
On v4 nodes, we can't seem to login immediately after sliver creation;
waiting a few seconds solves that problem.

as 'plabstatus-STATUS'.  Also add support for multiple ticket versions. I
had avoided this because I thought rollout would happen fast and I didn't
want to whack the db just to do this... but rollout is taking a long time
and hitting PLC for legacy tickets is too slow to ignore anymore.

slightly less.  Also unfix the previous "fix."

tree for v4 planetlab node support.  Currently, we support both v3 and
v4 NMs via a little wrapper, and we dist out different versions of the
rootball depending on NM version.  Also updated various parts of libplab
to log success and failure from interactions with planetlab nodes to the
db, and there are beginnings of support for that in plabmonitord.in.

importantly, fix several places where inserts were using %d as argument
placeholders in queries.  When using the MySQLdb module in python, you
can only use %s as a placeholder in "prepared" queries---the module looks
at the types of the values to see how to format them in the query.  This
behavior is insidious and contrary to the python standard DB interface
documentation, but that's how it is.