Updated openstack/openstack

Project: openstack/oslo-specs  b7f3eab45953b25a95b359ac61011671a2c841eb

New ZeroMQ driver implementation details

Blueprint: https://blueprints.launchpad.net/oslo.messaging/+spec/zmq-patterns-usage

This spec proposes a new zmq driver which should develop in parallel
to the existing one and should substitute the existing driver after
some stabilization period. This spec is extension of [1]
where was original proposal to implement a new zmq driver.

Existing driver implementation sticks to a universal socket pipeline approach.
This means that all messaging patterns are implemented over a single socket
pipeline.

In [1] there were proposed to develop new zmq driver and to switch from a splitted
universal forward(PUSH/PULL)+backward(PUB/SUB) pipeline to a unified REQ/REP
bidirectional pipeline. The change simplifies the driver implementation and
makes it more reliable but the pipeline still remains universal.

The main drawback of the universal pipeline is that it can not be optimized
for some specific messaging pattern. For example, if we would like to
make a FANOUT cast over a universal pipeline (PUSH/PULL or REQ/REP does not matter)
we have to emulate it over a number of direct casts while it could be
done over PUB/SUB zeromq pattern using a single api call.

This specification proposes to extend new zmq driver implementation
with several specific socket pipelines according to each messaging pattern.

1. https://review.openstack.org/#/c/171131/

Change-Id: Ibb7d403f3b7fe5639345bf1540429e2b8506655a
This commit is contained in:
Jenkins 2015-07-03 10:51:40 +00:00 committed by Gerrit Code Review
parent 6ee5473cc7
commit 26710d3b9d
1 changed files with 1 additions and 1 deletions

@ -1 +1 @@
Subproject commit f09e4f9b0b510f4ba0808ed812718ccd1b8ef737
Subproject commit b7f3eab45953b25a95b359ac61011671a2c841eb