GitLab

This is pretty minimal "support", but it is working.  I have some
uncommitted fixes for event/linktest/iperf, however, as mentioned in
issue #351.

Built out emulabizatization of docker alpine

See merge request !29

The organization of the code follows the guidelines set by the
ubuntu version extremely closely. Big differences to notice are
some of the package name changes switching from apt-get to apk,
the requirement of the --disable-ssl flag when running the configure
command for pubsub and the methodology required to build a custom
apk package to use our custom runit. Apk has lots of issues and
argues against building a new .apk package as root, so
runit-artifacts.sh creates a new user, gives them super user permissions,
adds them to the abuild group and runs the runit-packager.sh script
as this new user. Design of this solution was focused on doing as
much as possible while remaining in root. Enjoy!

Replaced by 40-emulab.

With it, iSCSI blockstores on Ubuntu16 and CentOS would not work.

but one can guess.

This race always existed cause there was no locking, it just didn't
manifest since there are not many multi-aggregate experiments.

multi aggregate experiments.

Turn on use of incremental updates in mountd (requires our special mountd)
and stop automatic export of all filesystems to boss (requires changing the
default ZFS "sharenfs" attribute for filesystems).

On nfree, we call nfsmfs_setup will all nodes in the experiment even
though it is unlikely that any of them are in the MFS. Even so, we were
unconditionally doing a "zfs share -a" to make sure the exports table was
up to date. This hurt hard in our environment where we have a zillion users
and oodles of nodes (these are very precise thresholds!)

Also, use "mount" to get the list of mounted NFS MFS filesystems rather
than "zfs list" which likewise can be quite painful when there are a gazillion
(1 gazillion > 1 zillion) ZFS filesystems.

Also, add a print statement in the unmount code that Hussam added so
that we can see how often this (still?) happens.

Many LV segments fail on "dmsetup remove" because they are still mounted. Need…

See merge request !28

Many LV segments fail on "dmsetup remove" because they are still mounted. Need to unmount them before the remove operation.

If a background resource allocation fails, we put the lease in the "failed"
state instead of destroying it. There were some ripple effects, specifically,
the lease_daemon now checks for "failed" leases and send messages to us at
the same frequency as for "unapproved" leases. The correct response here is
almost certainly to destroy the lease, though you can put it back in the
"unapproved" state (via modlease) and try to approve it to see what happened.

Also add background mode to approvelease since it can do time consuming
resource allocation.

Nit: cleanup logfiles used in backgroud operation.

Make sure the FS create actually fails before you cleanup and remove
the new volume...

seems to work for both.

something for my stack of tasks.

for user.

We want it processed before the default file so that we can stop
Emulab (local5) messages from going into "syslog".

 * A failure to allocate resources results in the embryonic dataset being
   destroyed. Previously, we would just leave it "unapproved". This means
   that, for a background lease creation, either the lease will eventually
   wind up in the "valid" state (success) or it will disappear (failure).

 * If creation fails early due to a policy violation, we exit with the
   value 2. Other early (non-background) exits will be 1 or -1 (255).
   This allows the a calling script to easily differentiate policy
   violations (for which the user might want to appeal via -U) from other
   more serious failures.

usage in the project for the reserved node type. Work in progress.

allow approval, but still allowed to send email and deny project.

that we do not want to deactivate or change the "end" time of the
reservation, in case we want to abort self destruction. Insert
Star Trek reference here:

experiments are recent too!

determine if reservations are being used. Work in progress.

Really, it is TMHS (Too Much Horizontal Space).
80 column output rules! Welcome to the 1950s.

Not super well testbed yet, but getting there.