OpenStack Messaging (Zaqar)
Go to file
Damien Ciabrini ff19fdeb54 Python 3: Fix parsing of received notification
The parsing of incoming notifications is performed with a helper
which normally resolves to a mimetools class.

For Python3, package mimetools doesn't exist anymore, and the helper
resolves to a class with incompatible signature.

In order to mimick the original helper behaviour and return a message
object as expected, use a different facility from package email.

Change-Id: I92f10755f1a98239df3b3a1494207299a3681a84
Closes-Bug: #1818046
Co-Authored-By: Michele Baldessari <michele@acksyn.org>
Co-Authored-By: Alex Schultz <aschultz@redhat.com>
2019-03-04 14:50:26 -07:00
api-ref/source Miss name filter in querying queues 2018-12-17 16:27:10 +08:00
devstack Remove setting of DEVSTACK_GATE_EXERCISES 2018-07-17 10:38:14 +02:00
doc The instructions on README.rst to create a sample queue was outdated. 2019-02-11 08:08:12 +05:30
etc CONF file structure refactor 2018-06-04 09:11:46 +08:00
playbooks/legacy Cleanup .zuul.yaml 2018-09-30 12:25:45 +02:00
rally-jobs Port Rally Task to format v2 2017-09-27 17:28:01 -07:00
releasenotes Imported Translations from Zanata 2019-02-01 08:08:28 +00: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 Python 3: Fix parsing of received notification 2019-03-04 14:50:26 -07: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 .stestr.conf configuration 2018-12-20 11:03:54 +08:00
.gitreview Fix .gitreview due to the repo rename/move 2014-08-16 21:30:22 +04:00
.stestr.conf Add .stestr.conf configuration 2018-12-20 11:03:54 +08:00
.zuul.yaml Replace tripleo-scenario002-multinode with scenario002-standalone 2019-01-03 17:07:56 -02: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 Add zaqar-status upgrade check command framework 2018-12-12 06:08:06 +00:00
README.rst Fix format 2018-05-30 08:44:51 +08:00
requirements.txt Add zaqar-status upgrade check command framework 2018-12-12 06:08:06 +00:00
setup.cfg Merge "Update mailinglist from dev to discuss" 2018-12-24 11:32:27 +00:00
setup.py Updated from global requirements 2017-03-10 03:40:58 +00:00
test-requirements.txt Fix redis CI job 2018-12-11 15:50:38 +08:00
tox.ini Add .stestr.conf configuration 2018-12-20 11:03:54 +08: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 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.