OpenStack Messaging (Zaqar)
Go to file
wanghao bd644fec02 Update os_client_config to openstack.config
Since now os-client-config has been superceded by openstacksdk[1].
So need to replace the os-client-config in zaqarclient to
slove the issue that 'No module named os_client_config'.

[1]:https://docs.openstack.org/os-client-config/latest/

Change-Id: Icd133a467dea36f60d00f75a1113fcdf8e7ac76b
2018-07-27 08:46:11 +08:00
api-ref/source Merge "Remove format constraint of client id" 2018-07-13 08:03:08 +00:00
devstack Remove setting of DEVSTACK_GATE_EXERCISES 2018-07-17 10:38:14 +02:00
doc Merge "Update the Bugs link for triage" 2018-06-29 10:00:11 +00:00
etc CONF file structure refactor 2018-06-04 09:11:46 +08:00
playbooks/legacy Convert zaqar-tox-integration to native Zuul v3 2017-12-21 05:14:17 +00:00
rally-jobs Port Rally Task to format v2 2017-09-27 17:28:01 -07:00
releasenotes Merge "Remove format constraint of client id" 2018-07-13 08:03:08 +00:00
samples replace windows line endings with unix format 2018-06-06 18:54:29 -04:00
tools Fix sqlalchemy migration 2017-02-02 20:20:29 +13:00
zaqar Update os_client_config to openstack.config 2018-07-27 08:46:11 +08:00
zaqar_upgradetests Support cold migration 2017-02-27 01:52:38 +00:00
.coveragerc Update .coveragerc after the removal of openstack directory 2016-10-17 17:17:34 +05:30
.gitignore Add .idea pattern to .gitignore 2017-04-10 16:01:48 +05:30
.gitreview Fix .gitreview due to the repo rename/move 2014-08-16 21:30:22 +04:00
.testr.conf Add zaqar tempest plugin 2016-02-18 20:41:07 -05:00
.zuul.yaml add lower-constraints job 2018-03-22 19:15:34 -04:00
AUTHORS.rst refactor: Rename AUTHORS so that it doesn't keep getting overwritten 2013-03-19 16:33:43 -04:00
CONTRIBUTING.rst Optimize the link address 2017-06-02 23:50:39 +07:00
HACKING.rst Update and optimize documentation links 2017-07-20 18:31:18 +08:00
LICENSE Include full license text 2014-03-21 10:16:28 +01:00
README.rst Fix format 2018-05-30 08:44:51 +08:00
babel.cfg Prepare marconi for localization 2014-06-04 22:31:55 +02:00
bench-requirements.txt Fix SSL and verbose issue of zaqar bench 2016-11-21 01:49:16 +00:00
bindep.txt Fix gate job failure 2017-12-02 23:21:27 +13:00
dox.yml Add a dox.yml config file 2014-09-08 13:55:13 +02:00
lower-constraints.txt Remove some unused lib 2018-06-29 16:51:58 +08:00
requirements.txt Update the lower-constrainsts 2018-05-09 06:30:50 +00:00
setup.cfg CONF file structure refactor 2018-06-04 09:11:46 +08:00
setup.py Updated from global requirements 2017-03-10 03:40:58 +00:00
test-requirements.txt Remove ignore D000 in validation code 2018-05-30 10:33:36 +07:00
tox.ini fix tox python3 overrides 2018-07-24 07:38:52 +00:00

README.rst

Team and repository tags

image

Zaqar

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:

https://wiki.openstack.org/wiki/Zaqar

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

https://wiki.openstack.org/wiki/Zaqar/specs/api/v2.0

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

https://docs.openstack.org/zaqar/latest

Zaqar's Release notes is available at:

https://docs.openstack.org/releasenotes/zaqar/

Contributors are encouraged to join IRC (#openstack-zaqar channel on irc.freenode.net):

https://wiki.openstack.org/wiki/IRC

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

https://docs.openstack.org/zaqar/latest/contributor/running_tests.html

Information on how to run benchmarking tool is available at:

https://docs.openstack.org/zaqar/latest/admin/running_benchmark.html

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:

https://docs.openstack.org/zaqar/latest/contributor/development.environment.html

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

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