GitLab

lib subdir.

It only makes sense to run this at the clearinghouse.  It brings both
the local CA bundle and the bundle to be distributed to federates up
to date with respect to .../etc/genicacerts/*.pem and
.../etc/extracerts.bundle.

Any time the sources are changed, just run this script.  The local bundle is
ready immediately.  The federates will fetch the new version as they get
around to it.

should be the last argument, not the first. Confusing at best, broken
at worse.

Passing unconverted port string to RecordVLanModification; fixed.

If doMakeVlan(), if source and target are the same, do not delete the
ports from the source.

Allows the firewall setup code to be rerun.

the command line, when trying to order vlans by their dependency
links. 2) Add backward compatability with older snmpit command line
arguments.

table when picking the vlan tags. This require some reorg of that
section. 2) Some changes to the schema.

Updated example stitching request.

protogeni response.

reused in the topo (since most of our nodes can bridge two links), and
the ticket release was confused by that. This is the actual problem
that was encountered when tarfiles setup was failing; nothing to to do
with tarfiles, just the ticket release.

slivers can store/return error info to the user in sliverstatus.
This include the top level aggregate for a slice.

Added an 'error' attribute to the top level sliverstatus return hash,
to return this error.

Put start/restart sliver into the background so that it runs async,
just like it does when invoked from the CreateSliver() path. This is
because start/restart can take an arbitrary length of time, and having
the RPC sit in hold for that long is not an ideal interface. Users can
get all the info they need from the sliverstatus call.

Change Start/Restart so that all of the error message we were printing
to STDERR for the mail log, also go back to the user in the toplevel
error for the aggregate.

top level error info for later return. This allows non-node slivers to
return useful info in sliverstatus.

Since the interface names in the solution do not match the interface names on the request, we can't correlate them anyhow. Reverting to just v1 processing until we move libvtop to outputting rspecv2

Testing this tool also allowed me to find some typos in the delaylink example.

Also, reordered initialization of counters so it is the same as the order of the access methods for easier verification that everything gets initialized.

manifest updated with new interfaces in the nodes section.

What you cannot do, is change the endpoint of an existing link. For
example, if link0 goes from A to B, you cannot submit an rspec that
changes link0 to go from A to C. What you *can* do is submit an rspec
that removes link0 and adds link1 from A to C. This was not working
before, for a number of reasons having to do with the manifest
generation, but those are all fixed now.

This reverts commit e9ed9bcd.
Apparently the mapper.in part breaks something.

We don't officially support this anymore, but the problems were minor:

mapper: use HAVE_XERCES to determine whether rspec v2 output is supported.
The symptom is that swapin will fail due to passing the unsupported 'f'
option to assign, but it just isn't going to work anyway without an XML
parser installed.

rc.mkelab: fix a broken version check that would lead to inner-boss
setup failure on a pre-FreeBSD7 machine.