OpenStack Messaging (Zaqar)
Go to file
Stephen Finucane c20dd17088 devstack: Fix version check
mongosh versions 2.2.0 appears to have changed the verbosity of logging.
We are attempting to extract version information from the output, but
looking at it manually shows no such output.

  $ mongosh zaqar --eval 'db.dropDatabase();'
  { ok: 1, dropped: 'zaqar' }

Downgrading the package to the last release before 2.2.0, 2.1.5, reveals
what we had been expecting:

  $ sudo apt install mongodb-mongosh=2.1.5

  $ mongosh zaqar --eval 'db.dropDatabase();'
  Current Mongosh Log ID: 65fd88a57854a39dcce03169
  Connecting to:          mongodb://127.0.0.1:27017/zaqar?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+2.1.5
  Using MongoDB:          7.0.7
  Using Mongosh:          2.1.5

  For mongosh info see: https://docs.mongodb.com/mongodb-shell/

  To help improve our products, anonymous usage data is collected and sent to MongoDB periodically (https://www.mongodb.com/legal/privacy-policy).
  You can opt-out by running the disableTelemetry() command.

  ------
     The server generated these startup warnings when booting
     <snip>
  ------

  { ok: 1, dropped: 'zaqar' }

We *could* increase the verbosity again using the '--verbosity' flag,
but rather than relying on arbitrary logging output, we could just use
the 'db.version()' function to pull our server version. Use that
instead.

Change-Id: I1faa317ebfa9927a4d576bd4da72872fab160560
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
2024-03-22 14:40:12 +00:00
api-ref/source Fix API DOC 2022-07-06 15:59:54 +08:00
devstack devstack: Fix version check 2024-03-22 14:40:12 +00:00
doc remove unicode prefix from code 2022-08-15 10:05:54 +08:00
etc CONF file structure refactor 2018-06-04 09:11:46 +08:00
rally-jobs Port Rally Task to format v2 2017-09-27 17:28:01 -07:00
releasenotes reno: Update master for unmaintained/yoga 2024-02-05 15:53:04 +00:00
samples Replace CRLF by LF 2024-02-15 02:28:37 +00:00
tools Fix ci broken for Debian 12 2023-12-20 12:19:50 -08:00
zaqar Bump hacking 2024-02-02 12:42:02 +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 Remove integrated-gate-storage 2024-01-20 20:23:26 +09:00
AUTHORS.rst [doc]Update IRC Info 2021-06-15 09:47:40 +08:00
CONTRIBUTING.rst [community goal] Update contributor documentation 2021-06-15 16:28:28 +08: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 [doc]Update IRC Info 2021-06-15 09:47:40 +08:00
bench-requirements.txt Fix SSL and verbose issue of zaqar bench 2016-11-21 01:49:16 +00:00
bindep.txt Fix ci broken for Debian 12 2023-12-20 12:19:50 -08:00
dox.yml Add a dox.yml config file 2014-09-08 13:55:13 +02:00
requirements.txt Bump hacking 2024-02-02 12:42:02 +00:00
setup.cfg Update python classifier in setup.cfg 2024-01-05 04:40:40 +00:00
setup.py Cleanup py27 support 2022-08-15 10:07:06 +08:00
test-requirements.txt Bump hacking 2024-02-02 12:42:02 +00:00
tox.ini Switch to 2023.1 Python3 unit tests and generic template name 2023-01-21 09:29:14 +08: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 are available at:

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

Contributors are encouraged to join IRC (#openstack-zaqar channel on OFTC):

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.