1. 11 Apr, 2013 2 commits
  2. 04 Apr, 2013 2 commits
  3. 02 Apr, 2013 1 commit
  4. 27 Mar, 2013 3 commits
  5. 26 Mar, 2013 1 commit
  6. 21 Mar, 2013 1 commit
  7. 22 Feb, 2013 1 commit
    • Iustin Pop's avatar
      Add option to redirect luxi socket for debugging · 055d6ac0
      Iustin Pop authored
      
      
      Currently, the choice between masterd and conf/queryd is made
      statically, based on whether a query is converted or not and whether
      split queries are enabled. This makes it hard to test and develop
      these new queries, so this patch adds an override for the socket.
      
      The choice for going with two hardcoded strings and arbitrary socket
      fallback is done so that it's easy to use this in virtual clusters as
      well.
      
      Additionally, the patch improves the error message on failed connects
      when we use arbitrary sockets; before, it always "blamed" confd for
      non-master sockets.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      055d6ac0
  8. 19 Feb, 2013 1 commit
  9. 11 Feb, 2013 2 commits
  10. 22 Dec, 2012 1 commit
    • Constantinos Venetsanopoulos's avatar
      Add the gnt-storage client · b954f097
      Constantinos Venetsanopoulos authored
      
      
      Add a new client called 'gnt-storage'.
      The client interacts with the ExtStorage interface, similarly to
      the way gnt-os interacts with the OS interface.
      
      For now, only two commands are supported: 'info' and 'diagnose'.
      
      'diagnose' calculates the node status of each provider on each node,
      similarly to gnt-os diagnose. Furthermore, for every provider, it
      calculates it's nodegroup validity for each nodegroup. This is done
      inside the LU and not the client (marked as 'TODO' for the  global
      validity of gnt-os diagnose).
      
      In the future, gnt-storage can be used to manage storage pools,
      or even be extended to diagnose other storage types supported by
      Ganeti, such as lvm, drbd (INT_MIRROR) or rbd (EXT_MIRROR).
      Signed-off-by: default avatarConstantinos Venetsanopoulos <cven@grnet.gr>
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      [iustin@google.com: fixed Haskell compatibility and style fixes]
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      b954f097
  11. 21 Dec, 2012 1 commit
  12. 19 Dec, 2012 1 commit
  13. 04 Dec, 2012 1 commit
  14. 20 Nov, 2012 4 commits
  15. 15 Nov, 2012 1 commit
  16. 05 Nov, 2012 1 commit
    • Dato Simó's avatar
      cli.py: use None as name for tag operations on the cluster · bcd35e09
      Dato Simó authored
      
      
      This change is mostly cosmetic. Previously, the literal "cluster" was
      used for the 'name' field of tag operations on the cluster (as opposed
      to a node or an instance). Since this field has a type of TMaybeString
      specifically for the case of the cluster, it seems more correct to use
      None, rather than an arbitrary string (that is not used by the callee).
      
      Additionally: note in opcodes.py that groups also expect a name; the
      previous comment only referred to nodes and instances.
      Signed-off-by: default avatarDato Simó <dato@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      bcd35e09
  17. 25 Oct, 2012 1 commit
  18. 17 Oct, 2012 1 commit
  19. 11 Oct, 2012 1 commit
  20. 02 Oct, 2012 1 commit
    • Michael Hanselmann's avatar
      cli: Exit with status 0 for --help · d971402f
      Michael Hanselmann authored
      
      
      This patch is somewhat longer than was anticipated. Before, commands like
      “gnt-instance --help” would exit with the status code 1 (failure). With
      this patch, those commands exits with 0 (success) while unknown commands
      still print the usage screen and exit with status 1.
      
      To achieve this goal without too much ugly code some refactoring on
      cli._ParseArgs was necessary. Printing the version and usage screen was
      separated. At the same time this allows for some unit testing.
      Signed-off-by: default avatarMichael Hanselmann <hansmi@google.com>
      Reviewed-by: default avatarBernardo Dal Seno <bdalseno@google.com>
      d971402f
  21. 28 Sep, 2012 1 commit
  22. 18 Sep, 2012 1 commit
  23. 28 Aug, 2012 2 commits
  24. 23 Aug, 2012 1 commit
    • Iustin Pop's avatar
      Bump pep8 version to 1.2 · 5ae4945a
      Iustin Pop authored
      
      
      Debian Wheezy will ship with this version, and it has many improved checks compared to 0.6, so let's:
      
      - bump version in the docs
      - silence some new checks that are wrong due to our indent=2 instead of 4
      - fix lots of errors in the code where the indentation was wrong by 1
        or 2 spaces
      - fix a few cases of == True, False, None and replace with 'is'
      - re-indent some cases where the code is OK, but pep8 complains
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      5ae4945a
  25. 07 Aug, 2012 1 commit
    • Iustin Pop's avatar
      Add infrastructure for building numeric namefield filters · 6f287cf3
      Iustin Pop authored
      
      
      Currently, all the CLI helpers in qlang.py and cli.py assume that all
      namefields are string, which leads to various breakage in case the're
      actually not.
      
      To improve the flexibility of the helpers, we add a bit of
      infrastructure for accepting so called "numeric" namefields; this is a
      bit of a hack, as a proper fix would actually add QFT_* support to the
      helpers, and case for example the regex/globbing on QFT_TEXT, etc. But
      that's left for (eventual) later improvement.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      6f287cf3
  26. 02 Aug, 2012 1 commit
    • Iustin Pop's avatar
      Fix uses of OpPrereqError without code info · 2cfbc784
      Iustin Pop authored
      
      
      A while back, we did cleanup the code and ensured (manually) that use
      of OpPrereqError includes an errors.ECODE_* field as second
      argument. Since we cannot automate the check for this, it turns out
      that more and more such usage has crept over the years, including in
      the master code (the use on the CLI side is not as important).
      
      Note that this also uncovered a few errors in ovf.py where the errors
      messages were wrongly constructed.
      
      Still looking for a way to automate this check…
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      2cfbc784
  27. 05 Jul, 2012 1 commit
  28. 29 May, 2012 1 commit
  29. 22 May, 2012 3 commits