[openstack-dev] [oslo] Should we drop kafka driver ?

Elancheran Subramanian esubramanian at godaddy.com
Wed Nov 30 23:59:59 UTC 2016

On 11/30/16, 4:45 PM, "Joshua Harlow" <harlowja at fastmail.com> wrote:

>Mehdi Abaakouk wrote:
>> Hi,
>> I think my subject is clear :) , but I will add some facts that can help
>> to the decision:
>> * It uses only deprecated python-kafka API [1] [2]
>> * It's not python3 compatible [3]
>> * We still don't have kafka testing in gate
>> So, one year after the driver introduction, this one is still in bad 
>> and doesn't match the requirements [4].
>> These reviews looks abandoned/outdated/unmaintained:
>> [1] https://review.openstack.org/#/c/297994/ [2]
>> https://review.openstack.org/#/c/332105/
>> Other links:
>> [3] https://review.openstack.org/#/c/404802/
>> [4]
>> And of course, we will not drop the code now, but just deprecate it for
>> removal.
>> Cheers,
>IMHO, not just yet, dims and I have been trying to use this driver 
>recently (for notifications only in my case) and I am more than willing 
>to try to get the changes needed to get this into a healthy state (from 
>my understanding dims and friends have been working through this as well).
>One of the places for gate testing that is still being worked on is the 
>following: https://github.com/jd/pifpaf/pull/28
>That will aid with some of the gate testing.

As Josh stated above, currently we have back ported the kafka driver to 
Stable/liberty https://github.com/tsecheran/oslo.messaging/pull/2 to get 
the notifications split work for Nova and Neutron in our cloud. It’s 
working fine and in early POC state, we need to still work on that pifpaf 
PR https://github.com/jd/pifpaf/pull/28 for the unit testing. 

- Cheran

More information about the OpenStack-dev mailing list