GitLab

Updated libtbdb for handling multiple sql connections to different database.
It's backward compatible with the older interface.

Also added a new method named 'DBBinaryQuery' for inserting binary data into
the database.

Adding new script name "pelab_sql_dbpush" for syncing data between ops
and DP using direct sql connection to the DP.

cache latest statistics about planetlab nodes (a reduction of the
data in plab_nodehist).

  "$DBQUERY_MAXTRIES" is not exported by the libdb module
All I did was exactly what Template.pm does, but obviously I am a bozo
for not understanding something!

The nfsdump2 source should really be put in the build tree and not the src...

Not used in Emulab software proper, but keeps this file in synch with
pubsub version (thus avoiding link problems).

goodnodes function (so that plabmetrics on boss can grab goodnodes), but
if we want to make anything other flexmon stats public, here's a place to
dump it.  The goodnodes algorithm included is essentially a straight port
from goodnodes.pl, which has problems, so I'll eventually replace it with
a better clique heuristic.

There's also a caching layer in this server which stores certain bits of
the past 24 hours worth of data so that goodnodes is faster.

dbs with passwords (passwords aren't stored, so auto-reconnect will not
work for those connections -- you must catch the right exception and
manually reconnect).

ops.

first one makes python's basic xmlrpc facility act a bit like java RMI
(the SimpleObjectXMLRPCServer).  The second (InetACLXMLRPCServer) filters
incoming requests based on allowed networks (i.e., 155.98.32.0/20 or
similar).  If ever desired, they should be compatible with the boss xmlrpc
server model) with just a tiny hack.

Added an iplane client. It contacts the iplane server and pulls down the latency of all pairs. It outputs a file suitable for use in cloudinfo-set to set initial conditions for an experiment.

* The checkout directory now includes just the datastore directory and
  tbdata/nsfile.ns. This removes a bunch of clutter.

* You can now run template_commit in any subdir of a checkout; the
  python wrapper will crawl upwards looking for the .template file.

  Note that I removed the option that allowed you to do a commit from
  the template tree in /proj/pid/templates since that directory will
  ultimately go away (or at least hide from view), and cause it
  conflicted with the new option and I didn't want to make things any
  messier for no reason.

things for which we previously linked -static.

Fixup some clean targets in a couple of cases as well.

Get capture to compile without SSL (capture-nossl).  This is untested.

if the parsing code couldn't find the line it was looking for it, it
would loop forever. Now, it will detect this and return an error.

described is the one exported to ops via the XMLRPC interface. This is
just playing aroundl no doubt this stuff is going to change.

* template_checkout guid/vers

  Checkout a copy of the template to the current working directory.

* template_commit

  Modify the previous template checkout, using the nsfile contained in
  the tbdata directory (subdir of the current directory). In other words,
  the current template is modified, creating a new template in the
  current working directory (the current directory refers to the new
  template).

  The datastore subdir is imported into the new template, but that is
  the only directory that is imported at present. Might change that.

So this sounds much cooler then it really is. Why?

* This only works from ops.

* The "current directory" must be one of the standard approved directories
  (/proj, /users, /groups).

* Cause, boss reads and writes that directory via NFS, as told to it
  by the xmlrpc client.

At some point in the future it would be nice to support something
fancier, using a custom transport, but lets see how this goes.