The release notes script expects to be able to find the link
to the bug tracker in the README.rst, so update the format
to match what is expected by that script and used by the other
projects.
Change-Id: Ifd20c23eb7ba69090cda2e5ecf206f15e81a8254
The previous attempt to do this in
Ide40b293c9b9c76aae094950720cead4179ea883 created a new module
oslo/messaging/notify/_impl_test.py which imported the symbols from
oslo_messaging/notify/_impl_test.py. That doesn't actually work, because
the functions to reset the notifications modify the copy of the symbol
in the oslo_messaging package, but the designate tests are still looking
at the copy in oslo/messaging.
This change imports a copy of the module from oslo_messaging in the
oslo/messaging namespace to make certain that the same module object,
and therefore the same global data structure, is used no matter which
path the code is accessed.
The designate team still needs to fix their fixture, but this will let
us release oslo.messaging without breaking their tests in the mean time.
Partial-Bug: #1412812
Change-Id: I629ac57ae1e74bb07e5e98ee2fbc21f8421c3c24
This removes the functionnal tests from the legacy
directory and run the ones in the new directory with tox.
Change-Id: Ibbfd6c946e25435ff37e459bf5e82565a1e21778
A number of the ZMQ test cases shared the same setUp method; refactor
and introduce a base test case class to share this code across all
appropriate ZMQ test cases.
Change-Id: I59300464af001c343efcd4f3f33d34c972da2b87
This patch exposes some private symbols used by the tests in nova and
heat.
Change-Id: Ide40b293c9b9c76aae094950720cead4179ea883
Partial-Bug: #1412812
Partial-Bug: #1412841
The Notification Listener Tracker class is not threadsafe,
so when a test stop an already stopped listener this one
can be restarted, due to concurrency access of the threads list and
concurrency execution of the start/stop/wait method of the notification
listener.
This result of a lockup of the test or a listener can continue to
got unepxected message.
This change fixes that by never stop the tread with the tracker callback
but only manually with the test.
This test also rename some 'Listener' to 'Server', to not mismatch
the driver listener from the notification listener.
Closes-bug: #1410902
Change-Id: I4777c7dd0ba71c61850d36641e85f33f9461e9c1
I516c580faef04f55fcc095d22adbfabcfa001da7 have been
merged just after the namespace change patch, but change only
the old test directory.
So reapply I516c580faef04f55fcc095d22adbfabcfa001da7 to the
new test directory.
Change-Id: I5cd7d7b6c507967e7fb4744012b2ad215c4f1ad3
Closes-Bug: #1409899
This properly deploys the oslo.messaging package may resolve
sphinx build errors for projects which have not yet
upgraded to oslo_messaging.
Change-Id: I4db750fb2356ebf44a8fccf7c422b474fefec0ee
Some of the heat unit tests import code from a private part of
oslo.messaging. With the namespace package change, that private part was
no longer being exposed. This change introduces the needed module so we
can release oslo.messaging with the namespace changes without breaking
heat, to give the heat team time to update their tests.
Partial-Bug: #1410196
Change-Id: Ib3ea106646f75b17665877b08ccbd382c5698714
With eventlet 0.16, it becomes possible to run Oslo Messaging tests on
Python 3 with eventlet.
This change ports the zmq driver to Python 3:
* encode the topic explicitly to UTF-8
* use a list comprehension instead of map() to also get a list
on Python 3 (not a generator)
The following eventlet change is needed to run tests:
https://github.com/eventlet/eventlet/pull/187
Related eventlet issue:
https://github.com/eventlet/eventlet/issues/185
I will propose a different change to enable tests with eventlet enabled
when a release of eventlet including this fix will be available.
Change-Id: Ic8fec515cfa757e08ffb9604e3bfb2e87d08f3d8
Tests now ensure that eventlet monkey patching is enabled before
importing the qpid module, otherwise qpid will hang.
Currently, qpid randomly hangs, depending on the order of the Python
module import, which probably depends on the local file modification
time.
Closes-Bug: #1409899
Change-Id: I516c580faef04f55fcc095d22adbfabcfa001da7
Move the public API out of oslo.messaging to oslo_messaging. Retain
the ability to import from the old namespace package for backwards
compatibility for this release cycle.
bp/drop-namespace-packages
Co-authored-by: Mehdi Abaakouk <mehdi.abaakouk@enovance.com>
Change-Id: Ia562010c152a214f1c0fed767c82022c7c2c52e7
When the duration of the timeout timer used in the rabbit driver.is
None and we want that the timer return a maximum of N secs it return None
(infinite) instead of N.
This change fixes that.
Closes-bug: #1408370
Change-Id: I7f4cb3075f776c63aa7dc497173677f92b68c16d
oslo.utils.strutils.mask_password take too much time on
big payload (nova-conductor can receive payload ~ 66k in
largeops jobs for example).
This change removes this logging until we make mask_password
more efficient or we have a smarted the oslo.messaging logging to
not log everything.
Change-Id: Ib1f1d70c5cb820e8ff2de10e6064037808ea1f3a
Closes-bug: #1408362
* add i18n support to some exception messages
* remove the return value of DecayingTimer.start()
Relates to review: I898a236a384b3466147026abc7a1ee21801e8ca1
Change-Id: I7adf5478732f1f46db1009b059b66ff8af6ecdc3
The concurrent.futures module is one of the ways
that async activities can be done in the future,
so we should try to work on getting to that future
by using more futures. To enable this (as well as
to enable getting off eventlet), add a thread pool
based executor which will process incoming messages
using the pool.
Also begins adding according docs as well for the
different types of executors that are available.
Change-Id: I1482fd70abbf69f4e2994597c5e95d91fecb815e
Sanitizes password fields found in lists of dicts for messages
before logging.
This change uses oslo.utils.strutils.mask_password to do it.
Change-Id: I7cd1e53e2ced7ebf9c5942b7a0dbbeb991acab4d
Closes-Bug: #1268459
