GitLab

We do this similarly to Xen.  There's a new script (container2pty.py)
that attaches to the Docker container, via the docker daemon, and
exports its stdio as a pty.  Then we run capture on a symlink to that
pty.  New options to capture tell it to keep retrying to open the pty
maxretries times (we invoke with infinitely many retries); and to not
prepend /dev to the device string.

free list box. Instead, use a per portal list of types to prune.

the X axis extends further out then needed.

need to deal with scaling still.

error is a resource shortage.

Switch the user version of the cluster status page to a new page that
provides a table of immediately available nodes as well as the time
series graphs. Note that the graphs are slightly different on this page
since we are shoiwing "available for allocation" instead of "available
to reserve", so we have to add the 'held' number to the free count
returned by Forecast().

The bulk of the commit is really shuffling things around a bit to make
it easier to reuse the graphs code in the new page.

the user.

This is a hack to get cnetwatch to shutup about dbox3 already!
It should be generalized to support both node_type_ and node_ attributes to
configure the various (currently global) parameters.

Users in lots of groups could overflow not one, but TWO different
buffers!

1. First off, we no longer do automatic lockdown of experiments when
   granting an extension longer then 10 days.

2. Instead, we will lockdown experiments on case by case basis.

3. Changes to the lockdown path that ask the reservation system at the
   target cluster if locking down would throw the reservation system
   into chaos. If so, return a refused error and give admin the choice
   to override. When we do override, send email to local tbops informing
   that the reservation system is in chaos state.

reservations at the target clusters.

rolled monitor code. This is featurized (all the old code is still
there) under GeniOsSetup for testing.

Geni path instead of hand rolled monitor code.

Closes #343.

has no encrypted certificate, generate one for them using a randomized
pass phrase.

Not sure why I singled out grub1 to not add that argument, it is
documented to work and does. By not setting it, old CentOS images
that used grub1 would hang at boot time for > 5 minutes causing a
stated timeout and reboot. Once stated had tried that 3 times, it
would stop doing the reboot and eventually the node would come up.

I have no idea why it was hanging unless the console output was
going to the real serial port (com1) and that was either generating
garbage input causing grub to go interactive or causing output to
block.

just kill this number when we have timeline graphs done.

This was the case where we would make a copy of the dom0 root FS
to create the vnode's FS.

missing handler for quarantine checkbox.