GitLab

The only reason it is here, is cause it uses gnuplot.

We now ask the portal for a the user's project membership list, and if the
user is not a member of any (unexpired) projects, we do not allow them to
create experiments (or much of anything else) in the Cloud Portal. I did
this by setting the local holding project trust to "user" and setting the
webonly bit in the users table. The user can use the picker to see public
profiles, but the create button tells them no dice, go join a project at
the GPO portal.

We make the project check each time the user logs in via the trusted
signer.

   <node>
     <emulab:moonshot_chassis chassis="4" />
   </node>

a credential to return the user, and we require that credential on
subsequent attempts to link to that shared vlan. It is assumed that the
caller knows how to delegate the credential if necessary.

Yes, out of the blue and off the wall. But I got tired of trying to
guess what we had Linux and FreeBSD use. I was surprised to discover
that we were using UDP on Linux (which caused Clemson CloudLab to fail
because they have jumbo frames enabled on their control net switches
but ops had the MTU set to 1500).

Anyway, here it is. The default setting is UDP for backward compat.
We should probably set it to TCP nowadays. There is also an 'osdefault'
setting which says use the default setting on the client OS.

at the next extension, to avoid user aggravation. Also show the reason on
the termination modal if the experiment has been locked down.

parameterized profile. Note that we don't use this path much, but
we might in the future.

account, do not create a new shadow account.

experiments. Lockdown is implemented at the portal and at the backend
cluster (ignore by cm and sa daemons). At present, the only policy is
that admin extensions longer then 14 days, set the lockdown.

job of limiting overuse of shared nodes.

error in creating it.

It's clear from the various Force10 switches and firmware versions
that we've seen now that the vlan membership PortSet bit
vector size can vary widely.  This variation even happens between
different versions of firmware on the same switch!  So, now we
detect this dynamically when the backend force10 snmpit object is
instantiated (in readifIndex()).

Required updates to Makefile-linux.sa makefiles which are used
in Ryan's build environment.