1. 21 Dec, 2012 1 commit
  2. 18 Dec, 2012 1 commit
  3. 20 Nov, 2012 1 commit
  4. 25 Sep, 2012 1 commit
  5. 18 Sep, 2012 1 commit
  6. 12 Sep, 2012 4 commits
  7. 28 Aug, 2012 1 commit
  8. 28 Jun, 2012 1 commit
  9. 10 May, 2012 2 commits
  10. 28 Mar, 2012 1 commit
  11. 21 Feb, 2012 1 commit
  12. 17 Jan, 2012 1 commit
    • Iustin Pop's avatar
      Accept both PUT and POST in noded · 7530364d
      Iustin Pop authored
      
      
      Currently, noded requires PUT, even though the semantics of the RPC
      calls do not match a PUT. We change the code accept both PUT and POST,
      with the intention to remove the PUT support in a later version.
      
      On the client side, the RPC code is changed to send POST requests.
      
      Additionally, we add a message to the HttpBadRequest exception to make
      clear the failure mode (not seeing any error message was what made me
      send this patch…). This was the only description-less use of this
      exception, by the way.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      7530364d
  13. 06 Jan, 2012 7 commits
  14. 05 Jan, 2012 4 commits
  15. 21 Dec, 2011 3 commits
    • Iustin Pop's avatar
      Change internal RPC client body values · d9de612c
      Iustin Pop authored
      
      
      Currently, all RPC payloads sent by the client to the remote node
      daemons must be identical, due to how the data is passed
      internally. This is deficient in both use (from the programmer's point
      of view) and from the network traffic (cluster verify/disk data
      gathering has a total payload which is O(n²) in size of the nodes
      being queried, instead of O(n)).
      
      This patch changes the RPC internals so that we always pass
      dictionaries indexed by target node name. For the default use case,
      when the payload is identical, we only serialise the payload once, so
      the extra overhead is just a dict with the node names and values all
      pointing to the same object. For different payloads, we will encode
      the body multiple times, but hopefully the bodies will be smaller.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      d9de612c
    • Iustin Pop's avatar
      Extend RPC definition change with another parameter · 60154921
      Iustin Pop authored
      
      
      This will be used in a later patch for parameter pre-processing. For
      now we just add the parameter as 'None' and add a consistency check
      for the parameter definitions.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      60154921
    • Michael Hanselmann's avatar
      serializer: Remove JSON indentation and dict key sorting · a182a3ed
      Michael Hanselmann authored
      
      
      Serializing to JSON using “simplejson” is significantly slower when
      indentation and/or sorting of dictionary keys is used. In simplejson 1.x
      the difference isn't that big, but with simplejson 2.x the difference
      can be up to a factor of 7.5. The reason is that the latter no longer
      uses C functions when sorting or indentation is used.
      
      With this patch we revert everything to simplejson's defaults, which
      should provide us with the best performance available.
      Signed-off-by: default avatarMichael Hanselmann <hansmi@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      a182a3ed
  16. 08 Nov, 2011 1 commit
  17. 07 Nov, 2011 3 commits
  18. 04 Nov, 2011 1 commit
  19. 03 Nov, 2011 1 commit
    • Michael Hanselmann's avatar
      Show RPC calls from config in lock monitor · b2acdbdc
      Michael Hanselmann authored
      
      
      With this patch all RPC calls at runtime of masterd will show up in the
      lock monitor. There is a chicken-and-egg issue with initializing the
      configuration with a context since the lock manager, containing the
      monitor, requires the configuration. This is worked around by setting
      the config's context only once the lock monitor is available.
      
      Example:
      rpc/node19.example.com/write_ssconf_files  Jq9/Job32/N_SET_PARAMjobqueue_update  Jq2/Job27/C_VERIFY_CONFIG
      Signed-off-by: default avatarMichael Hanselmann <hansmi@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      b2acdbdc
  20. 01 Nov, 2011 2 commits
  21. 28 Oct, 2011 1 commit
  22. 27 Oct, 2011 1 commit