user is not logged in.

User lockdown is as before, user can override that on the terminate
page. Admin lockdown is like Classic lockdown; the flag must be cleared
before the experiment can be terminated, there is no override on the
termination page.

UI changes on the status and admin extend page for the additional
flag (instead of a single lockdown, there are now two).

when they have leaked.

discussion in issue #134. Only studly user see this for now, so
that we can play with phony reservations.

1. Add a Reload icon on the Graphs tab, to reload the cluster data and
   redraw the graphs.

2. Implement a Reload Topology function, with button on status page, to
   sync the portal topology with the clusters current manifests. Currently
   available to studly users only. This closes ticket #92.

* 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.

an interaction between htmlentities and json_encode. I got rid of the
former and added options to json_encode, but that is not safe, so need to
make sure we use jquery .text() and underscore template <%- when displaying
that text.

switch to new admin extend page that includes more summary and utilization
and cluster info, to make it easier to determine the merits of a particular
extension. As part of this change, extension are now first class objects
associated with a instance (mostly a convenience, better then the ongoing
text field, which was annoying to do anything interesting with).

that in PHP, yuck. This is mostly to get ready for beefing up the extension
code as discussed, and do not want to do any of it in PHP.

Note; in another commit I added emulabfeature support to PHP (via a callout
to the perl code), I am going to roll this out slowly. Well, admins will
get it right away.

code into aptforms.js. More prep for portalization.

admins see it.

page can use the Shell button to log in as themselves.

Portal, what clusters are usable by each portal, ditto datasets. Remove
all hardwired cluster urns and urls.

control network port modification), and add front end support to the Portal
status page (admin mode only of course)

extension history, All buttons disabled/hidden.

1. Use information from sliverstatus to indicate that nodes have startup
   execution services running, and then tell then when they have finished,
   and they exited with non-zero status, indicate that they failed. We also
   hold saying the "ready" in the upper panel until all the services have
   exited, we say "booted" instead, and also say that nodes are running
   startup services.

2. For snapshot, when we know an image has to be copied back to its origin
   cluster, tell the web interface, so that we can add another step to the
   imaging modal ("copying"). We know the copy is done when the origin
   cluster has posted the new image data to the IMS, so we do an additional
   poll in the backend waiting for the image server to get the data, and
   then we mark the image as ready for use.

1. Provide text box to add to email message that is sent to user.

2. Track outstanding admin required requests, add a Deny button for those.

3. Add option to experiment listing for admins, to see outstanding admin
   required approval.

the apt_instance table record, and display that in on the admin extension
page so that we have it all in one place instead of email messages.
Also show the cluster usage graph in on the admin extend modal.

* Add a "lockout" checkbox to the red-dot instance view. When checked it
  prevents all future extension requests (no pad time granted either). This
  is an active checkbox; backend ajax call when you check/uncheck.

* Add Created to the instance view panel.

* Most of the snapshot node changes, but hidden for now until I get more
  testing done. This includes the modal and ajax changes, but not the
  backend changes (still in my devel tree).

* Minor changes to date formatting.

* More details in the extension email.

at the next extension, to avoid user aggravation. Also show the reason on
the termination modal if the experiment has been locked down.

password to collapse above the console window, inside the tab.