1. 11 Feb, 2010 9 commits
  2. 10 Feb, 2010 2 commits
  3. 09 Feb, 2010 1 commit
    • Iustin Pop's avatar
      Add an early release lock/storage for disk replace · 7ea7bcf6
      Iustin Pop authored
      
      
      This patch adds an early_release parameter in the OpReplaceDisks and
      OpEvacuateNode opcodes, allowing earlier release of storage and more
      importantly of internal Ganeti locks.
      
      The behaviour of the early release is that any locks and storage on all
      secondary nodes are released early. This is valid for change secondary
      (where we remove the storage on the old secondary, and release the locks
      on the old and new secondary) and replace on secondary (where we remove
      the old storage and release the lock on the secondary node.
      
      Using this, on a three node setup:
      
      - instance1 on nodes A:B
      - instance2 on nodes C:B
      
      It is possible to run in parallel a replace-disks -s (on secondary) for
      instances 1 and 2.
      
      Replace on primary will remove the storage, but not the locks, as we use
      the primary node later in the LU to check consistency.
      
      It is debatable whether to also remove the locks on the primary node,
      and thus making replace-disks keep zero locks during the sync. While
      this would allow greatly enhanced parallelism, let's first see how
      removal of secondary locks works.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      7ea7bcf6
  4. 08 Feb, 2010 2 commits
  5. 03 Feb, 2010 4 commits
  6. 01 Feb, 2010 7 commits
  7. 29 Jan, 2010 1 commit
  8. 28 Jan, 2010 3 commits
  9. 27 Jan, 2010 6 commits
  10. 26 Jan, 2010 2 commits
  11. 25 Jan, 2010 3 commits
    • Iustin Pop's avatar
      Add a crude disable for DRBD barriers · 89b70f39
      Iustin Pop authored
      
      
      Ideally we want to/will have per-device DRBD controls of disk/metadata
      flushes. In the meantime, we want at least a disable of the barrier
      functionality for cases where one has battery-backed caches.
      
      Background: DRBD has four mechanism of handling ordered disk-writes.
      From the drbdsetup man-page, these are: barrier, flush, drain and none.
      DRBD prior to 8.2 only has drain and none. This patch makes all 8.x
      versions of DRBD disable all methods, and revert to none, in case one
      fully trusts batteries (either UPS for the whole system or battery for
      NVRAM).
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      89b70f39
    • Iustin Pop's avatar
      LURemoveNode safety in face of wrong node list · 9bb31ea8
      Iustin Pop authored
      
      
      LURemoveNode runs under the BGL, which means we're guaranteed that the
      list of nodes as retrieved in CheckPrereq is still valid in
      BuildHooksEnv. However, we can make Ganeti handle failures in case the
      locking is broken (or the node list has been modified otherwise) easily,
      which is better than crashing hard in such a case.
      
      This will also fix issue 79, even though that is due to an out-of-tree
      patch.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      9bb31ea8
    • Iustin Pop's avatar
      Fix an unsafe formatting bug · 62579388
      Iustin Pop authored
      
      
      This might fix issue 84; in any case, the current situation is that we
      have a potentially unsafe formatting, which should be fixed.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      62579388