1. 03 Aug, 2011 1 commit
  2. 08 Jul, 2011 1 commit
  3. 24 May, 2011 1 commit
  4. 10 May, 2011 1 commit
  5. 08 Mar, 2011 1 commit
  6. 04 Mar, 2011 1 commit
  7. 17 Feb, 2011 1 commit
  8. 28 Jan, 2011 1 commit
    • Iustin Pop's avatar
      Re-create instance disk symlinks on activate · c417e115
      Iustin Pop authored
      This patch implements recreation of instance disk symlinks when the
      activate-disks operation is run. Until now, it was not possible to
      re-create these symlinks without stopping and starting or migrating an
      instance as the RPC call where this is done was in instance startup
      and migration.
      In order to do this, the blockdev_assemble rpc call needs the disk
      index too, which is added to the protocol. This is a change from 2.3
      and makes instance startup incompatible (FYI).
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
  9. 11 Jan, 2011 1 commit
  10. 06 Jan, 2011 1 commit
    • Iustin Pop's avatar
      RPC: mark jobqueue functions as URGENT · d2cd6944
      Iustin Pop authored
      Recently, we've seen more and more cases of a specific breakage
      pattern in Ganeti: master candidates which are semi-alive (as in, they
      respond to ping, they can complete a TCP/SSL handshake, but otherwise
      the root filesystem is broken) cause lots of confusion within masterd.
      My analysis shows that waiting up to 5 minutes for a reply from such a
      broken master candidate is too long, and this long wait breaks other
      timeouts (e.g. the Luxi timeout), making standard recovery from this
      situation very hard. It's much easier to kill the master daemon, edit
      manually the config file and mark the node as regular, then restart
      the master daemon.
      The proposal is therefore to reduce the timeout for the job queue
      functions to TMO_URGENT (1 minute), which should be more balanced
      between a working but overloaded node and a broken node.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
  11. 17 Dec, 2010 1 commit
  12. 09 Dec, 2010 1 commit
  13. 01 Dec, 2010 1 commit
  14. 03 Nov, 2010 1 commit
  15. 28 Oct, 2010 1 commit
  16. 26 Oct, 2010 2 commits
  17. 21 Oct, 2010 1 commit
  18. 11 Oct, 2010 1 commit
    • Iustin Pop's avatar
      RPC: disable curl's Expect header · 8e29563f
      Iustin Pop authored
      This patch solves the very slow (~8-9 seconds) gnt-instance modify
      behaviour. Well, it solves in general the slow RPC behaviour, but it was
      most visible in that LU.
      It seems that curl's behaviour with regard to file uploads (via PUT) and
      the 'Expect' header are interacting badly with our http server.
      First, our http server doesn't properly handle this header. According to
      RFC 2616:
        Requirements for HTTP/1.1 origin servers: Upon receiving a request
        which includes an Expect request-header field with the "100-continue"
        expectation, an origin server MUST either respond with 100 (Continue)
        status and continue to read from the input stream, or respond with a
        final status code.
      Our server doesn't do this, and hence it triggers this behaviour in curl
      (from the curl FAQ):
        4.16 My HTTP POST or PUT requests are slow!
        libcurl makes all POST and PUT requests (except for POST requests with a
        very tiny request body) use the "Expect: 100-continue" header. This header
        allows the server to deny the operation early so that libcurl can bail out
        already before having to send any data. This is useful in authentication
        cases and others.
        However, many servers don't implement the Expect: stuff properly and if the
        server doesn't respond (positively) within 1 second libcurl will continue
        and send off the data anyway.
        You can disable libcurl's use of the Expect: header the same way you disable
        any header, using -H / CURLOPT_HTTPHEADER, or by forcing it to use HTTP 1.0.
      This behaviour was detected by watching the captured traffic (in non-SSL
      mode), where between the initial HTTP headers (ending with the Expect
      one), there was a ~1-2 second pause until curl was sending the body.
      Properly RTFM-ing would have saved ~1 day of digging around, but hey…
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
  19. 23 Aug, 2010 2 commits
  20. 19 Aug, 2010 2 commits
  21. 18 Aug, 2010 2 commits
  22. 26 Jul, 2010 1 commit
  23. 16 Jul, 2010 1 commit
    • Michael Hanselmann's avatar
      Convert RPC client to PycURL · 33231500
      Michael Hanselmann authored
      Instead of using our custom HTTP client, using PycURL's multi
      interface allows us to get rid of the HTTP client threadpool.
      The majority of the code is still in the ganeti.http.client
      A simple per-thread HTTP client pool gives cURL a chance to
      cache and retain as much information as possible (e.g. SSL certs).
      Unused HTTP clients (e.g. due to removed nodes) are deleted after
      25 requests going through the pool.
      Signed-off-by: default avatarMichael Hanselmann <hansmi@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
  24. 09 Jul, 2010 1 commit
  25. 06 Jul, 2010 1 commit
  26. 23 Jun, 2010 2 commits
  27. 13 Jun, 2010 1 commit
  28. 11 Jun, 2010 1 commit
  29. 04 Jun, 2010 2 commits
  30. 21 May, 2010 1 commit
  31. 23 Apr, 2010 1 commit
  32. 22 Apr, 2010 3 commits