1. 15 Mar, 2010 1 commit
    • Iustin Pop's avatar
      Implement conversion from plain to drbd · e29e9550
      Iustin Pop authored
      This patch adds a new mode to instance modify, the changing of the disk
      template. For now only plain to drbd conversion is supported, and the
      new secondary node must be specified manually (no iallocator support).
      The procedure for conversion works as follows:
      - a completely new disk template is created, matching the count, size
        and mode of the instance's current disks
      - we create manually (not via _CreateDisks) all the missing volumes
      - we rename on the primary the LVs to the new name
      - we create manually the DRBD devices
      Failures during the creation of volumes will leave orphan volumes.
      Failure during the rename might leave some disks renamed and some not,
      leading to an inconsistent instance.
      Once the disks are renamed, we update the instance information and wait
      for resync. Any failures of the DRBD sync must be manually handled (like
      a normal failure, e.g. by running replace-disks, etc.).
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
  2. 11 Feb, 2010 2 commits
  3. 09 Feb, 2010 2 commits
    • 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>
    • Iustin Pop's avatar
      Fix "gnt-instance rename" functionality · c4a73785
      Iustin Pop authored
      Commit 91e0748c
       (Unify the “--no-ip-check” option) broke the options
      variable name for ‘--no-ip-check’ but since we don't have a QA test for
      instance rename (only burnin test), this was not caught until Issue 86
      was opened.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
  4. 25 Jan, 2010 1 commit
  5. 21 Jan, 2010 1 commit
  6. 04 Jan, 2010 3 commits
  7. 16 Dec, 2009 1 commit
  8. 25 Nov, 2009 2 commits
  9. 16 Nov, 2009 1 commit
  10. 02 Nov, 2009 1 commit
  11. 13 Oct, 2009 2 commits
  12. 09 Oct, 2009 1 commit
  13. 05 Oct, 2009 2 commits
  14. 24 Sep, 2009 1 commit
  15. 21 Sep, 2009 1 commit
  16. 18 Sep, 2009 18 commits