GitLab

Revision: bcf206e6d731108b893d9eff3fae06cdde41e405
MIT License

image will boot after reloading XEN43.

In particular, do a case-insensitive match with "serial number".

* Get rid of login (and logout) by ajax. Use the modal, but do a
  normal form submit so that the page is refreshed properly.

* Bug fix for - and _ not working in Firefox/Shellinabox window; thank
  you google search.

* Fix for NaN dates on Firefox. Turns out Javascript Date() is not
  rfcwhatever compliant. Too funny.

* Fix permission check that was allowing guest user to see and use
  someone else's experiments.

Not sure this is really useful, but Kevin Tew's test framework
uses it.

* Add a .htaccess file that does the rewrites, instead of in the httpd
  confile file. Added Rob's stuff for rewriting urls to hide the .php
  although not sure this is working correctly yet.

* Add simple MyExperiments page so that logged in users can find their
  way back to running profiles.

* Move the DB table holding the running experiment records from the
  geni-sa DB into the main Emulab DB. Lots of little changes for that.

* Change logout to plain link instead of ajax call. That was a silly
  thing to do.

* Bug fixes to ssh keys and shell login from the status page.

across reloads. If we do not do this and the state is lost, we
cannot reboot a halted VM since we won't know what image it was
supposed to boot, etc. There is probably a way around this, but
it is better to keep this state anyway.

without silly hack.

PREQUEST allows us to notify the server that this is a retry,
where REQUEST does not.

the shell function, cause the the ssh handle was using click.
I changed the handler to use mouseup,mousemove,mousedown events
(derived from a google search).

the actual DOM instead. The copy resulted in the click handlers
being lost. Seems odd, but this is more efficient anyway.

Obviously, we never fuzz tested this puppy!

For the Emulab configuration, we add the new site variable
"images/frisbee/maxrate_dyn" which should be set non-zero to enable
dynamic adjustment. If maxrate_dyn is enabled, then the maxrate_{std,usr}
values are used as both the initial and maximum values for the BW of any
instance. Really, if maxrate_dyn is on, then both of those should be set
to the same value so that all servers are operating the same and the value
should be just above the link BW.

For the "null" configuration (aka, the subboss configuration),
this is set by adding command line options:
    -O dynamicbw=1,bandwidth=1100000000
which would enable it and start/cap the BW at 1.1Gb/sec.