To prevent left over TCP connections from keystoneclient not correctly
cleaning up we shouldn't use a connection pool. This is not ideal but it
was a relatively new addition so shouldn't affect performance.
When we are able to find a long term solution to keystoneclient's other
problems we can move back to using a connection pool.
Reviewed: https:/ /review. openstack. org/82007 /git.openstack. org/cgit/ openstack/ python- keystoneclient/ commit/ ?id=6d1f907061c 85c6a4550379eab 3c11cdcc45def4
Committed: https:/
Submitter: Jenkins
Branch: master
commit 6d1f907061c85c6 a4550379eab3c11 cdcc45def4
Author: Jamie Lennox <email address hidden>
Date: Fri Mar 21 16:59:09 2014 +1000
Don't use a connection pool unless provided
To prevent left over TCP connections from keystoneclient not correctly
cleaning up we shouldn't use a connection pool. This is not ideal but it
was a relatively new addition so shouldn't affect performance.
When we are able to find a long term solution to keystoneclient's other
problems we can move back to using a connection pool.
Change-Id: I45678ef89b88ee a90ea04de1e3170 f584b51fd8f
Closes-Bug: #1282089