1. 26 Mar, 2015 1 commit
  2. 12 Sep, 2014 1 commit
  3. 22 May, 2014 1 commit
  4. 09 Jan, 2014 1 commit
  5. 14 Nov, 2013 1 commit
  6. 11 Nov, 2013 1 commit
  7. 29 Oct, 2013 1 commit
  8. 20 Sep, 2013 2 commits
  9. 29 Jul, 2013 1 commit
  10. 24 Jul, 2013 1 commit
  11. 29 May, 2013 1 commit
  12. 02 May, 2013 1 commit
  13. 17 Apr, 2013 1 commit
  14. 27 Nov, 2012 1 commit
  15. 20 Nov, 2012 1 commit
  16. 03 Sep, 2012 1 commit
    • 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>
  17. 30 Aug, 2011 1 commit
  18. 05 Oct, 2010 1 commit
  19. 01 Sep, 2010 1 commit
  20. 30 Jul, 2010 2 commits
  21. 29 Jul, 2010 1 commit
    • Michael Hanselmann's avatar
      workerpool: Change signature of AddTask function to not use *args · b2e8a4d9
      Michael Hanselmann authored
      By changing it to a normal parameter, which must be a sequence, we can
      start using keyword parameters.
      Before this patch all arguments to “AddTask(self, *args)” were passed as
      arguments to the worker's “RunTask” method. Priorities, which should be
      optional and will be implemented in a future patch, must be passed as a keyword
      parameter. This means “*args” can no longer be used as one can't combine *args
      and keyword parameters in a clean way:
      >>> def f(name=None, *args):
      ...   print "%r, %r" % (args, name)
      >>> f("p1", "p2", "p3", name="thename")
      Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       TypeError: f() got multiple values for keyword argument 'name'
      Signed-off-by: default avatarMichael Hanselmann <hansmi@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
  22. 12 Jul, 2010 1 commit
  23. 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
      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>
  24. 01 Jun, 2010 1 commit
  25. 18 May, 2010 1 commit
    • Michael Hanselmann's avatar
      Add tool to move instances between clusters · 6bf273d5
      Michael Hanselmann authored
      This is a first version of the instance move tool and it supports moving
      1..N instances from one cluster to another. When moving a single instance,
      the instance can be renamed, allowing for moves within the same cluster
      (not really useful in practice, but good for testing). Documentation is
      updated to describe this new tool and its usage.
      The “move-instance” tool uses the workerpool to support parallel moves of
      instances. Supporting them was simple as threads were required anyway due
      to the synchronous RAPI client.
      Signed-off-by: default avatarMichael Hanselmann <hansmi@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>