Hervé Beraud dfc684a24c Stop to use the __future__ module.
The __future__ module [1] was used in this context to ensure compatibility
between python 2 and python 3.

We previously dropped the support of python 2.7 [2] and now we only support
python 3 so we don't need to continue to use this module and the imports
listed below.

Imports commonly used and their related PEPs:
- `division` is related to PEP 238 [3]
- `print_function` is related to PEP 3105 [4]
- `unicode_literals` is related to PEP 3112 [5]
- `with_statement` is related to PEP 343 [6]
- `absolute_import` is related to PEP 328 [7]

[1] https://docs.python.org/3/library/__future__.html
[2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
[3] https://www.python.org/dev/peps/pep-0238
[4] https://www.python.org/dev/peps/pep-3105
[5] https://www.python.org/dev/peps/pep-3112
[6] https://www.python.org/dev/peps/pep-0343
[7] https://www.python.org/dev/peps/pep-0328

Change-Id: I88a05dfd99fbca043f25b5ddce7663467699e69b
2020-06-02 21:08:18 +02:00
2020-05-13 17:49:28 +08:00
2020-05-13 17:49:28 +08:00
2020-05-13 17:49:28 +08:00
2018-06-04 09:11:46 +08:00
2017-09-27 17:28:01 -07:00
2017-02-02 20:20:29 +13:00
2020-06-02 21:08:18 +02:00
2017-02-27 01:52:38 +00:00
2019-05-29 09:31:18 -05:00
2019-04-19 19:45:44 +00:00
2018-12-20 11:03:54 +08:00
2014-06-04 22:31:55 +02:00
2017-12-02 23:21:27 +13:00
2017-06-02 23:50:39 +07:00
2014-09-08 13:55:13 +02:00
2014-03-21 10:16:28 +01:00
2020-05-13 17:49:28 +08:00
2019-08-30 07:57:30 +00:00
2020-05-13 17:49:28 +08:00
2017-03-10 03:40:58 +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.

Description
OpenStack Messaging (Zaqar)
Readme 46 MiB
Languages
Python 96.1%
PHP 1.5%
Shell 1.2%
HTML 0.8%
Lua 0.3%