GitLab

the JS code to handle the new format.

Also add a -s (silent option) to avoid warnings that cause needless email
from the Geni XMLRPC interface.

rules. Need another approach.

array; there are two versions of the "where" field.

some more work to handle these special cases like libossetup does, lest we
get a lot of special cases.

Also fix a bug related to start/end times for short-lived experiments.
Note that a side effect of this fix is that the first aggregated data
point returned by idlestats may include data prior to the beginning of
an experiment (when returning data for nodes in an experiment).

a (slightly) larger selection of NFS mount options, then just yes/no.

(Re)initializing the ssh keys and ssl certs breaks the elabinelab.

for the most part that is all they are going to have. We still ignore them
on physical nodes, since they refer to MLE interfaces.

always updating the local slice expiration (for the apt daemon).
Also fix a problem with lockdown. But neither of these is what I was
looking for.

* Add a "lockdown" checkbox to status page (red-dot) next to the lockout
  checkbox.

* Change Lockdown on adminextend page to the an active checkbox (like
  lockout).

* Add openstackgraphs.js, not in use yet.

page, and be able to use them in a profile.

expiration #days in the future, clears the lockdown, sets the lockout (no
free extensions) and sends the text in the box to the user.

FreeBSD doesn't seem to do this by default.

We don't need it any more (and haven't since we used jail-based vnodes!)
and it just creates vulnerabilities by running rpcbind.

Note that we do need an NFS server for elabinelab ops/fs nodes, but rc.mkela
takes care of making sure it is turned on.

* More on issue #54; watch for openstack experiments and try to download
  the new openstack stats file via the fast XMLRPC path. Show this as a
  text blob in a new tab on the status page, still need to graph the data.
  The apt_daemon handles the periodic request for the data (every 10
  minutes), which we store in the apt_instances table.

* Addition for Rob on the admin extend page; Add a "more info" button that
  sends the contents of the text box as an email message requesting more
  info and stores that in the ongoing interaction log. Responses from the
  user are not stored though, might look at that someday.

* Another addition for Rob; on the extensions list page, also show expired,
  locked down experiments. Note the sorting; at the top of the list are
  actual extension request (status='ready') while the bottom of the list
  are status='expired'.

* Add a "graphs" tab to the status page, which shows the same idle stats
  graphs that were added to the admin extend page. Most of this change is
  refactoring the code and sharing it between the two pages.

disabled pending more discussion/debate (see issue #89) about whether it is
a good idea.