1. 13 Jan, 2010 1 commit
  2. 04 Jan, 2010 2 commits
  3. 28 Dec, 2009 1 commit
  4. 06 Nov, 2009 2 commits
  5. 02 Nov, 2009 1 commit
  6. 15 Oct, 2009 2 commits
  7. 13 Oct, 2009 1 commit
  8. 12 Oct, 2009 5 commits
  9. 17 Sep, 2009 1 commit
  10. 15 Sep, 2009 2 commits
  11. 09 Sep, 2009 1 commit
  12. 25 Aug, 2009 4 commits
  13. 24 Aug, 2009 3 commits
  14. 17 Aug, 2009 1 commit
  15. 14 Aug, 2009 1 commit
  16. 10 Aug, 2009 1 commit
  17. 04 Aug, 2009 2 commits
  18. 03 Aug, 2009 1 commit
  19. 31 Jul, 2009 1 commit
  20. 22 Jul, 2009 1 commit
  21. 07 Jul, 2009 2 commits
  22. 19 Jun, 2009 1 commit
  23. 18 Jun, 2009 1 commit
  24. 15 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