OpenStack Messaging (Zaqar)
Go to file
melissaml e195c8112b Switch to newer openstackdocstheme and reno versions
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems

Update Sphinx version as well.

Set openstackdocs_auto_name to use 'project' as name.

Change pygments_style to 'native' since old theme version always
used 'native' and the theme now respects the setting and using 'sphinx'
can lead to some strange rendering.

Remove docs requirements from lower-constraints, they are not
needed during install or test but only for docs building.

openstackdocstheme renames some variables, so follow the
renames before the next release removes them. A couple of variables
are also not needed anymore, remove them.

See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html

Change-Id: Ie623e7a2389c292ffc71a285f0fc2d4bb9820c3f
2020-05-26 14:03:34 +08:00
api-ref/source Switch to newer openstackdocstheme and reno versions 2020-05-26 14:03:34 +08:00
devstack Doc cleanups 2020-05-13 17:49:28 +08:00
doc Switch to newer openstackdocstheme and reno versions 2020-05-26 14:03:34 +08:00
etc CONF file structure refactor 2018-06-04 09:11:46 +08:00
playbooks/legacy Merge "[train][goal] Define new 'zaqar-tempest-swift-ipv6' job" 2020-01-09 03:49:19 +00:00
rally-jobs Port Rally Task to format v2 2017-09-27 17:28:01 -07:00
releasenotes Switch to newer openstackdocstheme and reno versions 2020-05-26 14:03:34 +08:00
samples Update the client version in samples 2018-09-17 10:50:25 +08:00
tools Fix sqlalchemy migration 2017-02-02 20:20:29 +13:00
zaqar Merge "Fix exception mishandling" 2020-01-31 05:28:22 +00: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 Unblock gate failures 2019-05-29 09:31:18 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:45:44 +00:00
.stestr.conf Add .stestr.conf configuration 2018-12-20 11:03:54 +08:00
.zuul.yaml Merge "[train][goal] Define new 'zaqar-tempest-swift-ipv6' job" 2020-01-09 03:49:19 +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
lower-constraints.txt Switch to newer openstackdocstheme and reno versions 2020-05-26 14:03:34 +08:00
README.rst Add zaqar-specs link to readme.rst 2019-08-30 07:57:30 +00:00
requirements.txt Doc cleanups 2020-05-13 17:49:28 +08:00
setup.cfg [ussuri][goal] Drop python 2.7 support and testing 2019-12-13 00:22:57 +00:00
setup.py Updated from global requirements 2017-03-10 03:40:58 +00:00
test-requirements.txt Switch to using stestr directly 2019-05-29 10:48:28 -05:00
tox.ini [ussuri][goal] Drop python 2.7 support and testing 2019-12-13 00:22:57 +00:00

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 are 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

Zaqar's design specifications is tracked at:

https://specs.openstack.org/openstack/zaqar-specs/

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.