1. 07 Sep, 2007 2 commits
  2. 06 Sep, 2007 1 commit
  3. 05 Sep, 2007 5 commits
  4. 04 Sep, 2007 4 commits
  5. 31 Aug, 2007 11 commits
  6. 30 Aug, 2007 2 commits
  7. 29 Aug, 2007 6 commits
  8. 28 Aug, 2007 2 commits
  9. 27 Aug, 2007 5 commits
  10. 24 Aug, 2007 2 commits
    • Leigh B. Stoller's avatar
      Both blind and dumb, thats me! · 8d12cd58
      Leigh B. Stoller authored
    • Mike Hibler's avatar
      First crack at limiting the node types assigned to new images. · fff92262
      Mike Hibler authored
      Currently we declare the valid types for an image to be those that are of
      class "pc" and for which we have at least one node in the testbed.
      With this change, when an image is created as a snapshot from an existing
      node, we look at the partition info for the existing image to further
      restrict the types that the derived image will work on.
      This will prevent images derived from old images like RHL90 or FBSD410
      from getting newer node types such as pc745d as a valid type.
      One problem with the current solution is that, we don't know til the form
      is submitted once, what node you are snapshot'ing, so the first time a
      user submits the form, it is almost certain to come back with an error.
      Further, they have no choice but to uncheck the offending types.  If part
      of their customization was to add support for a new node type...too bad,
      ya' can't add it!  There are numerous ways to fix this, all of which exceed
      my Friday afternoon mad hacking skilz.