It was returning info for blockstores of the same name in different
experiments...oops!

Same as ubuntu11 right now.

Disable deltas for all system images. This is temporary while we test.

* Add a uuid to the profile itself. So now we have a uuid for each specific
  version, and a uuid that points to the profile as a whole.

* On the manage page, move the URL to the left hand panel, and add a second
  URL. One is the URL of the specific version, and the other is a URL to
  the entire profile. Add popovers to explain the difference between.

* On the instantiate page, when you use this URL, we instantiate the most
  recently published version of the profile.

* Add a bit of verbiage to the publish modal.

(all versions).

fields.

and less scary (to Mike).

Tweaked uritemplate.js to allow '-' character in identifiers which is technically illegal according to the RFC. Might need to revisit this later.

The only kind of key allowed so far is of the form 'host-clientid' where client id is a node in the rspec.

to being a rack, it was just to do the initial install.

create_image runs as the invoking user but the frisbee uploader may
run as a different user (the creator of the image). If the file is
not group writable, we will get a permission denied error in the
uploader.

For externally managed experiments, don't consider the current state of
the experiment.  If a node is reserved to the experiment, period, then its
entry needs to be disabled in dhcp.  Otherwise the next time dhcp_makeconf
runs, any already active externally managed experiments will revert to Emulab
dhcp.

Don't look it up for each and every node...

Also quiet down the EmulabFeatures library where we are using it
to detect external management.  Too many "checking for feature ..."
messages.

Leaving the node entries in the dhcpd.conf file, but setting them to
be ignored is better.  Cuts out "no free leases" log messages and is
less confusing for people looking through the config file.

Sprinkle a few comments around in dhcpd_makeconf

In support of the collaboration effort with CHPC, I've added a check
and actions for a new feature, ExternalNodeManagment.  When swapping in,
the swapper, group, and experiment are checked for the feature.  Since
there doesn't appear to be a way to ask for an experiment feature in the
parser, I'm punting for now and just letting the experiment inherit this
feature from the user and/or project/group.

The effect of this feature is that nodes will be omitted from the
dhcpd.conf file when allocated to a marked experiment, and put back
in when freed from that experiment.

We will also use this feature to force nodes to reboot even when they
are in PXEWAIT during the OS setup phase.  Ultimately the point is for
something else to take over the boot process and manage the experiment's
nodes for the duration of the experiment.