1. 13 Dec, 2017 1 commit
  2. 06 Oct, 2017 1 commit
  3. 05 Oct, 2017 1 commit
  4. 24 Jul, 2017 1 commit
  5. 05 Jun, 2017 1 commit
    • Leigh Stoller's avatar
      Working on issue #269 ... · ad2a3e70
      Leigh Stoller authored
      Add new script to "deprecate" images:
      
      	boss> wap deprecate_image
      	Usage: deprecate_image [-e|-w] <image> [warning message to users]
      	Options:
      	       -e     Use of image is an error; default is warning
      	       -w     Use of image is a warning
      
      When an image is deprecated with just warnings, new classic experiments
      generate warnings in the output. Swapping in an experiment also
      generates warnings in the output, but also sends email to the user.
      When the image set for error, both new experiment and swapin will fail
      with prejudice.
      
      Same deal on the Geni path; we generate warnings/errors and send email.
      Errors are reflected back in the Portal interface.
      
      At the moment the image server knows nothing about deprecated images, so
      the Portal constraint checker will not be bothered nor tell the user
      until later when the cluster throws an error. As a result, when we
      deprecate an image, we need to do it on all clusters. Needs to think
      about this a bit more.
      ad2a3e70
  6. 14 Mar, 2017 2 commits
    • Leigh Stoller's avatar
      Minor cleanup and fixes: · ad48bbdb
      Leigh Stoller authored
      1. Small bits of cleanup to remove hardwired paths and test for images
         that live in /usr/testbed and need special handling.
      
      2. Make sure that the image directory exists in /proj when taking a
         snapshot of a system image that lives in /usr/testbed since that is
         were we always write new images.
      
      3. When deleting an image, remove the DB state for the highest numbered
         version if it never came ready/released.
      ad48bbdb
    • Leigh Stoller's avatar
      Remove test for deleted from NewVersion(), turns out that a quirk of how · 7c345c85
      Leigh Stoller authored
      I implemented versioning for images make this test the wrong thing to
      do. I need to come back and change this, but its not a big deal right
      now.
      7c345c85
  7. 09 Mar, 2017 2 commits
  8. 07 Mar, 2017 1 commit
  9. 06 Mar, 2017 1 commit
  10. 01 Mar, 2017 1 commit
  11. 21 Feb, 2017 1 commit
  12. 07 Feb, 2017 1 commit
  13. 25 Jan, 2017 1 commit
  14. 03 Jan, 2017 1 commit
  15. 17 Oct, 2016 1 commit
  16. 12 Oct, 2016 1 commit
  17. 06 Oct, 2016 1 commit
  18. 29 Aug, 2016 2 commits
  19. 20 Jul, 2016 1 commit
  20. 22 Mar, 2016 2 commits
  21. 21 Mar, 2016 2 commits
  22. 20 Mar, 2016 1 commit
  23. 10 Nov, 2015 1 commit
  24. 02 Nov, 2015 1 commit
  25. 30 Oct, 2015 1 commit
  26. 03 Sep, 2015 1 commit
  27. 25 Aug, 2015 1 commit
    • Leigh Stoller's avatar
      Add a new table image_boot_status to record boot success/failure each time · 4fa9d2ea
      Leigh Stoller authored
      an image is loaded on a node. We want to know both success and failure over
      time so that we can determine when a image works or does not work on a
      particular node/type. This is primarily for the image tracker to determine
      what images work on what node types, but might be useful for in other
      situations. I realize this duplicates some info we already have in the
      image_history table, but that does not record failure, only success, and it
      mostly concerned with who is using what images.
      4fa9d2ea
  28. 21 Aug, 2015 1 commit
  29. 26 Jun, 2015 1 commit
  30. 25 Jun, 2015 1 commit
  31. 24 Jun, 2015 1 commit
  32. 19 Jun, 2015 1 commit
  33. 29 May, 2015 1 commit
  34. 26 May, 2015 1 commit
  35. 15 May, 2015 1 commit