1. 03 Oct, 2012 9 commits
  2. 01 Oct, 2012 2 commits
  3. 28 Sep, 2012 13 commits
  4. 27 Sep, 2012 3 commits
  5. 26 Sep, 2012 9 commits
  6. 25 Sep, 2012 4 commits
    • Mike Hibler's avatar
      Logic for making osload failures non-fatal when nonfatal failure mode is set. · 783d3caf
      Mike Hibler authored
      Previously tb-set-node-failure-mode of "nonfatal" only applied to failures
      when rebooting a node. If there was an error during the disk reload phase,
      the experiment would still fail.
      This makes sense, as it is pretty dicey to let a node boot with an unloaded
      or partially-loaded disk. But there are situations, such as 500+ node
      experiments on PRObE, where it makes sense to not fail the experiment.
      What we do if a node fails reload, is to clear the OSIDs and partition info
      for the node and then force it to reboot (by setting the state to TBFAILED,
      for which there is a REBOOT trigger in stated). This causes the node to come
      up and park in pxeboot in the PXEWAIT state. It should remain in this state
      across reboots. The user can manually os_load the machine, or do a swap
      modify which will force the node to try to reload the original OS.
      Since this may not be for everyone, this new allow non-fatal osload failures
      requires that the "OsloadFailNonfatal" feature be enabled. This allows the
      new behavior to be global, per-group, per-experiment or per-user. The default
      is disabled.
    • Mike Hibler's avatar
      More fixed to "wedged node" handling. · e5d8d3cf
      Mike Hibler authored
    • Leigh B Stoller's avatar
      Changes to support XEN shared nodes and guest snapshots. · 2489c09b
      Leigh B Stoller authored
      Snapshots are done a little differently then openvz of course, since
      there are potentially multiple disk partitions and a kernel. The basic
      operation is:
      1. Fire off reboot_prepare from boss. Changes to reboot_prepare result
         in the guest "halting" insted of rebooting.
      2. Fire off the create-image client script, which will take imagezips
         of all of the disks (except the swap partition), and grab a copy of
         the kernel. A new xm.conf file is written, and then the directory
         is first tar'ed and then we imagezip that bundle for upload.
      3. When booting a guest, we now look for guest images that are
         packaged in this way, although we still support the older method
         for backwards compatability. All of the disks are restored, and a
         new xm.conf created that points to the new kernel.
    • Leigh B Stoller's avatar
      Export VMs control addresses to SHAREDHOST nodes, so that XEN VMs · 86d5e5ef
      Leigh B Stoller authored
      can mount the NFS filesystems. Only doing this for shared hosts
      at this time, to avoid driving up the number of exports too much.
      Might reconsider later.