1. 29 Jul, 2010 1 commit
    • Iustin Pop's avatar
      Change semantics of --force-multi for reinstall · 297ddce9
      Iustin Pop authored
      
      
      Currently, we require both --force and --force-multiple for skipping the
      confirmation on instance reinstalls. After offline conversations, this
      has been deemed to be excessive, and this patch changes the meaning of
      --force-multiple to be a “stronger” force, and not require both.
      
      So, to skip the prompts:
      - single instance reinstallation requires either --force or
        --force-multiple
      - multiple instance reinstallation requires --force-multiple
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      297ddce9
  2. 23 Jul, 2010 1 commit
  3. 16 Jul, 2010 2 commits
  4. 08 Jul, 2010 1 commit
  5. 06 Jul, 2010 1 commit
  6. 09 Jun, 2010 1 commit
  7. 01 Jun, 2010 2 commits
  8. 31 May, 2010 1 commit
    • Apollon Oikonomopoulos's avatar
      KVM: Migration bandwidth and downtime control · e43d4f9f
      Apollon Oikonomopoulos authored
      
      
      Introduce 2 new hypervisor options, migration_bandwidth and migration_downtime
      and implement KVM migration bandwidth and downtime control.
      
      migration_bandwidth controls KVM's maximal bandwidth during migration, in
      MiB/s. Default value is 32 MiB/s, same as KVM's internal default. This option
      is a global hypervisor option.
      
      migration_downtime sets the amount of time (in ms) a KVM instance is allowed to
      freeze while copying memory pages. This is useful when migrating busy guests,
      as KVM's internal default of 30ms is too low for the page-copying algorithm to
      converge. This is a per-instance option, with a default of 30ms, same as KVM's
      internal default.
      Signed-off-by: default avatarApollon Oikonomopoulos <apollon@noc.grnet.gr>
      Signed-off-by: default avatarBalazs Lecz <leczb@google.com>
      Reviewed-by: default avatarBalazs Lecz <leczb@google.com>
      e43d4f9f
  9. 28 May, 2010 1 commit
    • Balazs Lecz's avatar
      Add KVM chroot feature · 84c08e4e
      Balazs Lecz authored
      
      
      This patch adds a new boolean hypervisor parameter to the KVM hypervisor,
      named 'use_chroot'.
      If it's turned on for an instance, than KVM is started in "chroot mode":
      Ganeti creates an empty directory for the instance and passes the path
      of this dir to KVM via the -chroot flag.
      KVM changes its root to this directory after starting up.
      
      It also adds a "quarantine" feature for moving any unexpected files to
      a separate directory for later analysis.
      Signed-off-by: default avatarBalazs Lecz <leczb@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      84c08e4e
  10. 20 Apr, 2010 1 commit
  11. 31 Mar, 2010 1 commit
  12. 17 Mar, 2010 2 commits
  13. 15 Mar, 2010 2 commits
  14. 10 Mar, 2010 3 commits
  15. 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
  16. 01 Feb, 2010 1 commit
  17. 22 Jan, 2010 1 commit
  18. 16 Dec, 2009 1 commit
  19. 10 Dec, 2009 1 commit
  20. 26 Nov, 2009 1 commit
  21. 25 Nov, 2009 1 commit
  22. 16 Nov, 2009 1 commit
  23. 06 Nov, 2009 2 commits
  24. 04 Nov, 2009 1 commit
  25. 13 Oct, 2009 2 commits
  26. 09 Oct, 2009 1 commit
  27. 24 Sep, 2009 2 commits
  28. 24 Aug, 2009 1 commit
  29. 17 Aug, 2009 1 commit
  30. 14 Aug, 2009 1 commit
  31. 13 Aug, 2009 1 commit