GitLab

Up past 3:30AM this morning.  Despite a constant stream of caffinated products,
I am incapable of anything more demanding than cut and paste...

These variables were previously constants hardwired into create_image:

images/create/maxwait:
    Max time (minutes) to allow for saving an image
images/create/idlewait:
    Max time (minutes) to allow between periods of progress
    (image file getting larger) when saving an image (should be <= maxwait)
images/create/maxsize:
    Max size (GB) of a created image

Max image size should really be in DB as a per-testbed (per-project? per-user?
per-something!) value, and not hardwired here.  In the meantime, we set this
big and let disk quotas do the dirty work of limiting size.

Making crossdomain more permissive like this allows us to host the flash client on www.emulab.net which has a CA-certified certificate.

the toplevel makefile. Add a quiet mode. Minor cleanup. Also make
it possible to run the from object directory before the initial
install.

fragment scripts, much like we do with the DB updates. The intent
is to simplify testbed update for remote sites.

this will happen via the new update-testbed script.

this will happen via the new update-testbed script.

this will happen via the new update-testbed script.

that they all write proper pid files in /var/run. You can not actually
"stop" the testbed daemons from the command line.

for reopening the logfile for the benefit of newsyslog.

for reopening the logfile for the benefit of newsyslog.

CheckDaemonRunning(), MarkDaemonRunning(), and MarkDaemonStopped()
do what you expect.

Also write the commit hash of the source code into the version_info
table for easy access (as from the web interface).