Open Stack

Good day, Stackers.


During Paris Design summit oslo.messaging session was raised good question
about maintaining ZeroMQ driver in upstream (see section “dropping ZeroMQ
support in oslo.messaging” at [1]) . As we all know, good thoughts are
comming always after. I’d like to propose several improvements in process
of maintaining and developing of ZeroMQ driver in upstream.


Contribution focus. As we all see, that there are enough patches that are
trying to address certain problems related to ZeroMQ driver.

Few of them trying to add functional tests, which is definitely good, but …
there’s always ‘but’, they are not “gate”-able.

My proposal for this topic is to change contribution focus from
oslo.messaging by itself to OpenStack/Infra project and DevStack
(subsequently to devstack-gate too).

I guess there would be questions “why?”.  I think the answer is pretty
obvious: we have driver that is not being tested at all within DevStack and
project integration.

Also i’d say that such focus re-orientation would be very useful as source
of use cases and bugs eventually. Here’s a list of what we, as team, should
do first:

   1.

      Ensure that DevStack can successfully:
      1.

         Install ZeroMQ.
         2.

         Configure  each project to work with zmq driver from
         oslo.messaging.
         2.

      Ensure that we can run successfully simple test plan for each project
      (like boot VM, fill object store container, spin up volume, etc.).


ZeroMQ driver maintainers community organization. During design session was
raised question about who uses zmq driver in production.

I’ve seen folks from Canonical and few other companies. So, here’s my
proposals around improving process of maintaining of given driver:

   1.

      With respect to best practices of driver maintaining procedure, we
      might need to set up community sub-group. What would it give to us and to
      the project subsequently? It’s not pretty obvious, at least for now, but
      i’d try to light out couple moments:
      1.

         continuous driver stability
         2.

         continuous community support (across all OpenStack Project that
         are using same model: driver should have maintaining team,
would it be a
         company or community sub-group)
         2.

      As sub-group we would need to have our own weekly meeting. Separate
      meeting would keep us, as sub-group, pretty focused on zmq
driver only (but
      it doesn’t mean that we should not participate in regular meetings). Same
      question. What it would give us and to the project? I’d say that the only
      one valid answer is: we’d not disturb other folk that are not actually
      interested in given topic and in zqm drive too.


    So, in the end, taking into account words above i’d like to get
feedback from all folks. I’m pretty open for discussion, and if needed i
can commit myself for driving such activities in oslo.messaging.


[1] https://etherpad.openstack.org/p/kilo-oslo-oslo.messaging


Kind regards,

Denis M.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141117/ed37a518/attachment.html>