1. 20 Mar, 2012 1 commit
  2. 19 Mar, 2012 1 commit
  3. 16 Mar, 2012 10 commits
  4. 15 Mar, 2012 22 commits
  5. 14 Mar, 2012 3 commits
    • Mike Hibler's avatar
      Minor syntax error in update script. · ceaa2539
      Mike Hibler authored
      ceaa2539
    • Mike Hibler's avatar
      Make the secure boot path work with PXEWAIT. · ceeede28
      Mike Hibler authored
      When a node with the secure boot dongle is freed, it goes into PXEWAIT in
      the context of the secure MFS. Previously we remained in "secure mode"
      (i.e., did not terminate with a TPMSIGNOFF) while a node was in this state.
      If the next use of the node, just booted from the OS that was already on
      the disk, then we never signed off properly.
      
      Now we sign off before entering PXEWAIT. I thought that this would be the
      easiest alternative to fixing the problem..HaHaHa..not! Because now we have
      to restart the secure boot path (i.e., reboot) if the result of coming out
      of PXEWAIT is a request to reload the disk (i.e., if we are continuing the
      secure disk load path).
      
      Ideally this would have required only modifications to the state machines
      for SECUREBOOT/LOAD, but as you can see by the presence of stated.in in the
      modified files, this was not the case. The change required some additional
      "finesse" to get it working. See the comments in stated.in and bootinfo_mysql.c
      if you really care.
      ceeede28
    • Mike Hibler's avatar
      Pass through bootinfo flags on tmcc "bootwhat" command. · 3ca3abf6
      Mike Hibler authored
      bootwhat will now return a FLAGS=%d value corresponding to the flags
      field in the boot_what struct.
      
      NOTE: THIS REQUIRED A TMCD VERSION BUMP. We are now at version 35.
      The issue was backward compatibility with existing CD/dongle boot images
      which are overly strict in their parsing of the returned bootwhat values.
      
      Added a new boot_what flag (the whole point of this) to signify if the
      entity being returned is part of the "secure boot" path. This is used
      by the gPXE dongle to determine whether it needs to do a trusted boot
      path "sign-off" for the MFS it downloads. We used to use the name of
      the MFS as our heuristic for this.
      
      bootinfo uses the new tbdb.os_info osfeature "ontrustedboot" to determine
      whether to set the flag.
      3ca3abf6
  6. 13 Mar, 2012 1 commit
  7. 12 Mar, 2012 1 commit
    • Mike Hibler's avatar
      Print a less obtuse error if they attempt to image an "empty" partition. · 31e17da2
      Mike Hibler authored
      This is in the node type check where we look at what is currently in the
      partition they are imaging, and base the set of valid node type on that.
      However, if they specify a partition that doesn't currently have an image,
      we would previously effectively tell them that the image will not run on
      the node type that it is currently running on!
      
      Now we just say "there is no current image in that partition."
      31e17da2
  8. 11 Mar, 2012 1 commit