e135e43935
There were a lot of instances of exceptions being raised or logged incorrectly. When reraising an exception, "raise" should be called, not "raise ex". The second form will cause the original traceback to be modified to the new location. LOG.exception is the same as LOG.error with the additional behavior of logging any exception that is in the current scope. Therefore, doing something like "LOG.exception(ex)" is redundant and causes the exception message to be logged twice. Logging should be done with some sort of textual message without the exception object. Change-Id: I149c8fe7ef4b6628f910943587ab4302cc371441 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com> |
||
|---|---|---|
| api-ref/source | ||
| devstack | ||
| doc | ||
| etc | ||
| playbooks/legacy | ||
| rally-jobs | ||
| releasenotes | ||
| samples | ||
| tools | ||
| zaqar | ||
| zaqar_upgradetests | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| AUTHORS.rst | ||
| babel.cfg | ||
| bench-requirements.txt | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| dox.yml | ||
| HACKING.rst | ||
| LICENSE | ||
| lower-constraints.txt | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
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 is available at:
Contributors are encouraged to join IRC
(#openstack-zaqar channel on
irc.freenode.net):
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.