GitLab

Soon, we will have images with both full images and deltas, for the same
image version. To make this possible, the image path will now be a
directory instead of a file, and all of the versions (ndz,sig,sha1,delta)
files will reside in the directory.

A new config variable IMAGEDIRECTORIES turns this on, there is also a check
for the ImageDiretories feature. This is applied only when a brand new
image is created; a clone version of the image inherits the path it started
with. Yes, you can have a mix of directory based and file based image
descriptors.

When it is time to convert all images over, there is a script called
imagetodir that will go through all image descriptors, create the
directory, move/rename all the files, and update the descriptors.
Ultimately, we will not support file based image paths.

I also added versioning to the image metadata descriptors so that going
forward, old clients can handle a descriptor from a new server.

The stuff in db/Port.pm (Port::LookupByIface) wasn't handling the MLE
case where there are two wires table entries for physical wires with a
logical wire implemented by them; for my experiment, when snmpit was
trying to create the physical vlans on the apcon, it would grab the
logical wire instead of the physical one as it populated the Port
objects, and that screwed vlan creation up (the member port for the
physical layer 1 vlan gets labeled with a switch WIRE_END instead of
node -- which is correct for the logical wire, but not the physical).
So, I changed the query to check that wires.logical ==
interfaces.logical ; see the code.  This is a limited fix, maybe --
maybe that method should really do more verification to make sure it's
grabbed the correct wires table entry -- but since we only have 2 layers
it's plenty good for now.

change had some problems.

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.

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

metric until Mike adds uncompressed data size to the images table.

Hopefully will prevent catastrophic DB failure as we no longer make
tens of thousands of DB queries to find the first available uid.

datasets just like images, when versioning is enabled. Same syntax as
images (pid/imagename:version) in the NS file and rspec.

nodes.

* Various UI tweaks for profile versioning.

* Roll out profile versioning for all users.

* Disable/Hide publishing for now.

* Move profile/version URLs into a modal that is invoked by a new Share
  button, that explains things a little better.

* Unify profile permissions between APT/Cloudlab. Users now see just two
  choices; project or anyone, where anyone includes guest users in the APT
  interface, for now.

* Get rid of "List on the front page" checkbox, all public profiles will be
  listed, but red-dot can still set that bit.

* Return the publicURL dynamically in the status blob, and set/show the
  sliver info button as soon as we get it.

* Console password support; if the aggregate returns the console password,
  add an item to the context menu to show it.

* Other stuff.

Fix bug in Jacks Editor wrapper on cancel

definition of management interfaces. See comments in the diff.

of concurrent mappers that can run at once. Currently used only
on the Geni path.

recently we have had a spate of errors caused by double clicks causing
duplicate entries.

returning a writeable flag.

in the group.

You can now simultaneously RW and RO map a dataset because all the RO
mappings use copies (clones) of a snapshot. Only a single RW mapping
of course.

When the RW mapping swaps out it automatically creates a new snapshot.
So there is currently no user control over when a version of the dataset
is "published", it just happens everytime you swapout an experiment with
a RW mapping.

A new RW mapping does not affect current RO mappings of course as they
continue to use whatever snapshot they were created with. New RO mappings
with get the most recent snapshot, which we currently track in the DB via
the per-lease attribute "last_snapshot".

You can also now declare a lease to be "exclusive use" by setting the
"exclusive_use" lease attribute (via modlease). This means that it follows
the old semantics of only one mapping at a time, whether it be RO or RW.
This is an alternative to the "simultaneous_ro_datasets" sitevar which
enforces the old behavior globally. Primarily, I put this attribute in to
prevent an unexpected failure in the snapshot/clone path from wreaking
havoc over time. I don't know if there is any value in exposing this to
the user.

which looks at environment variable to determine what user should be used
for access checks. Now used from the protogeni interface, when real
accounts are in use (but all work still done by geniuser).

Was using internal EventSend but that is really just for talking
to boss and we need to talk to ops.