the py27 CI failed due to tox 2.5.0 release. The command
in tox.ini is required now[1].
This patch refactored the code tree to make CI work.
[1]:
1e888ce9b8/CHANGELOG (L40)
Change-Id: Icd90598367e3b529e64d184e78b144e4d075b9a3
We'd like to introduce the osprofiler lib to zaqar in Ocata. It's
useful for performance analysis.
Implements: blueprint osprofiler
Change-Id: Ic7ddafc8d375e9f5c6f70aa0e4de9164ab0b0dc7
Currently Zaqar can post notifications to the subscriber
once the subscription is created.
It doesn't need the subscriber to confirm the subscription.
This will lead a problem that users could send junk
information that whether subscriber want or not.
So we should support to confirm subscription by using
HTTP request like what Amazon SNS is doing.
Change-Id: I43c202e86a7a6a9605747096f707104d2d699010
Implements: blueprint subscription-confirmation-support
Allow a message to a Zaqar queue to trigger a Mistral workflow via the Zaqar
notification mechanism.
blueprint mistral-notifications
APIImpact
Change-Id: Id0639aff09a846c81bcb1e9949e5cf342cf5dfe6
Make queues lazy on operations with subscriptions, so the user will be
able to subscribe to yet unexisting queue.
blueprint lazy-queues-in-subscriptions
Change-Id: Ib5c25f160aa91525e18e9bbd06b6a48931ddec49
Add spec for support for binary communications over websocket transport
which will allow to reduce network traffic between Zaqar and it's
clients and also to increase performance.
Change-Id: I35b0912e2c5c0e31bca22706209ddee0cba50a1f
Zaqar needs to support policy. This proposal is for adding
policy.json and leveraging olso.policy to implement fine-grained
permissions for Zaqar's Rest API endpoints.
blueprint: fine-grained-permissions
Co-Authored-By: Louis Taylor <louis@kragniz.eu>
Change-Id: I61ff36b12d7128aae88a8b4da19be90c9faa0a02
This spec depicts the missing features that are going to be added
to the websocket driver in the Liberty release.
Change-Id: Ib7227cd4a2e4ff1d20c0b291b21fa8af6b356439
We've agreed on keeping all specs under backlog until they are
implemented. This way we'll be able to focus more on the design rather
than worrying about the scheudle. Whenever the implementation is ready,
we'll move the spec under the release directory.
Change-Id: Iec189edd9a022ff99c0a8908f2bf3fdd86c18098
In the original spec we noticed that capabilities were already implemented and
that the feature that needed to be added was 'notifications', that is why I
replaced the original 'capabilities' with 'notifications'.
Change-Id: I414d21e432490fbfb0096464ead5ddfb2b45fdd8
Python-zaqarclient currently has some missing features that
need to be added. This spec describes which endpoints are missing and
how those are going to be added to the client side.
Change-Id: Ic58ab9bd9c2f167e9f60e489a05744dbf87741a8
The backlog dir is meant to be used for incomplete ideas that it'd be
worth looking at in the future. Either these ideas are brought from
folks from the community or Zaqar's team itself.
Change-Id: I144e77ec201849d62bbe0dbbea273736c4d589d6
OpenStack has dropped the incubation notion, so labeling this as an
incubated project in the docs is confusing.
Change-Id: Ib28ab536f88c63019ab435697382533d584acb84
There are some changes for the design of notification API:
1. Update the REST API of subscriptions
2. Changed 'publisher' to 'subscriber'
Change-Id: Iea356e77c9b52d399a116e92a098ddb018b21188
Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.
Change-Id: I19aea934526bd6210fdd984f03e43fb484e65741
gecong1973