Support FreeBSD 10.3. We will need to be moving to this before long
as 10.2 EOLs in two days.

Support setup of "Emulab-aware" ZFS use in install scripts. Note that
the core support code was already done (WITHZFS, WITHAMD). Mostly this
involves changes to setup either amd (WITHAMD==1) or autofs (WITHAMD==0)
on the boss node and to NOT add mounts of /{users,groups,proj} to
/etc/fstab. We still need to add a section to the install documentation
about setting up a zpool for Emulab to use. There was also a fix to the
firstuser script which did not do the account setup correctly.

Support setup of ZFS in elabinelab. The elabinelab attributes CONFIG_ZFS
and CONFIG_AUTOFS are used to convey intent here. Currently they can only
be used in an "ops+fs" config (e.g., the standard boss and ops config,
NOT the seperate fs node config). It should work with either the physical
or virtual node setups:

* For the physical node setup, we actually use local blockstores ...

OSinfo and Image into a single object for the benefit of the perl
code. The database tables have not changed though.

image_import by URL to get initial images.

This should be run whenever an image is created or updated and possibly
periodically over existing images. It makes sure that various image
metadata fields are up to date:

 * hash: the SHA1 hash of the image. This field has been around for
   awhile and was previously maintained by "imagehash".

 * size: the size of the image file.

 * range: the sector range covered by the uncompressed image data.

 * mtime: modification time of the image. This is the "updated"
   datetime field in the DB. Its intent was always to track the update
   time of the image, but it wasn't always exact (create-image would
   update this with the current time at the start of the image capture
   process).

Documentation? Umm...the usage message is comprehensive!
It sports a variety of useful options, but the basics are:

 * imagevalidate -p <image> ...
    Print current DB metadata for indicated images. <image> can either
    be a <pid>/<imagename> string or the numeric imageid.

 * imagevalidate <image> ...
    Check the mtime, size, hash, and image range of the image file and
    compare them to the values in the DB. Whine for ones which are out
    of date.

 * imagevalidate -u <image> ...
    Compare and then update DB metadata fields that are out of date.

Fixed a variety of scripts that either used imagehash or computed the
SHA1 hash directly to now use imagevalidate.

mark the images to run on them. Not a great way to do this; needs more
thought.

image load. Also download the MBRs.

in which it will later run. Now setting up and protogeni during the
install.