1. 15 Mar, 2015 1 commit
  2. 13 Mar, 2015 3 commits
    • Jonathon Duerig's avatar
    • Gary Wong's avatar
      7a76cc98
    • Leigh B Stoller's avatar
      Checkpoint various changes. · 0d09773b
      Leigh B Stoller authored
      * Various UI tweaks for profile versioning.
      
      * Roll out profile versioning for all users.
      
      * Disable/Hide publishing for now.
      
      * Move profile/version URLs into a modal that is invoked by a new Share
        button, that explains things a little better.
      
      * Unify profile permissions between APT/Cloudlab. Users now see just two
        choices; project or anyone, where anyone includes guest users in the APT
        interface, for now.
      
      * Get rid of "List on the front page" checkbox, all public profiles will be
        listed, but red-dot can still set that bit.
      
      * Return the publicURL dynamically in the status blob, and set/show the
        sliver info button as soon as we get it.
      
      * Console password support; if the aggregate returns the console password,
        add an item to the context menu to show it.
      
      * Other stuff.
      0d09773b
  3. 12 Mar, 2015 1 commit
  4. 11 Mar, 2015 2 commits
  5. 10 Mar, 2015 5 commits
  6. 05 Mar, 2015 1 commit
  7. 25 Feb, 2015 1 commit
  8. 04 Feb, 2015 3 commits
  9. 31 Jan, 2015 1 commit
  10. 28 Jan, 2015 1 commit
    • Mike Hibler's avatar
      Implement "plan 1" for dataset sharing: "ephemeral RO snapshots". · 7aefdaa1
      Mike Hibler authored
      You can now simultaneously RW and RO map a dataset because all the RO
      mappings use copies (clones) of a snapshot. Only a single RW mapping
      of course.
      
      When the RW mapping swaps out it automatically creates a new snapshot.
      So there is currently no user control over when a version of the dataset
      is "published", it just happens everytime you swapout an experiment with
      a RW mapping.
      
      A new RW mapping does not affect current RO mappings of course as they
      continue to use whatever snapshot they were created with. New RO mappings
      with get the most recent snapshot, which we currently track in the DB via
      the per-lease attribute "last_snapshot".
      
      You can also now declare a lease to be "exclusive use" by setting the
      "exclusive_use" lease attribute (via modlease). This means that it follows
      the old semantics of only one mapping at a time, whether it be RO or RW.
      This is an alternative to the "simultaneous_ro_datasets" sitevar which
      enforces the old behavior globally. Primarily, I put this attribute in to
      prevent an unexpected failure in the snapshot/clone path from wreaking
      havoc over time. I don't know if there is any value in exposing this to
      the user.
      7aefdaa1
  11. 27 Jan, 2015 2 commits
  12. 26 Jan, 2015 3 commits
  13. 22 Jan, 2015 3 commits
  14. 18 Jan, 2015 1 commit
    • Mike Hibler's avatar
      Change tiplines urlstamp to be an expiration time for the urlhash. · a40fb744
      Mike Hibler authored
      Previously it was the creation stamp for the hash. By making it the
      expiration time, we can do different times for different nodes.
      
      Note that there is no serious compatibility issue with re-purposing
      the DB field. It is almost always zero (since they are only valid
      for 5 minutes) and if it isn't zero when the new code is installed,
      the hash will just immediately become invalid. So what? Big deal!
      a40fb744
  15. 12 Jan, 2015 3 commits
  16. 09 Jan, 2015 2 commits
  17. 08 Jan, 2015 2 commits
    • Kirk Webb's avatar
      Backend support for simultaneous read-only dataset access. · 9b6e1a59
      Kirk Webb authored
      Any number of users/experiments can mount a given dataset (given that
      they have permission) in read-only mode.  Attempts to mount RW will
      fail if the dataset is currently in use.  Attempts to mount RO while
      the dataset is in use RW are also prohibited.
      
      Under the hood, iSCSI lease exports (targets) are now managed per-lease
      instead of per-experiment.  The set of authorized initiators (based
      on network) is manipulated as consumers come and go.  When the last
      consumer goes, the export is torn down. Likewise, if there are no
      current consumers, a new consumer will cause an iSCSI export to be
      created for the lease.
      
      Also included in this commit is a small tweak to implicit lease permissions.
      9b6e1a59
    • Leigh B Stoller's avatar
      55388928
  18. 03 Jan, 2015 1 commit
  19. 29 Dec, 2014 1 commit
  20. 14 Dec, 2014 2 commits
  21. 06 Dec, 2014 1 commit