GitLab

created (on the command line at the remote cluster).

to user; especially important for Portal users, since there is no
interface to regenerate it.

image descriptor.

the road. And it is a causing an odd perl error.

VMs. These are not internal nodes (vhosts) but actual nodes in the
topology to which VMs have been assigned (instantiate_on).

I have to search the DOM instead.

Support FreeBSD 10.3. We will need to be moving to this before long
as 10.2 EOLs in two days.

Support setup of "Emulab-aware" ZFS use in install scripts. Note that
the core support code was already done (WITHZFS, WITHAMD). Mostly this
involves changes to setup either amd (WITHAMD==1) or autofs (WITHAMD==0)
on the boss node and to NOT add mounts of /{users,groups,proj} to
/etc/fstab. We still need to add a section to the install documentation
about setting up a zpool for Emulab to use. There was also a fix to the
firstuser script which did not do the account setup correctly.

Support setup of ZFS in elabinelab. The elabinelab attributes CONFIG_ZFS
and CONFIG_AUTOFS are used to convey intent here. Currently they can only
be used in an "ops+fs" config (e.g., the standard boss and ops config,
NOT the seperate fs node config). It should work with either the physical
or virtual node setups:

* For the physical node setup, we actually use local blockstores ...

profile source code, so that the Create button goes active.

remove are run on ops via the proxy script. Other smaller operations
like getting the source, logs, commit info are currently run on boss via
NFS to /usr/testbed/opsdir/repositories, which are one per profile.
Lots of work still to do on optimizing repositories.

does not result in immediate termination. Instead we dump the params
defs to a different file now, and continue on to spit the rspec to the
output file. This complicates returning back to ops though, since now we
have two file. So I elected to do a cheesy tar pack/unpack on the return
trip.

1. We do not need to save the param definitions; we have the script.

2. We do want to save the refspec in the history, even though we have
   the hash. Easier to see what is going on.

number, that is how the new OSImage code knows its a generic.

Initially frozen elabinelab users don't have boss/ops password file entries.
So don't try to modify those accounts.

a class (say, pc or pcvm) was wrong.

A recent commit to 10-STABLE caught my attention since it was a speed
up of the 'pw' command. Probably not a huge issue in our environment,
but I incorporated it into our patch.

elabinelab creation will work.

As of 5.5.53 it defaults to not allowing 'INTO OUTFILE' which we use in
a number of places (e.g., to save experiment state in /usr/testbed/expwork).