shared hosts. This is required for OpenVZ but not for XEN, so this does
mean that when using ZFS, shared OpenVZ hosts are not supported. Not likely
to be a problem.

link on the showuser page for local admins (Mike) to get some
old pages.

creating the initial ZFS volumes, that is described in Mike's notes
file on how to setup ZFS on ops. But once that is done, the runtime
supports takes care of creating volumes for users and projects/groups.
New configure variables, with defaults to:

	WITHZFS=0
	ZFS_ROOT=z
	ZFS_QUOTA_USER="1G"
	ZFS_QUOTA_PROJECT="100G"
	ZFS_QUOTA_GROUP="10G"

error in FreeBSD 10.

This used to be not required as p5-Crypt-X509 had a dependency for it,
and emulab-protogeni depended on p5-Crypt-X509. But, for a brief shining
moment, the FreeBSD port was broken and guess when I happened to take a
shapshot of the ports?

the event list to be a list of eight items, but we were sending back only
seven for the static events. Up until FreeBSD 10 this did not seem to be a
problem, but under 10, core dump!

in freebsd10 is not the default.

Otherwise, the shell will be killed by reboot leading to init restarting it.
Probably does not do any harm other than printing a confusing error message,
but I have seen cases of minorly corrupt root FSes in BSD images.

login modal, must use the original direct geni-login.php page
until we go live.

authenticate Geni users to CloudLab (who do not have Emulab accounts).
CloudLab users must have an account to do anything (unlike APT which allows
guest users). But instead of requiring them to go through the Emulab
account creation (high bar), let then use their Geni credentials to prove
who they are. We then build a local account for that new user, and save off
the speaksfor credential so that we can act on their behalf when talking to
the backend clusters (and their MA to get their ssh keys).

These users do not have a local account password, so they cannot log into
the web interface using the Emulab login page, nor do they have a shell on
ops.

Once authenticated, we put the appropriate cookies into the browser via
javascript, so they can use the Cloud (okay, APT) web interface (they
appear logged in).

I make use of the nonlocal_id field of the users table, which was not being
used for anything else. Officially, these are "nonlocal" users in the code
(IsNonLocal()).

When a nonlocal user instantiates a profile, we use their speaksfor
credential to ask their home MA for their ssh keys, which we then store in
the DB, and then provide to the aggregate via the CreateSliver call.
Note that no provision has been made for users who edit their profile and
add keys; I am not currently expecting these users to stumble into the web
interface (yet).

after mysqld starts, and the socket is not there for a few seconds.

we figure out what deletion with deltas means. Still a problem for
users, but at the moment we have not enabled provenance for mere
users.

Aside: Need to change purge so that we delete all image files
(file for each version). Forgot to do that.

(cloud/apt).

cloudlab/aptlab generated projects.

a text field that says emulab,cloudlab, or aptlab.

* autoswap time and idleswap time defaults are inherited from the
  associated sitevars.

 - "general/autoswap_threshold", and "idle/threshold", respectively

* autoswap default state follows associated sitevar ("general/autoswap_mode").

* Any user-requested autoswap duration is checked against the
  "general/autoswap_ max" sitevar.

 - Admins can override.

* Any user-requested idleswap duration is checked against the "idle/threshold"
  sitevar.

 - Admins can override.

* Disabling swapping (-S option) is prohibited, except by admins.

* Removed all special-case checks for requests coming via the XMLRPC server.

Handy.

The protocol now works perfectly.

TODO: Figure out why certificate parsing is failing