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
We do not need tox_install.sh, pip can handle constraints itself
and install the project correctly. Thus update tox.ini and remove
the now obsolete tools/tox_install.sh file.
This follows https://review.openstack.org/#/c/508061 to remove
tools/tox_install.sh.
Change-Id: Ifaaf656effff20ef08214f111645a3b5fc8b4d28
Oslo.messaging uses a single bindep.txt to define common
and driver dependencies. The bindep_profile is used by the
bindep role to select the driver specific packages.
This patch:
* Add bindep_profile var to jobs
* Add kafka dependencies
* update test-setup for use by amqp1
Depends-On: I6beb7b07a7dbc345e63e758ebbc86400e0ee16d3
Change-Id: Ib552152e841a9fc0bffdcb7c3f7bc75613d0ed62
there's only one scenario where the generator actually needs to be
forced into a list. don't waste time doing something unnecessary.
Change-Id: Iec897b1f6fed3d88b798eb673779e7c68ff930ec
groupby requires items to be sorted as it's clumping consecutive
items together. also, just use itemgetter instead of lambda
Change-Id: I1676fc60ebc2c9ff03ea00cc67061fdfb3b50868
Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.
Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.
This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
.
Change-Id: Icb7de5c9020c3543c218744c0dc75e758f0abb43
heartbeat_check in kombu.connection is not reraising exceptions as
exceptions.OperationalError, and the socket timeout during the heartbeat
check is really an issue seen in the field when a node goes down; the
heartbeat thread just tries again and again to deal with it, without
success.
Change-Id: I26dbdb18a7e64946db2cba676764ff2d428c7897
Closes-Bug: #1657444
