1. 13 Oct, 2009 2 commits
  2. 09 Oct, 2009 1 commit
  3. 05 Oct, 2009 1 commit
  4. 25 Sep, 2009 1 commit
  5. 24 Sep, 2009 2 commits
  6. 15 Sep, 2009 1 commit
  7. 14 Sep, 2009 1 commit
  8. 07 Sep, 2009 1 commit
  9. 04 Sep, 2009 1 commit
  10. 26 Aug, 2009 1 commit
  11. 24 Aug, 2009 1 commit
  12. 17 Aug, 2009 2 commits
  13. 14 Aug, 2009 1 commit
  14. 13 Aug, 2009 1 commit
  15. 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
  16. 04 Aug, 2009 4 commits
  17. 03 Aug, 2009 2 commits
  18. 29 Jul, 2009 1 commit
  19. 24 Jul, 2009 1 commit
  20. 19 Jul, 2009 1 commit
  21. 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
  22. 08 Jul, 2009 2 commits
  23. 07 Jul, 2009 1 commit
  24. 29 Jun, 2009 1 commit
  25. 18 Jun, 2009 1 commit
  26. 17 Jun, 2009 1 commit
  27. 16 Jun, 2009 2 commits
  28. 11 Jun, 2009 1 commit
  29. 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
  30. 22 May, 2009 1 commit