openstack/zaqar
Code Issues Proposed changes
OpenStack Messaging (Zaqar)
2,393 Commits 10 Branches 44 Tags 46 MiB
Python 96.4%
PHP 1.4%
Shell 1.2%
HTML 0.8%
Lua 0.2%
8d54d2c2b6
Go to file
liuyamin 8d54d2c2b6 Use rest_status_code for api-ref response codes 
Rather than our freeform way of listing response codes in our
api-ref, we should be using the os-api-ref extension option to
get nicely formatted response code listings.

https://docs.openstack.org/os-api-ref/latest/usage.html#rest-status-code

Change-Id: I70b5f0c20089d0eaa201ab9d9bbf9ec1464ec636
2018-03-23 17:50:24 +08:00
api-ref/source Use rest_status_code for api-ref response codes 2018-03-23 17:50:24 +08:00
devstack Remove use of unsupported TEMPEST_SERVICES variable 2018-01-23 16:26:29 +03:00
doc Nit update in jenkins.rst document 2018-02-13 10:44:29 +07:00
etc Policy in code: Update the related doc 2017-11-16 09:30:55 +00: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 Add reserved metadatas for dead letter queue 2018-03-15 16:56:24 +08:00
samples Replace uuid.uuid4().hex with uuidutils.generate_uuid() 2017-07-24 05:30:23 +00:00
tools Fix sqlalchemy migration 2017-02-02 20:20:29 +13:00
zaqar Add reserved metadatas for dead letter queue 2018-03-15 16:56:24 +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 heat job to zaqar check pipeline 2018-02-06 07:23:49 +00:00
AUTHORS.rst refactor: Rename AUTHORS so that it doesn't keep getting overwritten 2013-03-19 16:33:43 -04: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
CONTRIBUTING.rst Optimize the link address 2017-06-02 23:50:39 +07:00
dox.yml Add a dox.yml config file 2014-09-08 13:55:13 +02: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 Update and optimize documentation links 2017-07-20 18:31:18 +08:00
requirements.txt Updated from global requirements 2018-03-14 06:14:17 +00:00
setup.cfg Remove bundled intree tempest plugin from Zaqar 2017-10-26 13:03:23 +05:30
setup.py Updated from global requirements 2017-03-10 03:40:58 +00:00
test-requirements.txt Updated from global requirements 2018-03-15 09:40:49 +00:00
tox.ini Redis connection support password configure in zaqar 2018-01-03 00:55:34 +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

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.