1. 03 Sep, 2012 2 commits
    • Iustin Pop's avatar
      Fix warnings/errors with newer pylint · 8ad0da1e
      Iustin Pop authored
      
      
      To help developing Ganeti on newer distributions, let's try to fix
      pylint warnings/errors. I'm using pylint from current Debian wheezy:
      pylint 0.25.1, astng 0.23.1, common 0.58.0, and we have 3 things that
      needs fixing.
      
      First, a really wide "except", with the silencing in the wrong
      place. I'm not sure why this doesn't have "except Exception", so let's
      add it. However, pylint still complains about "Catching too general
      exception", even though we do want to catch both system and our
      exception, so let's add a silence for W0703. It's true that we
      shouldn't catch KeyboardInterrupt and friends, but that should be
      cleaned up on the master branch.
      
      Second, pylint complains about "redefining name builtin tuple",
      because we do some pattern matching in the except blocks in
      netutils. This seems to be a false positive, but let's clean the code
      around this.
      
      And finally, type inference again goes bad, so let's silence E1103
      with its "boolean doesn't have 'get' method".
      
      After this, I can run "make lint", and by extension "make
      commit-check" on Debian Wheezy, yay! We might be able to bump our
      required pylint versions to something not ancient…
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      8ad0da1e
    • Iustin Pop's avatar
      Fix decorator uses which crash newer pylint · fc3f75dd
      Iustin Pop authored
      
      
      Pylint version:
      
        pylint 0.25.1,
        astng 0.23.1, common 0.58.0
      
      crashes when passing the fully-qualified decorator name with:
      
        File "/usr/lib/pymodules/python2.7/pylint/checkers/base.py", line 161, in visit_function
          if not redefined_by_decorator(node):
        File "/usr/lib/pymodules/python2.7/pylint/checkers/base.py", line 116, in redefined_by_decorator
          decorator.expr.name == node.name):
      AttributeError: 'Getattr' object has no attribute 'name'
      
      I found out that simply using a shortened name will 'fix' this issue,
      so let's do this to allow running newer pylint versions.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      fc3f75dd
  2. 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
  3. 07 Aug, 2012 1 commit
    • Iustin Pop's avatar
      Switch job IDs to numeric · 76b62028
      Iustin Pop authored
      
      
      This has been a long-standing cleanup item, which we've always
      refrained from doing due to the high estimated effort needed.
      
      In reality, it turned out that after some infrastructure improvements
      (the previous patches), the actual job queue-related changes are quite
      small.
      
      We will need to update the NEWS file later, but so far the RAPI
      documentation doesn't mention that the job ID is a string (it only
      says it is "a number"), so it doesn't look like it needs update.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      76b62028
  4. 26 Jul, 2012 1 commit
  5. 25 Jul, 2012 1 commit
  6. 19 Jul, 2012 2 commits
  7. 11 Jul, 2012 1 commit
  8. 05 Jul, 2012 1 commit
  9. 27 Jun, 2012 1 commit
  10. 26 Jun, 2012 2 commits
  11. 19 Jun, 2012 1 commit
  12. 15 Jun, 2012 3 commits
  13. 12 Jun, 2012 1 commit
  14. 08 Jun, 2012 1 commit
  15. 07 Jun, 2012 2 commits
  16. 05 Jun, 2012 4 commits
    • Michael Hanselmann's avatar
      QA: Add default setting for tests · 69a15dd7
      Michael Hanselmann authored
      Commit 1010ec70
      
       enabled all tests by default. In some scenarios where
      the configuration is static one may not want newly added tests to be
      run.
      Signed-off-by: default avatarMichael Hanselmann <hansmi@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      (cherry picked from commit 59a8fe48)
      69a15dd7
    • Iustin Pop's avatar
      QA: add toggle for fewer common instance tests · b498540e
      Iustin Pop authored
      
      
      Currently, the "common" instance tests (shutdown, rapi stopped
      console, stopped modify, startup, rapi shutdown, rapi startup, list,
      info, modify, rapi modify , console, rapi console, reinstall, rename,
      rapi rename, rename and back, rapi rename and back, grow disk, reboot,
      tags, cluster verify, rapi test instance, node list, job list) are run
      4 times:
      
      - one time for plain instance created via RAPI, using client
      - one time for plain instance created via RAPI, without client
      - one time for plain instance created via gnt-instance
      - one time for DRBD instance created via gnt-instance
      
      This makes the QA long, and is over-doing it (for non-full QAs): an
      instance created via RAPI (either client) and via gnt-instance should
      have the same parameters, but our duplicate tests do not ensure that,
      just that instances behave OK.
      
      This patch adds a toggle so that we can skip the common tests for
      RAPI-created instances; the creation/deletion is still performed, but
      all the other operations are not. This reduces the time of a "quick"
      QA by ~20% (1h:15m → 1h).
      
      The common tests will still be run (unconditionally) for
      gnt-instance-created instances.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      b498540e
    • Iustin Pop's avatar
      QA: stop logging SSH arguments for each invocation · 710bc88c
      Iustin Pop authored
      
      
      Currently, this is how the QA log looks like:
      
      Command: ssh -oEscapeChar=none -oBatchMode=yes -l root -t -oStrictHostKeyChecking=yes -oClearAllForwardings=yes -oForwardAgent=yes -oControlPath=/tmp/ganeti-qa-multiplexer.DMzkuH -oControlMaster=no node14 exit
      Command: ssh -oEscapeChar=none -oBatchMode=yes -l root -t -oStrictHostKeyChecking=yes -oClearAllForwardings=yes -oForwardAgent=yes node8 exit
      Command: ssh -oEscapeChar=none -oBatchMode=yes -l root -t -oStrictHostKeyChecking=yes -oClearAllForwardings=yes -oForwardAgent=yes node18 exit
      
      And these arguments are repeated over and over. This patch proposes to
      log once the arguments, at the beginning of the QA (so that the SSH
      commands can be reproduced, if needed) and then drop them from the
      log. The new output looks like:
      
      SSH command for primary node: ssh -oEscapeChar=none -oBatchMode=yes -lroot -oStrictHostKeyChecking=yes -oClearAllForwardings=yes -oForwardAgent=yes -oControlPath=/tmp/ganeti-qa-multiplexer.24lgrK -oControlMaster=no node14
      SSH command for other nodes: ssh -oEscapeChar=none -oBatchMode=yes -lroot -oStrictHostKeyChecking=yes -oClearAllForwardings=yes -oForwardAgent=yes NODE
      (the above are the informational messages about parameters, then)
      Command: ssh node14 exit
      Command: ssh node8 exit
      Command: ssh node18 exit
      
      This makes the QA log much more readable, by dropping unneeded clutter
      (look how long the original lines were), and hopefully also a bit
      smaller (current QA log is > 100MB of text output).
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarBernardo Dal Seno <bdalseno@google.com>
      710bc88c
    • Iustin Pop's avatar
      Switch QA to tty-less mode · f14a8b15
      Iustin Pop authored
      
      
      This makes ssh generate much less noise when QA is run itself without
      a tty, as otherwise we get thousands of lines of:
      
        Pseudo-terminal will not be allocated because stdin is not a terminal.
      
      in the QA logs (which are already big enough).
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      f14a8b15
  17. 15 May, 2012 1 commit
  18. 14 May, 2012 2 commits
  19. 10 May, 2012 3 commits
  20. 04 May, 2012 3 commits
  21. 26 Apr, 2012 1 commit
  22. 23 Apr, 2012 1 commit
  23. 20 Apr, 2012 1 commit
  24. 19 Apr, 2012 1 commit
  25. 18 Apr, 2012 1 commit
  26. 13 Apr, 2012 1 commit