1af2c91e41
There are a few issues causing all gate runs to fail that are addressed in this patch. Update constraints to match global requirements: There are a few local requirements that conflict with what is now in upstream global-requirements. This updates sphinx to match the constrained versions due to incompatibility with py2 and uncaps jsonschema. Update handling for falcon 2.0.0 behavior changes: The 2.0.0 release of falcon changed the default values for two request query parsing options that would cause failures due to unexpected results. This sets those options to their previous defaults to maintain compatibility across 2.0.0 and pre-2.0.0 versions of the package. Lower constraint version raised to 1.1.0 where the options were introduced. There are additional integration test failures with Falcon 2.0.0 that were due to changes in the subscription URL path. Closes-bug: #1830903 Requirements and upper constraints not enforced in some tox targets: The docs and api-ref tox targets were not setting the right dependencies or the upper constraints to use for pip installs. Also updates the constraints to the newer preferred static redirect URL maintained by the release team. Co-authored-by: wanghao <sxmatch1986@gmail.com> Change-Id: I19c5363878c629a04e1be902c865ee7cea92dcd9 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.