Merge lp:~soren/nova/rpc-call-concurrency into lp:~hudson-openstack/nova/trunk
Proposed by
Soren Hansen
Status: | Merged |
---|---|
Approved by: | Devin Carlen |
Approved revision: | 664 |
Merged at revision: | 664 |
Proposed branch: | lp:~soren/nova/rpc-call-concurrency |
Merge into: | lp:~hudson-openstack/nova/trunk |
Diff against target: |
39 lines (+4/-4) 1 file modified
nova/rpc.py (+4/-4) |
To merge this branch: | bzr merge lp:~soren/nova/rpc-call-concurrency |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Devin Carlen (community) | Approve | ||
Jay Pipes (community) | Approve | ||
Review via email: mp+49373@code.launchpad.net |
Commit message
Create a new AMQP connection by default.
Description of the change
It turns out that rpc.call has the same problem as rpc.cast. This time I saw it
when two clients attempted to call GetConsoleOutput at the same time.
I changed new's default to True and changed everywhere else to rely on the default.
I left the code implementing the singleton in, so that if we switch to another amqp
library that deals better with this, we can just change the default again.
To post a comment you must log in.
I'm not sure why there is even an option to set instance(False), but that's a separate gripe. This fixes the problem.