Open Stack

Hi all,

I'd like to propose a simple but straightforward method to improve the
stability of the current implementation.

Here's the current implementation:

receiver(PULL(tcp)) <-- service(PUSH(tcp))
receiver(PUB(ipc)) --> service(SUB(ipc))
receiver(PUSH(ipc)) --> service(PULL(ipc))

Actually, as far as I know, the local IPC method is much more stable
than network. I'd like to switch PULL/PUSH to REP/REQ for TCP
communication.

The change is very simple but effective for stable network
communication. I cannot apply the patch for our production systems. I
tried it in my lab, and it works well.

I know there's another blueprint for REP/REQ pattern [1], but it's not
the same, I think.

I'd like to discuss it about how to take advantage of REP/REQ of zeromq.

[1] https://review.openstack.org/#/c/154094/2/specs/kilo/zmq-req-rep-call.rst

Best regards,
-- 
Li Ma (Nick)
Email: skywalker.nick at gmail.com