[openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

Tony Breeds tony at bakeyournoodle.com
Fri Dec 2 04:26:40 UTC 2016

On Thu, Dec 01, 2016 at 08:41:54AM -0800, Joshua Harlow wrote:
> Keen, Joe wrote:
> > I¹ll look into testing the newest version of kafka-python and see if it
> > meets our needs.  If it still isn¹t stable and performant enough what are
> > the available options?
> Fix the kafka-python library or fix monasca; those seem to be the options to
> me :)

Yup, Also worth including fix oslo.messaging to meet monasca's needs.  But
*something* needs fixing.
> I'd also not like to block the rest of the world (from using newer versions
> of kafka-python) during this as well. But then this may diverge/expand into
> a discussion we had a few summits ago, about getting rid of
> co-instability...

lalalalala not listening ;P

Less flippantly, there are a couple of ways to do this but IMO they're not in
the best interest of OpenStack.

1. vendor/fork python-kafka 0.X
2. Stop the proposal-bot from syncing with monasca, thereby allowing it to use
python-kafka 0.X at the expense of co-installability.

Fortunately either option is easy to reverse once the underlying issue is fixed.

Yours Tony.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161202/a99d2f9f/attachment.pgp>

More information about the OpenStack-dev mailing list