1. 06 Dec, 2010 1 commit
  2. 03 Dec, 2010 2 commits
  3. 05 Oct, 2010 2 commits
  4. 04 Oct, 2010 1 commit
  5. 20 Sep, 2010 1 commit
  6. 18 Aug, 2010 1 commit
    • Manuel Franceschini's avatar
      Introduce new IPAddress classes · 8b312c1d
      Manuel Franceschini authored
      
      
      This patch unifies the netutils functions dealing with IP addresses to
      three classes:
      - IPAddress: Common IP address functionality
      - IPv4Address: IPv4 specific functionality
      - IPv6address: IPv6-specific functionality
      
      Furthermore it adds methods to check whether an address is a loopback
      address, replacing the .startswith("127") for IPv4 and adding IPv6
      support.
      
      It also provides the basis for future IPv6 address handling. Methods to
      convert IP strings to their corresponding interger values will allow to
      canonicalize IPv6 addresses.
      Signed-off-by: default avatarManuel Franceschini <livewire@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      8b312c1d
  7. 17 Aug, 2010 2 commits
  8. 23 Jul, 2010 1 commit
  9. 16 Jul, 2010 1 commit
    • Iustin Pop's avatar
      Add a migration type global hypervisor parameter · e71b9ef4
      Iustin Pop authored
      
      
      Since migration live/non-live is more stable (e.g.) for Xen-PVM versus
      Xen-HVM, we introduce a new parameter for what mode we should use by
      default (if not overridden by the user, in the opcode).
      
      The meaning of the opcode 'live' field changes from boolean to either
      None (use the hypervisor default), or one of the allowed migration
      string constants. The live parameter of the TLMigrateInstance is still a
      boolean, computed from the opcode field (which is no longer passed to
      the TL).
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      e71b9ef4
  10. 15 Jul, 2010 1 commit
  11. 09 Jul, 2010 1 commit
  12. 30 Jun, 2010 2 commits
  13. 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
  14. 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 84c08e4e
      
      Signed-off-by: default avatarBalazs Lecz <leczb@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      547a63b7
  15. 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
  16. 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
  17. 18 May, 2010 1 commit
  18. 12 May, 2010 1 commit
  19. 07 May, 2010 1 commit
  20. 28 Apr, 2010 1 commit
  21. 21 Apr, 2010 5 commits
  22. 20 Apr, 2010 3 commits
  23. 31 Mar, 2010 2 commits
  24. 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
  25. 22 Mar, 2010 2 commits
  26. 11 Mar, 2010 1 commit
  27. 10 Mar, 2010 1 commit