So, one reason the fast RPC path is fast cause we do not normally
operate with credentials, but with reservations we have to since we want
the reservation creator to be a real user and of course the project has
to exist. Need credentials for that. But when an admin is editing or
creating a reservation in another project, we need the admin user to
exist too, and we might need the project to be created. That requires
different credentials. So in an attempt to deal more generally with the
admin problem, export an entrypoint to create a user (the admin user)
before trying to create a reservation. Not sure this is the best way to
go but its one way to go.

In general, I think we need a more explicit user/project management API
for the Portal. Needs more thought.

user (read: Mike) so the user (Uh, Mike) does not get all wigged out
about not being able to use the nodes he (Mike?) want to use.

1. Fix up multi architecture code wrt auxtypes (say, pvcm). I was
   failing to treat "d710-vm" as a node with a specified type, and so
   were doing multiple mapper runs with different architectures. This is
   cause an auxtype is not really a first class type object, but it is
   now, enough to recognize it as such.

   Aside; vtypes are still a potential problem, need to give this more
   thought.

2. Use the reservation MaxSwapInMap() to determine if the request is
   asking for more nodes of a specific type then allowed; do not bother
   to run assign, bail right away. We can do this we now track how many
   nodes of a specific type have been requested, for the multi
   architecture stuff. So might as well put to another good use.
   This close issue #236.

3. Add reservation system information dump to resinfo.log for post
   mortem debugging.

have been machine converted from rspecs to geni-lib scripts.

This closes issue #222.

need to call exports_setup.

and groups on the geni path. This seems to happen more then I thought it
might.

User lockdown is as before, user can override that on the terminate
page. Admin lockdown is like Classic lockdown; the flag must be cleared
before the experiment can be terminated, there is no override on the
termination page.

UI changes on the status and admin extend page for the additional
flag (instead of a single lockdown, there are now two).

in UpdateImageStatus().

Also remove use of local5.* in syslog.conf so we can turn around
and re-add it!

Make sure console is properly configured for "sio1" so we can see it.

Kill off left over QEMU processes that occur in Xen 4.6 (due to their
use of "-no-shutdown" on the qemu command line).

when checking the debug value throughout the file.

    Bump credential idx to a full int, we just overflowed the mediumint
    on the Mothership.

This should not even be used any more, but until we have a chance to
confirm that, I have increased the range (and reduced the ports-per-range).
Since we now have over 100 active vnodes, we hit this limit!

The event scheduler loves to send events to itself and will break badly
if we ever change pubsubd (back) to not forward notifications to the
sender. This was the start of an attempt to short circuit the path by
which such events are delivered, both sending an event (for any other
interested nodes) and invoking the event callback directly (for us).
Likely not a good idea...

This one doesn't seem to have bitten us yet, but maybe it could.

The code used $end (computed autoswap time) instead of $endtime.  This
could cause underestimation of the length of time an experiment could
occupy nodes in cases where $endtime came later (which can happen in
GENI slices).