[openstack-dev] [oslo][monasca] Can we uncap python-kafka ?
tony at bakeyournoodle.com
Fri Dec 2 04:19:26 UTC 2016
On Thu, Dec 01, 2016 at 07:57:37AM +0100, Mehdi Abaakouk wrote:
> I'm aware of all of that, oslo.messaging patch for the new version is
> ready since 8 months now. And we are still blocked... capping libraries,
> whatever the reason, is very annoying and just freezes people work.
And I agree with that statement. Capping isn't the right solution. By the
same token uncapping isn't eaither as we know we'll cause breakage.
> From the API pov python-kafka haven't break anything, the API is still
> here and documented (and deprecated). What monasca raises is performance
> issue due to how their uses the library, and on absumption on how it works
> internally. Blocking all projects for that looks not fair to me.
I understand that your blocked, but blocking the other team isn't the solution
> As nadya said, now, we have users that that prefers using an unmerged
> patch and the new lib instead of using upstream supported
> version with the old lib. This is not an acceptable situation to me but
> that's just my thought.
> Where is the solution to allow oslo.messaging works blocked since 8
> month to continue ?
> So, I'm waiting for monasca team input now and hope we can move forward.
I think the solution is pretty simple. Just Fix it. I'm not saying it's easy
but it is *simple*. We're a group of skilled individuals We have several ways
forward which just haven't been done in the last 8 months. Waiting doesn't seem
to be a viable course anymore.
From my POV this really feels more like a social problem then a technical one.
I'd like to remind everyone with a technical stake in this that it's OpenStack
First, Project Team Second. The thing that's best for OpenStack is for the
oslo.mesaging and monasca teams to come together and find a path forward. It's
really great that this thread has started that process!
Other people are much better placed to define the way forward, clearly fixing
python-kafka is the best option which almost certainly means joining that
Worst case if we really can't find a way forward, monasca can just vendor/fork
python-kafka 0.X and we'll all admit defeat.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 473 bytes
Desc: not available
More information about the OpenStack-dev