GitLab

1. Do not pass -u option (update mode) to the mapper call in GetTicket, if
   not actually an update. This will now cause the mapper to pass the -F
   option to assign, so that fixnode (by the user rspec) will not override
   normal constraint checking.

2. MAINSITE: Add d820-explicit desire so we can actually use the shared
   node pool.

3. Add checks for out of memory errors from assign, and pass that back for
   the caller.

Add a CheckMonitor() method to see if the monitor is running, and if not
clear the DB. This is one cause of slices not getting terminated when Utah
Cloudlab crashes.

which affords a bit more flexibility in the link element.

is just like importing images (by using a url instead of a urn), which
makes sense since image backed datasets are just images with a flag set.

Key differences:

1. You cannot snapshot a new version of the dataset on a cluster it has
   been imported to. The snapshot has to be done where the dataset was
   created initially. This is slightly inconvenient and will perhaps
   confuse users, but it is far less confusing that then datasets getting
   out of sync.

2. No image versioning of datasets. We can add that later if we want to.

1. A trivial change in GeniCM; only look at the first two interfaces in the
   link if it references an external node. We already depend on the fact
   that the first two interfaces are in the same order as the two stitch
   points in the stitching section, so as long as we ignore external nodes
   after the second interface, setting up the virtual state for a lan works
   just peachy.

2. libvtop_test: a bit less trivial, mostly cause of vlan tag pre
   reservation when stitching. When we encapsulate a lan we build another
   lans table entry that is linked. There is no need to do this when the
   encapsulation is vlan, and in fact I had changed links a long time ago
   to not do this, for the exact same reason. Lans are little bit more
   complicated but I think I got it.

with tag fragmentation which can causes us to not find any free tags
even there are plenty. Add some debugging when we do fail to find
a free tag.

clusters.

but there is already a geni_users account.

rather then "persistent";

   <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.

undefined variable error.

Fix bug in Jacks Editor wrapper on cancel

  <rs:site_info
      xmlns:rs="http://www.protogeni.net/resources/rspec/ext/site-info/1">
    <rs:location
        country="US" latitude="40.768652" longitude="-111.84581"/>
  </rs:site_info>

Eventually replace per-node info if its just duplicate, but for now leave
the old location in place.

1) Implement the latest dataset read/write access settings from frontend to
   backend. Also updates for simultaneous read-only usage.

2) New configure options: PROTOGENI_LOCALUSER and PROTOGENI_GENIWEBLOGIN.

   The first changes the way that projects and users are treated at the
   CM. When set, we create real accounts (marked as nonlocal) for users and
   also create real projects (also marked as nonlocal). Users are added to
   those projects according to their credentials. The underlying experiment
   is thus owned by the user and in the project, although all the work is
   still done by the geniuser pseudo user. The advantage of this approach
   is that we can use standard emulab access checks to control access to
   objects like datasets. Maybe images too at some point.

   NOTE: Users are not removed from projects once they are added; we are
   going to need to deal with this, perhaps by adding an expiration stamp
   to the groups_membership tables, and using the credential expiration to
   mark it.

   The second new configure option turns on the web login via the geni
   trusted signer. So, if I create a sliver on a backend cluster when both
   options are set, I can use the trusted signer to log into my newly
   created account on the cluster, and see it (via the emulab classic web
   interface).

   All this is in flux, might end up being a bogus approach in the end.

I needed more info back about the set of reservations referencing a
particular lease. Existing code updated to compensate.

Also includes some bug fixes.

    <emulab:failure_action action="nonfatal"/>

all users. Cloudlab added to the list, but not exposed except to
admins and studly users.

Project leases are now per-group, so we build a sub authority certificate
for a remote dataset so that on the remote side, it is created inside the
group named by the project on the local side.

Many bug fixes.

e.G. the following assign violations gave just 'Not enough bandwdith' as the 0 always matched.
Now we match with any number 1-9

   BEST SCORE:  50.5 in 0 iters and 0.008631 seconds
  unassigned:  0
  pnode_load:  26
  no_connect:  0
  link_users:  0
  bandwidth:   0
  desires:     0
  vclass:      0
  delay:       0
  trivial mix: 0
  subnodes:    0
  max_types:   0
  endpoints:   0