Move the requirements for the optional drivers to
test-requirements.txt and setup.cfg. The default rabbitmq driver's
dependencies should be the only hard requirements for the base
package.
Leaving ZeroMQ deps unchanged for now as it will be removed in Stein
Change-Id: I19dd699ccf87e43202ccefb99258fbaa9ea17b7e
Set the default python to python3 except for the py27 specific test
environments. Set Python 2.7 as the python version to use for these
tests.
Temporarily ignore optional driver requirements for now. This will be
addressed in a later update.
Change-Id: Iea8e48b72234bb9a580f2345396cf60fe2022618
Fix the lower constraints to match the expected values.
We will manage the eventlet version using constraints now. See the
thread starting at
http://lists.openstack.org/pipermail/openstack-dev/2018-April/129096.html
for more details.
Change-Id: I61d5680182c53774713ee83808b1f6e7a4fba9ff
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This reverts commit c881baed29db49c5710795496cb07907e35ceaba.
Eventhough batch_size is set, rabbitMQ prefetch count is not changed
at the first time of connection creation. It works only connection reset
cases(i.e. rabbitMQ restart). So this patch can not fix original issue
https://bugs.launchpad.net/ceilometer/+bug/1551667
Moreover, it makes another bug that messages of sameple queues are not
consumed properly. So revert it.
Change-Id: Ia8ebee8e2a670e46b6a68859bc30e717bd56ed7e
Signed-off-by: Wonil Choi <wonil22.choi@samsung.com>
Closes-bug: 1759755
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I8991c2ab1c880c401fd807e38565258403af05e8
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
At the Rocky PTG the Oslo team decided to once again deprecate and
remove the ZMQ driver. This is the first part of doing that, which
removes the unit tests and extra functional test jobs, which are
failing.
Change-Id: Ia02adf122d2d4ff281e7c9fd3dff8894da241925
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
It is recommended that all users of the Pika driver transition to
using the Rabbit driver instead. Typically this is done by changing
the prefix of the transport_url configuration option from "pika://..."
to "rabbit://...". There are no changes required to the RabbitMQ
server configuration.
Change-Id: I52ea5ccb7e7c247abd95e2d8d50dac4c4ad11246
Closes-Bug: #1744741
This merely provides a restart() method that passes through to the existing
restart() method on the StopWatch used as the internal for DecayingTimer so
that we can reset it.
Change-Id: Ie6b607ec588db94e2c768bd22ae736a05ab484c1
The pip_missing_reqs tool is abandoned and now incompatible with
recent versions of pip. It has been supplanted by the pip_check_reqs
tool which provides the same pip-missing-reqs entrypoint (plus some
others), effectively renamed.
This is the same as https://review.openstack.org/#/c/453208/ and
the commit message above is copied here.
Change-Id: Ibd02fda9c3f96034c96c7bf4abb9248219e0662c
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I9cb1cce40e473d854a9fe6a640c8fc5036288cbd
* telemetry integration tests run in tempest-venv so plugin
needs to be installed in the same venv. devstack plugin installs
the plugin all-plugin venv so tests are not discovered by tempest.
In order to fix the same we need to use TEMPEST_PLUGINS vars for
the same.
* telemetry integration tests are dependent on heat-tempest-plugin
so we need to add that to the required projects.
Change-Id: Icab1e53d20bb7c95c232a4512e83905dcca7c599
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I42269c34d2c9647d827a88a9ae8f1fd79dffac98
This patch changes the default driver behavior to synchronously
commit messages following consumer poll. A configuration option
will enable the auto commit for asynchronous commit if desired.
Depends-On: I5b4f01c928373cac530aa6877a34c684577bc64e
Change-Id: I92a3dc95c5d424aa722138195fef5a855a66b31d
Emulate vhost support by adding the virtual host name to the
topic created on the kafka server. Also, update connection
management for producer/consumer.
This patch:
* updates target to topic generation
* add consumer and producer connection classes
* remove connection pool
* update driver test
Change-Id: Idd164444c04e9f465a43ee909af840a41bb090c0
This patch addresses a number of issues that prevented the functional
tests from running. The functional tests now execute and can complete
succesfully. At times, the test will fail (noticiably in CI) indicating
an underlying issue with consumer interaction with the kafka server.
It would be beneficial to merge this patch as it provides repeatability
and visibility for driver-kafka server integration to facilitate
additional debugging and testing.
This patch:
* removes use of deprecated get_transport
* override consumer_group for each test
* changed to synchronous send
* update to kafka 1.0.0 server
Depends-On: Ib552152e841a9fc0bffdcb7c3f7bc75613d0ed62
Change-Id: I7009a3b96ee250c177c10f5121eb73d908747a52
