1. 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
  2. 15 Sep, 2009 1 commit
  3. 14 Sep, 2009 1 commit
  4. 07 Sep, 2009 1 commit
  5. 04 Sep, 2009 1 commit
  6. 26 Aug, 2009 1 commit
  7. 24 Aug, 2009 1 commit
  8. 17 Aug, 2009 2 commits
  9. 14 Aug, 2009 1 commit
  10. 13 Aug, 2009 1 commit
  11. 05 Aug, 2009 1 commit
    • Iustin Pop's avatar
      export: add meaningful exit code · 084f05a5
      Iustin Pop authored
      
      
      Currently ‘gnt-backup export’ always returns exit code zero, even in the
      face of complete failure during backup (only failure to stop/start the
      instance will cause job failure and thus non-zero exit code). This is
      bad, since one cannot script the backup.
      
      This patch adds some simple results from the LU so that the command line
      script can return good exit code. It will:
        - return zero for full success (snapshot removal errors are ignored
          though)
        - return one for full failure (finalize export failure or all disks
          failure)
        - return two for partial failure (some disks backed up, some not)
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      084f05a5
  12. 04 Aug, 2009 4 commits
  13. 03 Aug, 2009 2 commits
  14. 29 Jul, 2009 1 commit
  15. 24 Jul, 2009 1 commit
  16. 19 Jul, 2009 1 commit
  17. 16 Jul, 2009 2 commits
    • Raiford Storey's avatar
      Improve the description of node flags in man page · 253ba78f
      Raiford Storey authored
      
      
      [iustin@google.com: slightly reworded the explanation for offline and
      changed the commit message]
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      253ba78f
    • 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
  18. 08 Jul, 2009 2 commits
  19. 07 Jul, 2009 1 commit
  20. 29 Jun, 2009 1 commit
  21. 18 Jun, 2009 1 commit
  22. 17 Jun, 2009 1 commit
  23. 16 Jun, 2009 2 commits
  24. 11 Jun, 2009 1 commit
  25. 27 May, 2009 1 commit
    • Iustin Pop's avatar
      Add a node powercycle command · f5118ade
      Iustin Pop authored
      
      
      This (somewhat big) patch adds support for remotely rebooting the nodes
      via whatever support the hypervisor has for such a concept.
      
      For KVM/fake (and containers in the future) this just uses sysrq plus a
      ‘reboot’ call if the sysrq method failed. For Xen, it first tries the
      above, and then Xen-hypervisor reboot (we first try sysrq since that
      just requires opening a file handle, whereas xen reboot means launching
      an external utility).
      
      The user interface is:
      
          # gnt-node powercycle node5
          Are you sure you want to hard powercycle node node5?
          y/[n]/?: y
          Reboot scheduled in 5 seconds
      
      The node reboots hopefully after sending the reply. In case the clock is
      broken, “time.sleep(5)” might take ages (but then I suspect SSL
      negotiation wouldn't work).
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      f5118ade
  26. 22 May, 2009 1 commit
  27. 19 May, 2009 1 commit
    • Iustin Pop's avatar
      Add -H/-B startup parameters to gnt-instance · d04aaa2f
      Iustin Pop authored
      
      
      This patch modifies the start instance script, opcode and logical unit
      to support temporary startup parameters.
      
      Different from 1.2, where only the kernel arguments were supporting
      changes (and thus xen-pvm specific), this version supports changing all
      hypervisor and backend parameters (with appropriate checks).
      
      This is much more flexible, and allows for example:
        - start with different, temporary kernel
        - start with different memory size
      
      Note: in later versions, this should be extended to cover disk
      parameters as well (e.g. start with drbd without flushes, start with
      drbd in async mode, etc.).
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      d04aaa2f
  28. 11 May, 2009 1 commit
  29. 06 May, 2009 1 commit
  30. 04 May, 2009 1 commit
    • Iustin Pop's avatar
      Allow gnt-debug submit-job to take multiple args · 99036060
      Iustin Pop authored
      
      
      Currently “gnt-debug submit-job” takes a single argument and has
      non-trivial startup-costs; in order to exercise the job system, it is
      better to be able to submit multiple jobs with a single invocation of
      the script.
      
      This patch extends it to take multiple argument, de-serialize the
      opcodes and then submit all of them as fast as possible, in order to
      increase pressure on the master daemon.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarAlexander Schreiber <als@google.com>
      99036060
  31. 24 Apr, 2009 1 commit
  32. 15 Apr, 2009 1 commit
    • Iustin Pop's avatar
      A bunch of doc and other small fixes · 949bdabe
      Iustin Pop authored
      This patch adds a couple of both externally and internally reported
      issues:
        - missing SGML tags (Issue 54), report and patch by superdupont
        - wrong variable used in the init.d script, report and patch by
          Karsten Keil <karsten-keil@t-online.de>
        - man page for gnt-instance reinstall needs clarification (Issue 56)
        - gnt-instance man page missing --disks documentation for
          replace-disks
        - gnt-node modify help output is unclear about the -C/-D/-O input
          format, and the man page doesn't document this command at all
        - “gnt-node modify -C yes” for offline or drained nodes had wrong
          error message
        - “gnt-instance reinstall --select-os” has wrong prompt, we only
          accept a number for the OS and not the template name
      
      Reviewed-by: ultrotter
      949bdabe