OpenStack Compute (Nova)
d4d0eedeb4
This patch makes some code in test_qpid be more explicit about emptying the connection pool. It now ensures that it removes exactly how many connections are in the pool. The previous code made a couple of assumptions. First, it assumed that only one connection was in the pool (which is true, but it's still nice not to make the assumption here in the cleanup code). Second, it assumed that free() returned the number of connections that have been placed in the pool. This is not correct. The result also includes the number of connections that could be created based on the max size of the pool. Use the free_items attribute instead, which gives the exact number of connections that have been put() in the pool. Change-Id: I97378919c2d3e68f224862f07a75529575647163 |
||
|---|---|---|
| bin | ||
| contrib | ||
| doc | ||
| etc/nova | ||
| nova | ||
| plugins/xenserver | ||
| po | ||
| smoketests | ||
| tools | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| Authors | ||
| HACKING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| pylintrc | ||
| README.rst | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
The Choose Your Own Adventure README for Nova
You have come across a cloud computing fabric controller. It has identified itself as "Nova." It is apparent that it maintains compatibility with the popular Amazon EC2 and S3 APIs.
To monitor it from a distance: follow @openstack on twitter.
To tame it for use in your own cloud: read http://docs.openstack.org
To study its anatomy: read http://nova.openstack.org
To dissect it in detail: visit http://github.com/openstack/nova
To taunt it with its weaknesses: use http://bugs.launchpad.net/nova
To watch it: http://jenkins.openstack.org
To hack at it: read HACKING
To cry over its pylint problems: http://jenkins.openstack.org/job/nova-pylint/violations