[openstack-dev] [oslo][messaging] Summary for drivers discussion
ozamiatin at mirantis.com
Mon Nov 9 10:31:50 UTC 2015
Just wanted to sum up a little bit from the discussions at Mitaka summit
(etherpad available ).
General for oslo.messaging:
- Implement single-machine failover test suite using multiprocessing +
iptables for network failures emulation.
Needed for emulating different situations critical for messaging
(like connectivity lost or server restart or server hangs) to see how
oslo messaging (or a specific driver) deals with that.
- Write detailed specification of messaging patterns (API) to form
expectations of their behavior, reliability etc.
From session etherpad: "Define more *explicitly* semantics of cast,
call, and what is expected"
- Divide RPC and Notifications drivers so we can use different backends
for each pattern.
For ZeroMQ (slides )
Make driver production-ready in Mitaka cycle.
- Make use of tooz library with different driver backends instead of
- Implement more matchmaker backends in addition to redis (more
- Provide more configuration options for zmq driver (like port-binding
ranges, memory limitations etc.)
- Provide versioning of critical places like request serialization,
publisher/consumer compatibility etc.
For Pika (slides )
There were proposed to use pika driver as the default rabbitmq driver in
future releases without any backwards
compatibility with the old driver. Leave kombu driver for previous versions.
Spec is accepted and available at 
The driver is not intended for RPC but may be used as an alternative for
If I missed something please correct me.
Was very pleased to meet all of you at the summit!
 - https://etherpad.openstack.org/p/mitaka-oslo-messaging-zmq-pika-kafka
 - http://www.slideshare.net/AlexeyZamiatin/zmq-driver-mitaka-summit
 - http://www.slideshare.net/AlexeyZamiatin/pika-driver
 - https://review.openstack.org/#/c/189003/
More information about the OpenStack-dev