GitLab

DeleteSliver had been calling StopSliver then DeleteSlice,  but the
recommentation from Utah is to skip that and just call
CMV2::DeleteSlice.

This should help to explain exactly what has happened when the slice
was renewed but for some reason the sliver was not.

Not much more to say. Shutdown was stubbed as unsupported and now it
has been implemented as a pass through to CMV2::Shutdown.

Compression is now done in one place and in one way rather than two
different places and two different ways. Added handling of an
additional error case in the second call to resolve if a slice_urn is
present. Improved comments as well.

The AM ListResources implementation had punted on the path that
included a slice_urn in the options. This is now implemented per the
GENI AM API spec. It's still a bit brittle, but working.

Need to set the magic debug sysctl on geom to allow changing active disk.

(this time for the urn). Also change the protoype to allow an error to
be returned.

(this time for the urn). Also change the protoype to allow an error to
be returned.

vlans.

internally, as the primary key in the tables, but the CM/SA APIs no
longer use them. The CH still accepts them for now. We can probably
stop putting them into manifests and advertisements at this point as
well. 

For slivers, stop using the uuid of the node as the uuid of the sliver
itself; generate a new one. As above, this is cause the uuid is the
primary key in the table, but the URN is what we use for lookups,
etc.

not grant credentials to users.

In fact, it might return an empty string if there is no data available.
Thus testing trim(fgets(...))=='' is NOT a good way to test for a
blank line.  Fixed this by accounting for the no data case.

This bug caused the header of the HTTP response of an xmlrpc call to
become part of the body, and thus creating invalid xml, which in turn
caused xmlrpc_decode_request to fail.  The end result was that a WEB
ERROR REPORT was created and no useful info was returned to the user
when an NS file took a long time to parse.

backwards compatible with old SAs and CMs until new code makes it
out to everyone. So the CM now does a version check at the target SA,
and if an old version 1, use the bogus self signed cred. If the SA is
version 1.01, send a proper sliver credential.

In the SA, accept older bogus credential for now, but start accepting
the new sliver credential, and apply more stringent checks.

The awk implementation used in Busybox (for the Linux MFS) was giving
strange results when converting our dotted-quad IP address and mask to
a base-10 decimal integer.  It looks like it has something to do with
the sign bit in one of the intermediate values, and I don't really
want to debug it right now.

The kernel is perfectly happy with hex numbers for integer values when
writing to /proc/sys/* (directly or via sysctl), so we now simply pass
the dotted-quad address to awk (with '.' as the field separator) and
do a simple printf to get the result we want.

We no longer need to call sed either, since POSIX "remove matching
prefix/suffix" syntax is supported by ash in the MFS.

adding them to the local SA DB).

Conflicts:
	tbsetup/snmpit.in