since those vlans might not be consistent in the DB. In general, we
need to be looking at only actual experiments with vlans on the
Experiment stack, but this change fixes the problem with ptopgen
bailing early with an error.

we had 768K of real memory left, but we wanted 1024 for a VM.

both sides of the wires table for external network nodes.

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

Previously ptopgen was ignoring permissions granted to individual users
for OS access.  This commit also updates subos enumeration (previously
ptopgen was not looking at the permissions table at all for suboses).

   <rspec_routable_addresses
      xmlns="http://www.protogeni.net/resources/rspec/ext/emulab/1"
      configured='XXX' available='YYY' />

will correct error (no_bandwidth instead of no_connect).

Quite simple actually. In ptopgen we add all persistent stores, which
are identified by having a non-zero lease_idx. To ensure they are only
matched up with the correct virt_blockstore, we add a feature "bs-lease-NN"
where NN is the unique lease index with weight 1.0.

In vtopgen, when a request is made to map a persistent store, we first
verify that the experiment pid matches that of the blockstore's lease
(this is a fer-now simple check which is actually redundant as we make
this check in the parser too) and ensure that the blockstore is not already
mapped (indicated by the blockstore_state entry having size==0) and then
we emit an entry with desire "bs-lease-NN" and weight 1.0.

Most of the file changes were actually to get the "preassign" flag to
vtopgen forwarded into the various libvtop modules so that I can check it
and not perform the permission/size check if it is set.

Also, multiple ports on the same contact node will now be consolidated into one stitch:node tag with multiple stitch:port children.

On shared nodes, look for the 'xen-host' or 'openvz-host' osfeatures when
determining sliver types.