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. 28 Oct, 2010 1 commit
  3. 27 Oct, 2010 1 commit
  4. 26 Oct, 2010 2 commits
  5. 20 Oct, 2010 1 commit
  6. 05 Oct, 2010 1 commit
  7. 30 Sep, 2010 1 commit
  8. 20 Sep, 2010 2 commits
  9. 14 Sep, 2010 2 commits
  10. 13 Sep, 2010 1 commit
  11. 07 Sep, 2010 1 commit
  12. 24 Aug, 2010 1 commit
    • Michael Hanselmann's avatar
      Add simple lock monitor · 19b9ba9a
      Michael Hanselmann authored
      
      
      This patch adds an initial implementation of a lock monitor, accessible
      for the user through “gnt-debug locks”. It currently shows all resource
      locks: BGL, nodes and instances. Config and job queue locks could be
      shown too, but wouldn't be of much help.  The current owner(s) and mode
      are also shown.
      
      Showing pending acquires will require further changes on the SharedLock
      internals and is not yet implemented.
      
      Example output:
      $ gnt-debug locks -o name,mode,owner
      Name            Mode      Owner
      BGL/BGL         shared    JobQueue19/Job147
      instances/inst1 exclusive JobQueue19/Job147
      instances/inst2 -         -
      instances/inst3 -         -
      instances/inst4 -         -
      nodes/node1     exclusive JobQueue19/Job147
      nodes/node2     exclusive JobQueue19/Job147
      Signed-off-by: default avatarMichael Hanselmann <hansmi@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      19b9ba9a
  13. 23 Aug, 2010 1 commit
  14. 19 Aug, 2010 2 commits
  15. 18 Aug, 2010 1 commit
  16. 13 Aug, 2010 1 commit
  17. 28 Jul, 2010 2 commits
    • Iustin Pop's avatar
      Improve handling of lost jobs · 91c622a8
      Iustin Pop authored
      
      
      Currently, if the cli.JobExecutor class is being used, and one of the
      jobs is being archived before it can check its result, it will raise a
      stracktrace as _ChooseJob is not prepared to handle this case.
      
      This case makes JobExecutor work better with lost jobs (it still reports
      them as 'failed', but it doesn't break and returns a proper error
      message), and modifies the generic FormatError to report the JobLost
      exception properly, instead of as "Unhandled Ganeti Exception".
      
      Since JobExecutor is hard to test properly, I only tested this manually,
      via a fake invocation.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      91c622a8
    • Iustin Pop's avatar
      luxi: convert permission errors into exception · 5a1c22fe
      Iustin Pop authored
      
      
      This patch adds handling of permission errors so that we don't show
      tracebacks when a non-root user runs a gnt-* command. Since in the
      future we'll have different permissions, we need to handle this in RAPI
      too.
      
      It also fixes a typo in RAPI error message and the docstrings of LUXI
      errors.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      5a1c22fe
  18. 26 Jul, 2010 2 commits
  19. 23 Jul, 2010 1 commit
  20. 19 Jul, 2010 1 commit
    • Iustin Pop's avatar
      Introduce git reference/tag tracking for debugging · 84a12e40
      Iustin Pop authored
      
      
      This patch adds a new vcs-version file that is generated via git (and
      can be adapted if VCS is changed) and then embebbded as VCS_VERSION in
      the constants module.
      
      This means two things:
      - local modifications without committing to git (or when using a tar.gz
        archive + mods) will not be reflected
      - version is fixed at the time of the last make regen-vcs-version (dist time,
        or devel/upload which calls this)
      
      Thus this is more geared at developers rather than end users.
      
      The patch:
      
      - adds rules for generating the vcs-version file
      - adds a dist-hook for re-generating the file (if possible) and copying
        the updated version to the distdir
      - modifies devel/upload to re-generate the file before upload
      
      The output of --version will look like:
      gnt-cluster (ganeti v2.2.0beta0-184-gebca7e6) 2.2.0~beta0
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      84a12e40
  21. 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
  22. 12 Jul, 2010 2 commits
  23. 09 Jul, 2010 1 commit
  24. 08 Jul, 2010 1 commit
  25. 06 Jul, 2010 2 commits
  26. 29 Jun, 2010 1 commit
  27. 23 Jun, 2010 1 commit
  28. 22 Jun, 2010 1 commit
  29. 10 Jun, 2010 1 commit
  30. 25 May, 2010 1 commit
  31. 10 May, 2010 1 commit
  32. 21 Apr, 2010 1 commit