OpenStack library for messaging
8424dbc7cb
ZeroMQ manages failover automatically when socket is being connected to multiple hosts. Dynamic connections mode assumes to connect once per message so we connect only to a single host. However we cannot say for sure if this host is still alive. For failover reasons we can connect to a primary host and then add some more hosts as failover and let ZeroMQ to decide where it finally sends the message. Change-Id: I19cbb75aaea8a0b725dd6a8ff665392738e164a1 |
||
---|---|---|
doc/source | ||
etc | ||
oslo_messaging | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
babel.cfg | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
setup-test-env-amqp1.sh | ||
setup-test-env-kafka.sh | ||
setup-test-env-zmq-direct-dynamic.sh | ||
setup-test-env-zmq-proxy.sh | ||
setup-test-env-zmq-pub-sub.sh | ||
setup-test-env-zmq.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Team and repository tags
Oslo Messaging Library
The Oslo messaging API supports RPC and notifications over a number of different messaging transports.
- License: Apache License, Version 2.0
- Documentation: http://docs.openstack.org/developer/oslo.messaging
- Source: http://git.openstack.org/cgit/openstack/oslo.messaging
- Bugs: http://bugs.launchpad.net/oslo.messaging