1. 17 Aug, 2010 1 commit
  2. 04 Jun, 2010 2 commits
    • Guido Trotter's avatar
      _ExecuteKVMRuntime: fix hv parameter fun · 297e6e53
      Guido Trotter authored
      When executing the kvm runtime we were currently accessing a mix of the
      parameters as configured currently on the instance and the ones it was
      started with. We were doing it without a precise criteria, but quite by
      chance we got it *almost* right. The only remaining issue was that when
      ganeti was upgraded and some parameters were added, trying to access
      them from the "old" ones caused a keyerror, since they weren't present
      back when the instance was started.
      
      To fix this:
        - We fill the startup-time dict with any new parameter
        - We provide a clear guideline on which version of the parameters to
          access, and about the fact that new parameters must have an
          instance-migration backwards compatible default
      Signed-off-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      297e6e53
    • Guido Trotter's avatar
      Update FinalizeMigration docstring · fea922fa
      Guido Trotter authored
      This is used not only for aborted migrations, so the docstring should
      reflect that.
      Signed-off-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      fea922fa
  3. 01 Jun, 2010 1 commit
    • Balazs Lecz's avatar
      Add KVM chroot feature · 547a63b7
      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.
      
      This has been backported from master,
      commit 84c08e4eSigned-off-by: default avatarBalazs Lecz <leczb@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      547a63b7
  4. 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
  5. 18 May, 2010 1 commit
  6. 12 May, 2010 1 commit
  7. 07 May, 2010 1 commit
  8. 28 Apr, 2010 1 commit
  9. 21 Apr, 2010 5 commits
  10. 20 Apr, 2010 3 commits
  11. 31 Mar, 2010 2 commits
  12. 23 Mar, 2010 1 commit
    • Iustin Pop's avatar
      Extend the hypervisor API with name-only shutdown · bbcf7ad0
      Iustin Pop authored
      Currently the ShutdownInstance method of the hypervisors takes a full
      instance object. However, when doing instance shutdowns from the node
      only, we don't have a full object, just the name.
      
      To handle this use case, we add a new ‘name’ argument to the method,
      which makes the shutdown not use/rely on the ‘instance’ argument. The
      KVM and fake hypervisors need a little bit of work, otherwise the change
      is straightforward.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      bbcf7ad0
  13. 22 Mar, 2010 2 commits
  14. 11 Mar, 2010 1 commit
  15. 10 Mar, 2010 3 commits
  16. 08 Mar, 2010 2 commits
  17. 02 Mar, 2010 1 commit
  18. 22 Jan, 2010 2 commits
  19. 04 Jan, 2010 4 commits
  20. 28 Dec, 2009 1 commit
  21. 10 Dec, 2009 1 commit
  22. 26 Nov, 2009 1 commit
  23. 11 Nov, 2009 1 commit
  24. 10 Nov, 2009 1 commit