1. 26 Sep, 2016 1 commit
  2. 20 Sep, 2016 1 commit
    • Mike Hibler's avatar
      Initial support for ephemeral RW clones of persistent blockstores. · f98ab0e5
      Mike Hibler authored
      Using "set-rwclone" ala:
          set $bsobj [$ns blockstore]
          $bsobj set-lease "emulab-ops/bar"
          $bsobj set-node $node
          $bsobj set-rwclone 1
      in your NS file will create a clone of the indicated persistent blockstore.
      Somewhat limited in utility since you can only have one clone of a
      particular blockstore per experiment.
  3. 15 Sep, 2016 1 commit
  4. 14 Sep, 2016 1 commit
  5. 12 Sep, 2016 2 commits
    • Mike Hibler's avatar
      Modify NOVIRTNFSMOUNTS to allow mounts on vnodes with routable IPs. · 470a81e5
      Mike Hibler authored
      This is different than the traditional behavior of this defs- variable.
      Previously it caused tmcd to not expose any NFS mounts to shared-host vnodes.
      We relax that now to allow exposing such mounts to vnodes with routable IP
      The rationale for this change is simply that the original option was only
      intended to prevent exporting mounts to hosts that could not reach the FS
      node anyway due to their unroutable cnet IPs.
    • Mike Hibler's avatar
      Make exports_setup consistent with tmcd w.r.t. NOVIRTNFSMOUNTS. · 7ba4cfd0
      Mike Hibler authored
      Previously, we would not pass the mounts via tmcd but they were still
      exported from fs.
  6. 06 Sep, 2016 1 commit
  7. 02 Sep, 2016 1 commit
    • Leigh Stoller's avatar
      Changes for dealing with group/password file locking errors: · fd0fd225
      Leigh Stoller authored
      * Move user mod (gecos,password) into the accountsetup proxy instead of
        ssh chpass. Wrap all usermod/chpass system calls in a loop that looks
        for the busy file error, back off and try again for a while.
      * Add same wrapping to local (boss) calls of usermod/chpass. I put that
        function into emutil.
      * Rename old modgroups in the proxy to setgroups, since that it is what
        it was actually doing.
  8. 29 Aug, 2016 3 commits
  9. 25 Aug, 2016 1 commit
  10. 10 Aug, 2016 1 commit
    • Mike Hibler's avatar
      Rejiggered reload_daemon to enforce a max time. · b6d272a2
      Mike Hibler authored
      There are now some sitevars to control its behavior, the one of interest here
      is reload/failtime:
      The way the reload daemon is supposed to work now is that nodes will be
      started on their reloading adventure with an os_load. If they are still there
      after reload/retrytime minutes, then they will either be rebooted (if the
      os_load was successful) or os_load'ed again (if the first os_load failed
      outright). The logic for either of these is that there might have been some
      transient condition that caused the failure. If we do have to perform this
      "retry" then we will send email to testbed-ops if reload/warnonretry is set.
      If, after another reload/retrytime minutes, a node is still there, then the
      node will be sent to hwdown, possibly powering it off or booting it into the
      admin MFS depending on the setting of reload/hwdownaction.
      So really, reload/failtime should not be needed. All node should exit
      reloading in 2 * reload/retrytime minutes. But it is there as a backstop
      (and because I didn't understand the logic of the reload daemon at first!)
      Well, it also comes into play if the reload daemon is restarted after being
      down for a long period of time. In this case, all nodes in reloading will
      get moved to hwdown. May need to reconsider this...
  11. 29 Jul, 2016 4 commits
  12. 21 Jul, 2016 1 commit
  13. 19 Jul, 2016 1 commit
  14. 17 Jun, 2016 1 commit
  15. 10 Jun, 2016 2 commits
  16. 06 Jun, 2016 1 commit
  17. 26 May, 2016 1 commit
  18. 16 May, 2016 1 commit
  19. 11 May, 2016 1 commit
  20. 10 May, 2016 1 commit
  21. 09 May, 2016 1 commit
  22. 06 May, 2016 2 commits
  23. 03 May, 2016 1 commit
  24. 28 Apr, 2016 1 commit
  25. 25 Apr, 2016 1 commit
  26. 18 Apr, 2016 1 commit
  27. 13 Apr, 2016 1 commit
  28. 12 Apr, 2016 1 commit
  29. 08 Apr, 2016 1 commit
  30. 07 Apr, 2016 3 commits