GitLab

Add new table experiment_keys to hold RSA priv/pub key pair and an SSH
public key derived from the private key.

Initialized when experiment is first created, I have not done anything
to set the keys for existing experiments yet.

But for testing, you can do this:

	use lib "/usr/testbed/lib";
	use Experiment;

	my $experiment = Experiment->Lookup("testbed", "layers");
	$experiment->GenerateKeys();

* Fix the logging that had been messed up for while; the logfile object
  was not defined in the children, needed a little reorg.

* Add changes needed for SecureImageDownload(), which is a little
  messier with fcgid since we have to stream the image back to apache
  which means we need to reconnect the fcgid handler.

* Add the CH module, seems to work fine.

* Wrap the calls to cluster-wrapper.pl so that we can set an ENV
  variable indicating which module is being served, and then put this
  in the proc title; its very annoying that perl (sometime?) messes the
  with the proc title without permission from me, so I don't know what
  each server is serving since the command line options are gone.

* Some tweaks to the apache config file.

Note hat this is not running live yet, still just in my devel tree.

invoked (as for long running fcgid daemon).

when invoked (as for long running fcgid daemon).

This closes issue #314.

upon to handle pre-reserves and reservations in a reasonable manner.

1) Include URN of pre-reserve project so that it can be mapped back to
   local project at the caller.

2) Return freecount info as determined by Reservation->Freecount() so we
   can show adjusted numbers.

We were previously acknowledging the KnowOps award.

"CNS-" is not part of the award number.

The previous value was based on the University account number.

Also, default to FreeBSD 10.x when possible.

* Make user privs work across remote clusters (including stitching). I
  took a severe shortcut on this; I do not expect the Cloudlab portal
  will ever talk to anything but an Emulab based aggregate, so I just
  added the priv indicator to the user keys array we send over. If I am
  ever proved wrong on this, I will come out of retirement and fix
  it (for a nominal fee of course).

* Do not show the root password for the console to users with user
  privs.

* Make sure users with user privs cannot start experiments.

* Do show the user trust values on the user dashboard membership tab.

* Update tmcd to use the new privs slot in the nonlocal_user_accounts
  table.

This closes issue #309.

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!