1. 11 Apr, 2018 5 commits
  2. 10 Apr, 2018 3 commits
  3. 09 Apr, 2018 6 commits
  4. 07 Apr, 2018 3 commits
  5. 06 Apr, 2018 1 commit
  6. 05 Apr, 2018 1 commit
  7. 03 Apr, 2018 8 commits
  8. 02 Apr, 2018 4 commits
  9. 30 Mar, 2018 6 commits
    • Kirk Webb's avatar
      Add s5048 model definitions. · c5ee65fa
      Kirk Webb authored
      c5ee65fa
    • Mike Hibler's avatar
      Install the right file Mike.. · 396431a0
      Mike Hibler authored
      396431a0
    • Mike Hibler's avatar
    • Mike Hibler's avatar
      Initialize port range from defs- vars. · e593d62b
      Mike Hibler authored
      e593d62b
    • Mike Hibler's avatar
      Support for frisbee direct image upload to fs node. · 99943a19
      Mike Hibler authored
      We have had issues with uploading images to boss where they are then written
      across NFS to ops. That seems to be a network hop too far on CloudLab Utah
      where we have a 10Gb control network. We get occasional transcient timeouts
      from somewhere in the TCP code. With the convoluted path through real and
      virtual NICs, some with offloading, some without, packets wind up getting
      out of order and someone gets far enough behind to cause problems.
      
      So we work around it.
      
      If IMAGEUPLOADTOFS is defined in the defs-* file, we will run a frisbee
      master server on the fs (ops) node and the image creation path directs the
      nodes to use that server. There is a new hack configuration for the master
      server "upload-only" which is extremely specific to ops: it validates the
      upload with the boss master server and, if allowed, fires up an upload
      server for the client to talk to. The image will thus be directly uploaded
      to the local (ZFS) /proj or /groups filesystems on ops. This seems to be
      enough to get around the problem.
      
      Note that we could allow this master server to serve downloads as well to
      avoid the analogous problem in that direction, but this to date has not
      been a problem.
      
      NOTE: the ops node must be in the nodes table in the DB or else boss will
      not validate proxied requests from it. The standard install procedure is
      supposed to add ops, but we have a couple of clusters where it is not in
      the table!
      99943a19
    • Leigh Stoller's avatar
      Minor fixes. · e4485562
      Leigh Stoller authored
      e4485562
  10. 29 Mar, 2018 3 commits