For the case in which mkextrafs is used to create local homedirs/projdirs:

Look for the desired mount point (/local) in /etc/fstab and use that if
it exists (i.e., that FS was already setup by the blockstore system or a
previous mkextrafs).

Otherwise, look for /var/emulab/boot/extrafs which should contain info
left behind by the local blockstore setup code indicating a FS or unused
device to use. For an unused device, rc.storage will identify the largest
available device that is at least 10MB.

Flush() it.

monitoring system.

New portal_monitor daemon does a GetVersion/ListResources call at each
of the clusters every five minutes, and updates the new table in the
DB called apt_aggregate_status. We calculate free/inuse counts for
physical nodes and a free count for VMs. Failure to contact the
aggregate for more then 10 minutes sets the aggregate as down, since
from our perspective if we cannot get to it, the cluster is down.

Unlike the jfed monitoring system, we are not going to try to
instantiate a new experiment or ssh into it. Wait and see if that is
necessary in our context.

On the instantiate page, generate a json structure for each cluster,
similar the one described in issue #172 by Keith. This way we can easily
switch the existing code over to this new system, but fail back to the
old mechanism if this turn out to be a bust.

Some other related changes to how we hand cluster into the several web
pages.

in the AUTOLOAD block, throwing off the error reporting.

a user error, although manifesting as DBQuery error (duplicate key) is
not exactly friendly.

1. If the blockstore name has a '-' in it, the dm name will have '--'.
2. The version of "lvs" in Ubuntu 16 has a new attribute in the output.

Might explain a lot annoying cache behavior.

One was minor (not rolling the ip optional field length into
pskb_may_pull check).  The second was not minor; we weren't
appropriately calling pskb_may_pull to check if the iph + icmph + ipod secret
was in a linear buf... and then we finally ran across a driver for which
the ipod secret did not fully fit in the first skb buffer chunk... so
linearization was actually necessary.

Another way that has been suggested to fix the potential bugs that arise
from linearization, the use of skb_header_pointer, isn't the most
desireable option in this case, since it costs more stack memory *for
each* input ICMP packet (and nearly 100% of the time, it's not an ipod
and we don't care).

Temporary fix for iMinds cluster status in instantiate page. Remove when actual stats are available again.

only right now.

breaking stitching.

and tooltips.

we sort them into the right bins.

these with last update, we were missing some glyphs.

an inconsistency in SliverAction(); when operating on the entire slice
we do the whole thing in the background, returning (almost) immediately.
Which makes sense, we expect the caller to poll for status after.

But when operating on a subset of slivers (nodes), we do it
synchronously, which means the caller is left waiting until we get
through rebooting all the nodes. As David pointed out, when rebooting
nodes in the openstack profile, this can take a long time as the VMs are
torn down. This leaves the user looking at a spinner modal for a long
time, which is not a nice UI feature.

So I added a local option to do slivers in the background, and return
immediately. I am doing the for restart and reload at the moment since
that is primarily what we use from the Portal.

Note that this has to push out to all clusters.

same forced typing to untyped VMs by appending "-vm" to the architecture
in libvtop and ptopgen. This solves a problem that was causing the
mfactor to effectively be ignored, mapping one vm to a physnode when the
type is plain "pcvm".

instead.

See comment in code.

Total wait time before capture gives up is a smidge under 5 minutes.

to the person updating it. Minor changes to the templates for display.