GitLab

operating in standalone mode (not part of a federation), which would be
the case for everyone that is not us. Further exercise would be to
automate portal setup when part of a federation. Not a big deal to add,
but lets checkpoint what I have done so far.

a standalone site (or an elabinelab).

fed/nofed json files, but those are Mothership specific. So when not the
Mothership, use the type free/inuse counts we store in database and do
not worry about fed/nofed. Eventually want to drop use of those files,
will do that next.

images we import as part of the normal boss setup. This reduces a bunch
of confusing clutter inside, and improves the testing of the image
import/usage path. As per Mike, remove the elabinelab option to
mfrisbeed that would ask the outer boss for a missing image.

message instead of silently failing. The message points to the accept
certificate page on ops, since typically this is the cause of the
error (a self signed certificate). Unfortunately there is no way to know
why it failed, the browser tells you nothing.

try to chown the source directory.

the permissions.

DBQuoteSpecial() on it already, and we avoid lots of backslashes!

have default values. Hmm.

revision.

Also a mysql 5.7 fixup.

shellinabox.

out of the log file. Accept default-vm as synonym for emulab-xen. Kill
exclusive flag on raw pcs so the conversion completes. Throw error on
duplicate iface.

messages so they are easier to find in the log.

remote blockstore interface names with the wrong node name prepended,
and allow them so that rspec comparison works.

Apparently there are some issues with UFS2 support in Linux.
Fsck mostly fixes incorrect block counts:
    INCORRECT BLOCK COUNT I=1043374 (0 should be 8)
for inodes that get created by Linux (e.g., /etc/ssh host keys,
/var/emulab/boot stuff). Everything seems to be fine after the fsck.

Also: specify "-Zy" when creating LVMs so that old GPTs, superblocks, etc.
don't leak through. LVM seems to be frightfully deterministic in its
allocation strategies to the extent that virtual disks created in previous
experiments have their metadata show up in newer experiment LVMs.
All the things that are changed

Previously, we were still putting the default utah boss key there.

camcontrol cannot change the cache settings on "ada" devices.

Try to catch the occasional corrupt filesystem before we make it worse.

FreeBSD 8.x smartctl binary does work with 10.x kernel.

This will close issue #310.