[openstack-dev] [devstack] [zmq] [oslo.messaging] Running devstack with zeromq
eezhova at mirantis.com
Thu Jun 19 13:56:20 UTC 2014
I have managed to make zmq work using matchmaker ring, but I haven't tried
it with more than one server.
There are proposed fixes for the bugs that Mehdi mentioned (
But in any case, if zmq really is not used by anybody, then there is no
reason to maintain it.
On Thu, Jun 19, 2014 at 5:46 PM, Sean Dague <sean at dague.net> wrote:
> On 06/19/2014 09:39 AM, Mark McLoughlin wrote:
> > 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  or  let me think that nobody can use it currently.
> >>  https://bugs.launchpad.net/oslo.messaging/+bug/1301723
> >>  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.
> +1. No one has been maintaining zmq in the community for quite some
> time, so we should mark it as such. Much better to signal to people that
> features aren't working vs. letting them discover that on their own.
> Sean Dague
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev