GitLab

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.

what they should be from the siteids on the nodes.

name attribute.

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.

UI to not use modals.

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

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

a routeable IP, then use "basic" instead of closed so that ssh is
allowed in (on the alternate port of course).

of the rspec.

and libraries. Rough, needs plenty more work.