6827bce759
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>
(cherry picked from commit
|
||
|---|---|---|
| api-ref/source | ||
| devstack | ||
| doc | ||
| etc | ||
| rally-jobs | ||
| releasenotes | ||
| samples | ||
| tools | ||
| zaqar | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| AUTHORS.rst | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| bench-requirements.txt | ||
| bindep.txt | ||
| dox.yml | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Team and repository tags
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:
The API v2.0 (stable) specification and documentation are available at:
Zaqar's Documentation, the source of which is in
doc/source/, is available at:
Zaqar's Release notes are available at:
Contributors are encouraged to join IRC
(#openstack-zaqar channel on OFTC):
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:
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.