You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Tomaz Muraus (JIRA)" <ji...@apache.org> on 2012/05/18 22:49:08 UTC

[dev] [jira] [Commented] (LIBCLOUD-199) Add http connection timeout to openstack and libcloud connections

    [ https://issues.apache.org/jira/browse/LIBCLOUD-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279170#comment-13279170 ] 

Tomaz Muraus commented on LIBCLOUD-199:
---------------------------------------

I just checked the code and it looks like httplib in Python 2.5 doesn't support setting a timeout*.

We need to make sure it also works with 2.5. One of the option would be to set a timeout on a socket, but I don't like this approach, because it's a global setting and also affects other socket operations (e.g. when calling deploy node, etc.)

* http://docs.python.org/library/httplib.html
                
> Add http connection timeout to openstack and libcloud connections
> -----------------------------------------------------------------
>
>                 Key: LIBCLOUD-199
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-199
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Compute, Core
>    Affects Versions: 0.8.0, 0.9.1
>            Reporter: Chris Gilmer
>              Labels: auth, authentication, openstack,, timeout,
>             Fix For: 0.8.0, 0.9.1
>
>         Attachments: openstack_and_libcloud_connection_timeout_patch.txt
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Authentication calls to an openstack endpoint (in this case Rackspace) will occasionally create a connection that will stay open indefinitely.  By adding a timeout I can force the connection to close after a few seconds.  That way I can catch this behavior with an exception and log the error before the server request times out.  In this branch I add a timeout kwarg and set a reasonable default of 200 seconds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira