GitLab

I'm not sure exactly why this was originally like this (let the node out
of reloading before doing the console-based reconfiguration --- cleaning
out the old config and writing a default one, via the console), but it
now fails because the node gets released from reloading (and thus its
reservation is cleared) before the reconfiguration step can grab the
console line via tiptunnel --- and a subsequent tiptunnel connect fails,
presumably because the reload_daemon no longer has permission to grab
the line.

Anyway, we'll try this... I can't see any obvious negative side
effects.

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.

extensions, to show on the admin extend page.

For imagezip. Since I am the founding--and only--member of both camps,
I get to decide what is right! I am back to generating imagezip relocations
(for FreeBSD images only) since those images are just a big pile of bit-slag
if you want to load them anywhere other than their standard location.

Just luuuv string manipulation in C...

instead of cloudlab-ops, which we want to use for the combined cluster
email list. Send more email to logs instead of ops, now that we are
generating enough of it.

their experiments, we fall back to naming it for them.

picking pieces out, so I added this:

  my $foo = GeniHRN->new("urn:publicid:IDN+emulab.net:testbed+slice+myexp3");

and provides:

  $foo->domain();
  $foo->type();
  $foo->id();
  $foo->urn();

and has a stringify method that returns the urn, so that existing code all
works.

The problem though is the XML::RPC and Frontier libraries provide no hooks
to catch this, and rather then using a stringification, they both convert
all blessed references into structs, and so anyplace that puts a urn into
something to go out on the wire, has to be changed to force to the string.

Damn, how disappointing! So all the code is here but basically disabled
until I find time to go through all the code.

The "Emulab configuration" of the mserver will now use uploader_path
if set rather than path.

A slight semantic change goes along with this. If the uploader_path is
set, we assume that it is a temporary file to upload to and we (the mserver)
do not do the dance of uploading to our own temporary and moving it into place.

of image files present.

Add uploader_path to communicate the path to use to write the file.
Set in create_image.

   RELOADSETUP -> RELOADFAILED
   RELOADING -> RELOADFAILED
   RELOADFAILED -> SHUTDOWN

defaults to NULL since we did not require names prior to this, thus there
is no unique key defined.

defaults to NULL since we did not require names prior to this, thus there
is no unique key defined.

the xl create, so that we can watch for VMs that do not get to TBSETUP in a
reasonable amount of time (which means it hung and we need to restart it).

time we "xl create" and the guest sends in a TBSETUP. We sometimes hang up
here for reasons that elude us, but a restart from boss usually gets it
going the second time.

Also add a couple of missing state transitions that stated was whining
about.

require admin approval just grant it.

The -S (sanity check) option adds the ability to do the obvious: validate
an image file using its signature. So what did imagehash do all these years?
Well, its primary job was to generate a signature file that imagezip could
use to generate a delta. Secondarily, it would compare a signature vs. a dis
with an image loaded on it. But now we use imagezip to gen most signatures
while generating the image itself.

Also added -X (xtreme hack) option to have imagehash attempt to check or
generate signature file entries in a way that is consistent with what
imagezip does. The difference is that imagezip can produce hashes for
blocks that span chunk boundaries, imagehash (previously) never did this.

So when validating an image whose signature was generated by imagezip:

   imagehash -SX foo.ndz

To generate a new signature for an image:

   imagehash -cX foo.ndz