1. 01 Nov, 2010 1 commit
    • Guido Trotter's avatar
      Drop the -g shortcut for --vg-name · 04367e70
      Guido Trotter authored
      
      
      Changing the volume group is a lot less frequent than acting on a node
      group. As such we drop the "-g" shortcut and require the long option to
      be passed. In 2.3 the commands which used to accept the volume group as
      "-g" won't have any node group option, so no confusion will arise. Later
      on we may pass "-g" as the initial node group name to gnt-cluster init,
      although that's not strictly necessary, as modifying it later is always
      possible.
      Signed-off-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      04367e70
  2. 26 Oct, 2010 1 commit
  3. 21 Oct, 2010 1 commit
  4. 19 Oct, 2010 1 commit
  5. 19 Aug, 2010 1 commit
  6. 17 Aug, 2010 1 commit
  7. 29 Jul, 2010 1 commit
  8. 28 Jul, 2010 1 commit
  9. 26 Jul, 2010 1 commit
  10. 08 Jul, 2010 1 commit
  11. 09 Jun, 2010 1 commit
  12. 01 Jun, 2010 1 commit
  13. 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
  14. 16 Apr, 2010 1 commit
  15. 08 Apr, 2010 1 commit
  16. 17 Mar, 2010 2 commits
  17. 15 Mar, 2010 1 commit
    • Michael Hanselmann's avatar
      Rightname confd's HMAC key · 6b7d5878
      Michael Hanselmann authored
      
      
      Currently, the ganeti-confd's HMAC key is called “cluster HMAC key” or
      simply “HMAC key” everywhere. With the implementation of inter-cluster
      instance moves, another HMAC key will be introduced for signing critical
      data. They can not be the same, so this patch clarifies the purpose of the
      “cluster HMAC key” by renaming it. The actual file name is not changed.
      Signed-off-by: default avatarMichael Hanselmann <hansmi@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      6b7d5878
  18. 12 Mar, 2010 1 commit
  19. 10 Feb, 2010 1 commit
  20. 01 Feb, 2010 1 commit
  21. 06 Nov, 2009 1 commit
  22. 22 Oct, 2009 1 commit
  23. 24 Sep, 2009 1 commit
    • Guido Trotter's avatar
      document the nic link meaning in routed mode · 8063787e
      Guido Trotter authored
      
      
      Currently this feature is hypervisor specific, but under kvm we use it
      by default (aka: if the user hasn't specified another network script
      which overrides our auto-generated one) to specify the routing table.
      This was already hinted as a possibility in the manpages, but never
      explicitely stated as a reality, so we update gnt-cluster(8) to actually
      say this, and gnt-{backup,instance}(8) to point to gnt-cluster(8) for
      more information.
      Signed-off-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      8063787e
  24. 26 Aug, 2009 1 commit
  25. 04 Aug, 2009 1 commit
  26. 29 Jul, 2009 1 commit
  27. 16 Jul, 2009 1 commit
    • Guido Trotter's avatar
      Get rid of the default_hypervisor slot · 066f465d
      Guido Trotter authored
      
      
      Currently we have both a default_hypervisor and an enabled_hypervisors
      list. The former is only settable at cluster init time, while the latter
      can be changed with cluster modify.
      
      This becomes cumbersome in a few ways: at cluster init time for example
      if we pass in a list of enabled hypervisors which doesn't include the
      "default" xen-pvm one, we're also forced to pass a default hypervisor,
      or an error will be reported. It is also currently possible to disable
      the default hypervisor in cluster-modify (with unknown results).
      
      In order to avoid this we get rid of this field altogether, and define
      the "first" enabled hypervisor as the default one. This allows ease of
      changing which one is the default, and at the same time maintains
      coherency.
      
      At configuration upgrade we make sure that the old default is first in
      the list, so that 2.0 cluster defaults are preserved.
      Signed-off-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      066f465d
  28. 08 Jul, 2009 2 commits
  29. 17 Jun, 2009 1 commit
  30. 16 Jun, 2009 1 commit
  31. 11 Jun, 2009 1 commit
  32. 05 Mar, 2009 1 commit
    • Guido Trotter's avatar
      Update gnt-cluster(8) for be/hyp parameter syntax · 555918b3
      Guido Trotter authored
      Now it displays:
      
      --hypervisor-parameters hypervisor:hv-param=value [ ,hv-param=value ... ]
      --backend-parameters be-param=value [ ,be-param=value ... ]
      
      Sorry for the super-long lines :( Is there a better way to insert spaces
      without pushing them to the resulting man page?
      
      Reviewed-by: iustinp
      555918b3
  33. 12 Feb, 2009 1 commit
  34. 23 Oct, 2008 2 commits
  35. 20 Oct, 2008 1 commit
  36. 08 Oct, 2008 1 commit
  37. 29 Aug, 2008 1 commit