[openstack-dev] [devstack] [zmq] [oslo.messaging] Running devstack with zeromq

Mark McLoughlin markmc at redhat.com
Thu Jun 19 13:39:06 UTC 2014

On Thu, 2014-06-19 at 14:29 +0200, Mehdi Abaakouk wrote:
> Hi,
> Le 2014-06-19 00:30, Ben Nemec a écrit :
> > On 06/18/2014 05:45 AM, Elena Ezhova wrote:
> > 
> >> So I wonder whether it is something the community is interested in 
> >> and, if
> >> yes, are there any recommendations concerning possible implementation?
> > 
> > I can't speak to the specific implementation, but if we're going to 
> > keep
> > the zmq driver in oslo.messaging then IMHO it should be usable with
> > devstack, so +1 to making that work.
> Currently the zmq driver have a really bad test coverage, the driver is 
> 'I think' broken since a while.
> Bugs like [1] or [2] let me think that nobody can use it currently.
> [1] https://bugs.launchpad.net/oslo.messaging/+bug/1301723
> [2] https://bugs.launchpad.net/oslo.messaging/+bug/1330460
> Also, an oslo.messaging rule is "a driver must not force to use a 
> eventloop library",
> but this one heavily use eventlet. So only the eventlet executor can 
> works with it, not the
> blocking one or any future executor.
> I guess if someone is interested in, the first step is to fix the zmq 
> driver, remove eventlet stuffs and write unit tests for it,
> before trying integration, and raise bugs that should be catch by 
> unit/functionnal testing.
> If nobody is interested in zmq, perhaps we should just 
> drop/deprecated/mark_as_broken it.

Yes, I agree with all of that. Unless the situation improves rapidly, I
think we should mark it as deprecated in Juno and plan to remove it in
K. That might seem like an overly rapid deprecation cycle, but it is
currently broken and unusable in Icehouse ... so no-one can be using it
in Icehouse.


More information about the OpenStack-dev mailing list