1. 12 Jan, 2011 1 commit
    • Iustin Pop's avatar
      Run pylint over QA code too · 3582eef6
      Iustin Pop authored
      
      
      Right now, the QA code is not covered by pylint, and this shows at
      least one low-impact bug.
      
      This patch does the necessary changes to make QA pylint-clean, and the
      changes the makefile to run pylint for it.
      
      Notable changes:
      
      - qa_utils.GenericQueryTest: randfields was not used at all, and my
        belief is that it was indented to be used in order not to modify the
        input list; so I replaced randfields with fields, so we only shuffle
        the our local copy
      - qa_node.TestOutOfBand was using it's own copy of AcquireNode(), so I
        replaced it with the existing version
      - qa_os: was using 'dir' in a couple of places, replaced with dirname
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      3582eef6
  2. 13 Dec, 2010 2 commits
  3. 09 Dec, 2010 1 commit
    • Guido Trotter's avatar
      Simplify instance rename qa test · e5c2accd
      Guido Trotter authored
      
      
      The current instance rename qa testing function can only perform
      back-and-forth renames, both for command line and rapi. In order to be
      able to perform same-name rename tests we change it to be able to
      perform simple renames, and then we change qa to call it to perform both
      sides of the renaming.
      
      The same change is applied both to the local and the rapi test.
      Signed-off-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      e5c2accd
  4. 08 Dec, 2010 1 commit
  5. 01 Dec, 2010 1 commit
  6. 20 Oct, 2010 1 commit
  7. 07 Oct, 2010 1 commit
    • Iustin Pop's avatar
      Try again to fix the inter-cluster move QA test · 638a7266
      Iustin Pop authored
      
      
      This time, we re-establish the old pri/sec nodes corretly. Unfortunately this
      will require now a 3-node cluster at least for drbd instances, hence it's
      somewhat suboptimal, but… The other option would be to move it simply from p:s
      to s:p and then back to p:s, without involving a third node (for DRBD case),
      but I think that moving it to a completely separate node is slightly better for
      testing.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      638a7266
  8. 06 Oct, 2010 1 commit
    • Iustin Pop's avatar
      QA: Fix instance move tests · 677e16eb
      Iustin Pop authored
      
      
      The instance move tests were moving the instance from node pair (A,_) to
      (B, A), and left it there. This patch makes sure that the first step
      moves the instance to (B,A) but the second one back to (A,B), so that
      the instance is left on the same primary node.
      
      The original secondary node is lost though, if I read the code
      correctly.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      677e16eb
  9. 05 Oct, 2010 1 commit
  10. 16 Sep, 2010 2 commits
  11. 18 Aug, 2010 1 commit
  12. 10 Aug, 2010 1 commit
  13. 29 Jul, 2010 1 commit
  14. 08 Jul, 2010 1 commit
  15. 01 Jul, 2010 1 commit
    • Michael Hanselmann's avatar
      RAPI client: Switch to pycURL · 2a7c3583
      Michael Hanselmann authored
      
      
      Currently the RAPI client uses the urllib2 and httplib modules from
      Python's standard library. They're used with pyOpenSSL in a very fragile
      way, and there are known issues when receiving large responses from a RAPI
      server.
      
      By switching to PycURL we leverage the power and stability of the
      widely-used curl library (libcurl). This brings us much more flexibility
      than before, and timeouts were easily implemented (something that would
      have involved a lot of work with the built-in modules).
      
      There's one small drawback: Programs using libcurl have to call
      curl_global_init(3) (available as pycurl.global_init) while exactly one
      thread is running (e.g. before other threads) and are supposed to call
      curl_global_cleanup(3) (available as pycurl.global_cleanup) upon exiting.
      See the manpages for details. A decorator is provided to simplify this.
      
      Unittests for the new code are provided, increasing the test coverage of
      the RAPI client from 74% to 89%.
      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>
      2a7c3583
  16. 14 Jun, 2010 1 commit
  17. 18 May, 2010 1 commit
  18. 13 May, 2010 1 commit
  19. 11 May, 2010 1 commit
  20. 05 May, 2010 2 commits
  21. 12 Apr, 2010 1 commit
  22. 26 Mar, 2010 1 commit
  23. 25 Sep, 2009 1 commit
  24. 24 Jul, 2009 2 commits
  25. 10 Feb, 2009 1 commit
  26. 06 Feb, 2009 1 commit
    • Iustin Pop's avatar
      QA: switch RAPI to https · 49b1d36e
      Iustin Pop authored
      Since we by default now use SSL for RAPI, we need to switch the QA
      tests to SSL too.
      
      Reviewed-by: amishchenko
      49b1d36e
  27. 05 Feb, 2009 1 commit
    • Iustin Pop's avatar
      Revive RAPI QA tests for 2.0-style RAPI · a5b9d725
      Iustin Pop authored
      This patch fixes the RAPI QA tests to work with today's RAPI code and
      also does some other minor improvements:
        - QA: only create the cluster if so configured (‘create-cluster’ key),
          this allows running parts of the QA suite against existing clusters
        - export the “hvparams” for instances in RAPI
      
      Reviewed-by: imsnah
      a5b9d725
  28. 15 Aug, 2008 2 commits
  29. 15 Jul, 2008 1 commit