Pyngus 2.0 includes a new API for configuring SASL credentials.
Previous versions of Pyngus did not provide this API - the driver had
to invoke Proton APIs in order to configure user credentials. Moving
to the Pyngus API will preserve compatibility with older versions of
Proton, since the next release of Proton wil be changing its SASL API.
Pyngus 2.0 also adds strict enforcement of callback re-entrancy
constrants. This patch fixes some bad driver reentrancy violations.
Closes-bug: #1473515
Change-Id: Iddccefd3ee3c9092c086fc54e3810f78d5df9338
Add the directive to include the configuration options to the library
documentation.
Depends-On: I549c8db98bf548dd0a7e8869a57301fa4096f78c
(feature change in oslo.config)
Depends-On: I89e3e4fd41ed4c989c2dd4c9cd1d7b7e806fa15a
(global requirements change to update oslo.config version)
Change-Id: Ibec7071027fc33374a73abc30f8f672380bae6ea
When logging a message, any secrets and passwords should be masked. This
uses oslo_utils.strutils to mask any passwords that are to be logged.
Change-Id: I263d44c0f2e900c5f6e210cbd7ec56e48d0d5bb2
Closes-Bug: #1487038
Add hacking rule borrowed from keystone to make sure
we don't regress and fix all the issues found by the
hacking check.
Change-Id: I41635fdd83c3e04d04f9849a72c49ccb5ac42875
- added config options to set debug level
- added config options to show proceed messages per second on rpc-server
- added config options to select executor for rpc-server
- added config options to select call or cast mesages for rpc-client
Usage section updated
Change-Id: Ieadbc600f556ca5eb43b05abec69315b46023662
Pushing upstream a patch we used for debugging several rabbit
issues in an old fork of oslo.messaging. Use the new
LOG.trace() functionality from oslo.log 1.8.4
Co-Authored-by: Bogdan Dobrelya <bdobrelya@mirantis.com>
Co-Authored-by: Alexei Kornienko <akornienko@mirantis.com>
Co-Authored-by: Oleksii Zamiatin <ozamiatin@mirantis.com>
Change-Id: I0033bba47002f9685479bbd55b29746a06563a51
Changes introduced in:
I0fc1717e3118bc1cd7b9cd0ccc072251cfb2c038
are causing Neutron to fail as summarized by Doug in:
http://markmail.org/message/2xlclp7gqnqpkted
So we should log warnings instead and make sure we
find which projects are affected (using logstash) and
fix them. Once we do that, then we can switch this
back to raise RuntimeError(s)
Change-Id: I9dce272246b89f3ec63aefcf11d385fd2d21da6e
Message will not be handle after acknowledge failure, but it will store
in cache to prohibit handle duplicate message by skipping it.
So a message can be missed if client receive a duplicate message.
Fix this problem by store the message info in cache after a successfuly
message acknowledgment.
Change-Id: I907a58199eeadac22c31490111ec51ee6dd874d5
listen_for_notifications() accepts `pool` argument in driver classes, so
we should add this argument to the base abstract class as well.
Change-Id: Ic52924bb66c8a89cdc90102b1171427806e9a823
It's documented, the application consumer must not use wait before stop.
but this is not enforced, so enforce it
Also the code assume start/stop/wait are called from the same thread,
but this is not enforced, so enforce it.
A common broken usage is:
server = oslo.messaging.get_rpc_server(..., executor='eventlet')
t = threading.Thread(target=server.start)
t.daemon = True
t.start()
...foobar code...
server.stop()
server.wait()
With monkey patching, start() will do a context switch and then stop()
is called but start is unfinished, that can cause unexpected behavior.
This patch fixes these issues by making all of this explicit.
Closes-bug: #1465850
Closes-bug: #1466001
Change-Id: I0fc1717e3118bc1cd7b9cd0ccc072251cfb2c038
