* remove check for gather arg, use TESTINFO from tmcc hwinfo
  instead. Only call tmcc once. Let non-MFS boot collect data.
* tmcc hwinfo not return a TESTINFO line. Handle the LOGDIR, COLLECT
  and CHECK indicators
* Do to variable scoping make sure everything runs in the shell.
  Do not 'exit' from called programs. Source called programs instead
  of starting new shells.
* Nothing wrong with the which() function I put in since the
  MFS/busybox installation does not have one, but if we have a real
  which(1) program use it.
* output format changes and programming space changes
* remove check for gather arg, use TESTINFO from tmcc hwinfo
  instead. Only call tmcc once. Let non-MFS boot collect data.
* tmcc hwinfo not returning a TESTINFO line. Handle the LOGDIR, COLLECT
  and CHECK indicators
* Do to variable scoping make sure everything runs in the shell.
* Do not 'exit' from called programs. Source called programs instead of
  starting new shells.
* Nothing wrong with the which() function I put in since the MFS/busybox
  installation does not have one, but if we have a real which(1) program
  use it.
* call sub-programs by sourcing not by starting new shell.
* oops mfsmode is not set until initialize is run. also set -e -u to
  catch this type of thing.

Checknode tests once again run in standard images and can collect
data.

* All tests can now be "sourced" from gatherinv to insure everything
  runs in a single shell.
* All tests can also be called standalone.
* MFS mode and non-MFS mode honor the CHECK and COLLECT flags.
* Create, if necessary, a new project save directory.
* This will be needed once every-time checknodes is run in a new project.
  path is /proj/{pid}/nodecheck.
* If script can't run quit with a 'return 0' so the rest of the checks
  can continue.

Change filename gatherinv -> checknode

* Can't run in MFS mode if not in the emulab-ops pid

So we don't hang forever if the tipserver is down.

recorded about what it is doing.

(This was accidentally broken in the previous commit.)

This is the client-side of our current "swapmod" goal. You can add and
remove blockstores, but you cannot modify the attributes of an existing
blockstore.

Prior to this commit, XEN guests disks were single partition, no MBR,
the bits dumped into the lvm. This makes a snapshot of a XEN node,
look completely different then a physical disk image, especially if
users want more disk space (mkextrafs) inside the guest, and then want
to take a snapshot of that, and then run it on a physical node (which
was not possible).

With these changes, guests now use the same MBR layout as our version
two MBR, which makes them interchangeable with physical disk images.
In fact, the goal is to be able to switch back and forth as needed,
based on physical resource availability.

they enter and leave projects. We were leaving lots of files in
the guest group.

    <sliver_type name="emulab-xen">
      <emulab:xen cores="1" ram="512" disk="8"/>
    </sliver_type>

We currently ignore cores ... Ram in MB, disk in GB.