1. 01 Dec, 2015 1 commit
    • Leigh B Stoller's avatar
      Add support for cancelation; stopping an experiment setup early, instead of · 32c3d934
      Leigh B Stoller authored
      waiting till it finished setting up (or fails). This is really nice when a
      1000 node experiment has gone awry and it is pointless to wait for it to
      finish. When we do this, we mark the instance as canceled in the DB, and
      then wait for create_instance() to notice it. When it does, it stops
      waiting and invokes terminate with a new cancel option at the backend.
      32c3d934
  2. 30 Nov, 2015 1 commit
  3. 02 Nov, 2015 1 commit
    • Leigh B Stoller's avatar
      Add password block decryption and expansion in the instructions panel. · d7d3800a
      Leigh B Stoller authored
      Given a password element in the rspec:
      
      	<emulab:password name='foo'></password>
      
      which the portal has converted to an encrypted secret, when that experiment
      is later shown (the status page), ask the server to decrypt the block, and
      then replace the string "{password-foo}" in the instructions with the
      actual password.
      
      Need to generalize this a bit more, for arbitrary encryption blocks, when
      we have those.
      d7d3800a
  4. 28 Oct, 2015 1 commit
  5. 22 Oct, 2015 1 commit
  6. 21 Oct, 2015 1 commit
  7. 19 Oct, 2015 1 commit
  8. 03 Sep, 2015 1 commit
  9. 11 Aug, 2015 2 commits
  10. 27 Jul, 2015 1 commit
  11. 11 Jul, 2015 1 commit
    • Leigh B Stoller's avatar
      Improvements to admin extend: · 7564c408
      Leigh B Stoller authored
      1. Provide text box to add to email message that is sent to user.
      
      2. Track outstanding admin required requests, add a Deny button for those.
      
      3. Add option to experiment listing for admins, to see outstanding admin
         required approval.
      7564c408
  12. 10 Jul, 2015 1 commit
  13. 30 Jun, 2015 1 commit
  14. 19 Jun, 2015 1 commit
    • Leigh B Stoller's avatar
      New support for importing image backed datasets from other clusters. This · 613d90dd
      Leigh B Stoller authored
      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.
      613d90dd
  15. 10 Jun, 2015 1 commit
  16. 09 Jun, 2015 1 commit
  17. 28 May, 2015 1 commit
  18. 26 May, 2015 1 commit
  19. 22 May, 2015 1 commit
  20. 15 May, 2015 1 commit
  21. 01 May, 2015 2 commits
  22. 30 Apr, 2015 1 commit
  23. 27 Apr, 2015 2 commits
  24. 21 Apr, 2015 2 commits
  25. 15 Apr, 2015 1 commit
  26. 14 Apr, 2015 2 commits
  27. 13 Apr, 2015 1 commit
  28. 10 Apr, 2015 1 commit
  29. 04 Apr, 2015 1 commit
  30. 31 Mar, 2015 1 commit
  31. 09 Mar, 2015 1 commit
  32. 05 Mar, 2015 1 commit
  33. 02 Mar, 2015 1 commit
  34. 27 Jan, 2015 1 commit
    • Leigh B Stoller's avatar
      Two co-mingled sets of changes: · 85cb063b
      Leigh B Stoller authored
      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.
      85cb063b
  35. 15 Dec, 2014 1 commit