GitLab

waiting till it finished setting up (or fails). This is really nice when a
1000 node experiment has gone awry and it is pointless to wait for it to
finish. When we do this, we mark the instance as canceled in the DB, and
then wait for create_instance() to notice it. When it does, it stops
waiting and invokes terminate with a new cancel option at the backend.

through the loop we look to see if signals are pending, and if so we return
early with an error. The caller (libvnode_xen) can use this to avoid really
long waits, when the server has said to stop what its doing. For example, a
vnode setup is waiting for an image lock, but the server comes along ands
to stop setting up. Previously, we would wait for the lock, now we return
early. This is to help with cancelation where it is nice if the server can
stop a CreateSliver() in its tracks, when it is safe to do so.

cancel option, will stop a CreateSliver() in its tracks. We stop the
monitor, then cleanup the slice. I also added an optimization for tearing
down large numbers of VMs on shared nodes, previously we were doing them
one at a time. Note that only the Portal is going to use this option, since
it loosely depends on code in the XEN clientside (described in another
commit).

Also, sync up a couple of files with 10.2.

Do the testing Mike...

When we split the option list, all but the first option would have a
leading space. Fortunately, "nfs" is always the first option.

We don't want to stripe an SSD in with regular HDs (specifically at
Wisconsin) when creating the LVM VG for vnodes. They are typically a
lot smaller and won't improve performance of the VG since any operation
will likely be limited by the speed of the rotating disks.

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.