GitLab

Per-repository 'keywords' may now be configured by setting the
hooks.gitmail.keyword option.  One X-Git-Repo-Keyword header is added
to commit mails for each keyword specified.

The primary use case for this is to configure related repositories
with the same keyword(s), so that commit mails for those repositories
can be filtered with a single rule rather than one for each
repository.

use this path when setting up the vlan, instead of recomputing the set
of trunks that are need. Assign does a much better job of this, so
throwing the info away is bad.

But, if there is no switch path, we still have to be careful cause the
switch infrastructure might have loops, and the existing algorithm did
not take that into account. And in fact, Utah has loops and this was
causing grief. I added a simple spanning tree function (Prim's Greedy)
to calculate a loop free set of trunks.

An added complication is if the vlans are modified on the command
line, and the there is a switch path in the DB. In this case we have
to throw that away, and revert to dumb loop free calculation.

Note that we also have to store the switch path in the vlans table,
since for swapmod/synctables, we need to know how to undo stale vlans
(which are no longer in the lans table).

actual switch details.

lans.

loopfree path from a set of trunk links.

Silly place for this, but I need it in libvtop.

table, and is a lan attribute).

will be subsumed by the NewMapper feature when that is exported to all
sites, which will happen soon.

context instead.

flag that says to reregister certs and resources. This is used from an
update script (21) that updates the certificates with a new URL that
uses http on a different port then 443.

variables for easier config in apache and protgeni code. The port
defaults to 12369, RPCNAME to $WWWHOST, and the URL is derived from
those two.

running on a different port. This will solve the problem with ssl
renegotiation since at some point, we can turn that off (remove the
protogeni stuff) from the main https virtual server. This one runs on
a different port, and can in fact be a distinct IP addresse, but that
is not really necessary.

Instead, lets use the created field, and age out authorities and
components if they get too stale. This will help to keep sites from
getting too far out of date with respect to the clearinghouse.

Also, the URL for the certificates now comes from configure: PROTOGENI_URL

certificate common name. Emulab will now put the full url (with port)
into user certificates, so that we can the RPC server on any node or
port we want.

not put in any of the req_altname stuff.