Specifically designed to avoid using root SSD on new d430 nodes.

old parents, assign was hitting a buffer overflow cause of too
many parents.

FTOS has changed from using vlan-specific ifIndexes to the more
sensible choice of vlan tags as indexes in the Q-BRIDGE-MIB tables.
However, it still uses these ifindexes in the RFC1213 and IF-MIB
mibs!  This broke the snmpit_force10 module.

No more 1,10,11..19,2,20,21...

This will only be for boss and for FreeBSD 10.2 and beyond.

hosts (as for XEN phys hosts). This was never a problem, until we got a
cluster with super long node names.

paths.

to the mapper and then to assign.

Need to change this entirely.

Looks like we are going to want the ability to tweak vnode placement per
run rather than by building new assign binaries. So, add new '-S
balance' and '-S pack' options. I suspect it would also be useful to add
'-S spread' to try to spread vnodes out across as many hosts as
possible, some people want this when using shared hosts.

wait time to 15 minutes, but watch for progress. Any time a node changes
bump the waiting time above five minutes. Just a start point, lets
see how it goes.

for a 500 node experiment is really BIG.

100s of times in really big experiments.

big topologies.

When set, the goal is to pack vnodes as tightly as possible - that is,
to penalize wasted slots in assignments.

One downside is that this will tend to make really lopsided mappings:
eg. if you have 50 slots per pnode, and 51 vodes, you will end up
mapping 50 to one and 1 to the other.

The other downside is that I have not yet thought about how to balance
this with link weights.

that messes up the snapshot. So make it read-only.

not be in the holding project, so add them.

they are added by the mapper, and have no virt table entries. I will need
to add a new tmcd call to provide VM hosting configuration parameters.

1. Don't stat all exported mountpoints from boss to see if they exist.
   Not only is this wrong from boss (a mount may be valid, but not yet
   exported) it also makes the automounter work its butt off as we might
   stat hundreds or thousands of directories across NFS. The original
   purpose of this was to keep mountd from freaking out when presented
   with a non-existent directory. Since mountd freaking out is about as
   rare as the sun rising in the east, we keep this check but do it on
   the proxy (ops) side instead.

2. Have exports_setup (boss) generate a list of directories that it should
   be able to mount. This goes in /usr/testbed/etc/validmounts.txt and will
   be used by autofs (I hope) to narrow down the wildcarded "/users/*"
   and "/proj/*" mounts to those that might actually work. Right now you
   can "ls /users/WtF" and it will try to mount it from ops and take 4
   seconds to timeout and fail.

Some fixes for the status picker. Fixed showing VM numbers, can now show both VM and PC numbers, fixed a few minor bugs