[
https://issues.apache.org/jira/browse/LIBCLOUD-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280152#comment-13280152
]
Chris Gilmer commented on LIBCLOUD-199:
---------------------------------------
Thanks for merging the timeout part. I'll work on the test case and I think I
should leave out the timeout entirely for auth and set it as None. The
original timeout of 200s is high but I grabbed that value from another
connection timeout that was specified in the code. However, for backwards
compatibility and to ensure I'm not setting a timeout that will break things,
setting the value to None seems the better option. Again, thanks for helping
me with this.
> 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,
> openstack_and_libcloud_connection_timeout_patch_v2.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
