1. 08 Jan, 2015 1 commit
    • 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
  2. 05 Jan, 2015 1 commit
    • Kirk Webb's avatar
      Enforce permissions for dataset leases at mapping time. · bedcb609
      Kirk Webb authored
      * Swapper must have appropriate level of access (RO or RW).
      * If RO is requested, dataset must not be in use RW.
      * If RW is requested, dataset must not be in use at all.
      
      Also relaxed the checks in the parser; it was considering dynamic lease
      state, which isn't the right thing to do there.
      bedcb609
  3. 29 Dec, 2014 2 commits
  4. 22 Dec, 2014 4 commits
  5. 21 Dec, 2014 1 commit
  6. 19 Dec, 2014 2 commits
  7. 18 Dec, 2014 1 commit
  8. 17 Dec, 2014 2 commits
  9. 16 Dec, 2014 4 commits
  10. 15 Dec, 2014 11 commits
  11. 14 Dec, 2014 8 commits
  12. 12 Dec, 2014 3 commits
    • Mike Hibler's avatar
      Double the timeout period for waiting for the master server to reply. · a78a427e
      Mike Hibler authored
      This is a "temporary" hack to get around the single-threaded nature of
      the master server. That in itself is not the killer, it is that it
      sleeps for 2 seconds after it spawns a child process (frisbeed, frisbee
      or uploader). So if three images are requested simultaneously by a handful
      of clients, then it will take 6 seconds to get the frisbeed processes
      started, exceeding the 5 second timeout in the clients. So other clients
      in the queue after the three clients that are starting images will timeout
      before the master server handles them.
      a78a427e
    • Mike Hibler's avatar
      Add a "failstop" command line argument for frisbee MFS. · a271d365
      Mike Hibler authored
      If specified on the kernel command line in the pxelinux.cfg config,
      the init script will drop to a shell prompt when frisbee fails.
      With failstop off, it will instead report via "tmcc bootlog", wait
      a couple of seconds, and then reboot in order to try again.
      a271d365
    • Leigh B Stoller's avatar