Skip to content
OpenStack Messaging (Zaqar)
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
api-ref/source Miss name filter in querying queues Dec 17, 2018
devstack Remove the pool group totally Jan 10, 2019
doc Unblock gate failures May 29, 2019
etc CONF file structure refactor Jun 4, 2018
playbooks/legacy OpenDev Migration Patch Apr 19, 2019
rally-jobs Port Rally Task to format v2 Sep 28, 2017
releasenotes Merge "Imported Translations from Zanata" Jun 5, 2019
samples Update the client version in samples Sep 17, 2018
tools Fix sqlalchemy migration Feb 2, 2017
zaqar_upgradetests Support cold migration Feb 27, 2017
.coveragerc Update .coveragerc after the removal of openstack directory Oct 17, 2016
.gitignore Unblock gate failures May 29, 2019
.gitreview OpenDev Migration Patch Apr 19, 2019
.stestr.conf Add .stestr.conf configuration Dec 20, 2018
.zuul.yaml Dropping the py35 testing Apr 25, 2019
AUTHORS.rst refactor: Rename AUTHORS so that it doesn't keep getting overwritten Mar 19, 2013
CONTRIBUTING.rst Optimize the link address Jun 2, 2017
HACKING.rst Update and optimize documentation links Jul 20, 2017
LICENSE Include full license text Mar 21, 2014
README.rst Fix format May 30, 2018
babel.cfg Prepare marconi for localization Jun 4, 2014
bench-requirements.txt Fix SSL and verbose issue of zaqar bench Nov 21, 2016
dox.yml Add a dox.yml config file Sep 8, 2014
lower-constraints.txt Unblock gate failures May 29, 2019
requirements.txt Unblock gate failures May 29, 2019
setup.cfg Dropping the py35 testing Apr 25, 2019 Updated from global requirements Mar 10, 2017
test-requirements.txt Fix redis CI job Dec 11, 2018
tox.ini Merge "Dropping the py35 testing" Jun 5, 2019


Team and repository tags


Zaqar is a multi-tenant cloud messaging and notification service for web and mobile developers. It combines the ideas pioneered by Amazon's SQS product with additional semantics to support event broadcasting.

The service features a fully RESTful API, which developers can use to send messages between various components of their SaaS and mobile applications, by using a variety of communication patterns. Underlying this API is an efficient messaging engine designed with scalability and security in mind.

Other OpenStack components can integrate with Zaqar to surface events to end users and to communicate with guest agents that run in the "over-cloud" layer. Cloud operators can leverage Zaqar to provide equivalents of SQS and SNS to their customers.

General information is available in wiki:

The API v2.0 (stable) specification and documentation are available at:

Zaqar's Documentation, the source of which is in doc/source/, is available at:

Zaqar's Release notes is available at:

Contributors are encouraged to join IRC (#openstack-zaqar channel on

Information on how to run unit and functional tests is available at:

Information on how to run benchmarking tool is available at:

Using Zaqar

If you are new to Zaqar and just want to try it, you can set up Zaqar in the development environment.

Using Zaqar in production environment:

Coming soon!

Using Zaqar in development environment:

The instruction is available at:

This will allow you to run local Zaqar server with MongoDB as database.

This way is the easiest, quickest and most suitable for beginners.

You can’t perform that action at this time.