On Wed, Nov 30, 2016 at 08:13:44PM +0100, Mehdi Abaakouk wrote: > > > Le 2016-11-30 19:11, Nadya Shakhat a écrit : > > Hi all, > > > > This one [1] is used very intensively actually :) It is not merged > > because > > we cannot just upgrade python-kafka version because of Monasca. We had > > some > > talks in their channel, but no results still. I suggest the following: > > 1. On our side we will update this change > > 2. I will ping Monasca guys once more and we will proceed with > > discussions > > in the CR > > > > [1] https://review.openstack.org/#/c/332105/ > > Good news, so I should retitle this thread "Can we uncap python-kafka ?"
So right now I think the answer is still no we can't uncap it. To the best of
my knowledge monasca still suffers a substatial performance decrease and the
switch from sync to async producers isn't desired for them.
Joe wrote this all up in:
http://lists.openstack.org/pipermail/openstack-dev/2016-June/098420.html
Unfortunately this comes down to monasca and olso.messaging getting on the same
page with python-kafka. From a requirements POV we really only care about
co-installability, which uncappiugn clearly breaks.
Yours Tony.
signature.asc
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
