fullname field in the DB.

Allowing oversubscription can push the current_load of a pnode
over its max_load, which causes us to try to take the square
root of a negative number. So, add an explicit check for that case.

Consists of just a command line option right now!

Currently this is done using the -E (erase) option to zapdisk to
erase a partition or the entire disk.

We run zapdisk before starting a frisbee load. Ultimately, I want
TRIM support in frisbee proper (to erase rather than skip or zero
free blocks), but erasing the entire disk might be a better option
anyway (frisbee itself will benefit from the TRIMed disk).

Notes:

We only trim the disk when a node is in reloading. Didn't want to take
a chance on having a user reload a partition on their disk and wind up
getting the entire disk erased. That should not happen, but I didn't
want to think through all the possibilities right now.

Only works on FreeBSD right now. Linux MFS will still need to be modified.
Just didn't want to track down how Linux does block erase right now.

The clientside here is different than what is used on the Moonshots.
On the Linux-based Moonshot MFS, we TRIM in slicefix by running fstrim
on the root FS we just layed down. This used to be a good alternative
back when the root FS occupied the entire disk, but now it won't work
as well as we will only trim blocks from the first 6GB. Need to switch
this over to the zapdisk (or frisbee) based TRIM.

The server infrastructure on the Moonshots is the same: tmcc passes a
TRIM=1 flags in "loadinfo" when the disk should be trimmed. So when to
TRIM is based on the time since the last TRIM, and can now be specified
site-wide, per-nodetype, or per-node.

Currently, slicefix (x86 or ARM) doesn't do anything to the FS layed
down to ensure that TRIM is done during the lifetime of the FS. Both
FreeBSD and Linux have such options that can be set when the FS is
created or added with tunefs. We need to think about this for mkextrafs
and local blockstores as well.

Make the interval between TRIM operations a per nodetype (or per node)
attribute instead of a global site variable. The sitevar will still be
used to turn TRIM on or off globally.

The latter causes on/off/cycle operations to return a generic error
(though the operations do work!)

	boss> wap perl prereserve lbsbox pcxxx pcyyy ...

Overall pre-reserve handling is unchanged; if there is a another higher
priority type pre-reserve, it will be filled first. Moral, be sure to think
about the priority argument, which you had to do anyway.

need node_reservations for, well, node_reservations.

is in the Cloudlab or aptguest projects.

ptopgen that adds wiretypes to the ptop file.

to use this code.

out who is returning 100+ level errors.

update from two places (here, and from the apt event daemon).

the alternate pubsubd, and updates the portal experiment as indicates
(slice and sliver status, and imaging status/size).

into the local event stream. These events are different then normal emulab
events in that the SITE is set to the URN of the aggregate, and there is
json representation of the slice/sliver status. There are other fields as
well that are not in normal emulab events. These events can mix okay with
emulab events on the local boss, nothing will care about them. But they
will get forwarded to pubsubd at the portal if CLUSTER_PORTAL is set in the
defs file.

efficiently.