1. 21 Dec, 2009 8 commits
    • Leigh Stoller's avatar
      New approach to dealing with nodes that fail to boot is os_setup, and · 5cf6aad2
      Leigh Stoller authored
      land in hwdown.
      
      Currently, if a node fails to boot in os_setup and the node is running
      a system image, it is moved into hwdown. 99% of the time this is
      wasted work; the node did not fail for hardware reasons, but for some
      other reason that is transient.
      
      The new approach is to move the node into another holding experiment,
      emulab-ops/hwcheckup. The daemon watches that experiment, and nodes
      that land in it are freshly reloaded with the default image and
      rebooted. If the node reboots okay after reload, it is released back
      into the free pool. If it fails any part of the reload/reboot, it is
      officially moved into hwdown.
      
      Another possible use; if you have a suspect node, you go wiggle some
      hardware, and instead of releasing it into the free pool, you move it
      into hwcheckup, to see if it reloads/reboots. If not, it lands in
      hwdown again. Then you break out the hammer.
      
      Most of the changes in Node.pm, libdb.pm, and os_setup are
      organizational changes to make the code cleaner.
      5cf6aad2
    • Robert Ricci's avatar
      Change the mail and branch matching code due to a conversation I had · 46157519
      Robert Ricci authored
      with Eric this afternoon.
      46157519
    • Ryan Jackson's avatar
      More readme cleanup · bd235551
      Ryan Jackson authored
      bd235551
    • Ryan Jackson's avatar
      Add helper scripts to make exporting to CVS easier · facfd08e
      Ryan Jackson authored
      - git-cvsexportcommit.mod is the same as the standard
        git-cvsexportcommit script, except it doesn't fail if you try applying
        a patch to the sandbox that has already been applied (i.e., you do a
        cvspush before the upstream git repo has been updated).
      
      - git-cvspush uses the above script to export each commit between the
        upstream branch head and your local branch head to CVS. To use it,
        run the following command inside your git repo:
      
        git config branch.<branch>.cvsdir <sandbox>
      
        where '<branch>' is your local git branch name and '<sandbox>' is
        the CVS sandbox where you've checked out that branch.  Set up an
        alias for it with this:
      
        git config --global alias.cvspush "!git-cvspush"
      
        and run 'git cvspush <branch>' (where '<branch>' is the branch to push
        or the current one if not specified) when you're ready to push pending
        commits to CVS.
      facfd08e
    • Robert Ricci's avatar
      New script: gitmail . Will be used to send out mail about git pushes · bcd94a3b
      Robert Ricci authored
      to mailing lists, etc.
      bcd94a3b
    • Ryan Jackson's avatar
      Cleanup of old TODOs · e0798882
      Ryan Jackson authored
      e0798882
    • Mike Hibler's avatar
      Another random thought. · d68056a7
      Mike Hibler authored
      d68056a7
    • Leigh Stoller's avatar
      Add -j option when creating system experiments, so that they get · 4c05ab13
      Leigh Stoller authored
      marked as active instead of new.
      
      Add another system experiment, hwcheckup for automated testing of
      nodes that have failed during a swapin.
      4c05ab13
  2. 18 Dec, 2009 15 commits
  3. 17 Dec, 2009 3 commits
  4. 16 Dec, 2009 1 commit
  5. 15 Dec, 2009 13 commits