3308af985b
Now when we update subscription and specify TTL, subscription is not renewed. It's life is not extended, and it's expiration date is still old. Because of that, it's impossible to extend life of subscription without recreating it. But during subscription recreation some messages may not be sent to subscriber, because there will be a moment when subscription does not exist, which is bad. This patch makes subscriptions renewable by PATCH method, when TTL is specified in the body. In such case PATCH method sets subscription TTL to a new value and sets expiration date to a recalculated value: current time + TTL. This patch also adds two functional tests for testing TTL-related things in subscriptions. This increases functional testing time by ~2-4 minutes. APIimpact Closes-Bug: #1552866 Co-Authored-By: wangxiyuan <wangxiyuan@huawei.com> Co-Authored-By: Eva Balycheva <ubershy@gmail.com> Change-Id: I048c37d6485ff27cf18ed27988874e470301fb57 |
||
|---|---|---|
| devstack | ||
| doc | ||
| etc | ||
| examples | ||
| rally-jobs | ||
| releasenotes | ||
| tools/doc | ||
| zaqar | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| AUTHORS.rst | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| babel.cfg | ||
| bench-requirements.txt | ||
| doc-test.conf | ||
| dox.yml | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
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 v1.1 (stable) specification and documentation are available at:
Zaqar Contributor Documentation, the source of which is in
doc/source/, 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:
http://docs.openstack.org/developer/zaqar/running_tests.html
Information on how to run benchmarking tool is available at:
http://docs.openstack.org/developer/zaqar/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:
http://docs.openstack.org/developer/zaqar/devref/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.