Specs repos now build with tox -e docs and this fails since warnings are
treated as errors. Fix issues, see below for details.
tox -e docs fails with:
1)
queens/remove-pool-group-from-zaqar.rst:402: WARNING: Inline emphasis start-string without end-string.
Fix RST syntax.
2) queens/support-md5-of-body.rst:: WARNING: document isn't included in any toctree
Include document in toctree.
3) rocky/queue-filter-support.rst:38: WARNING: Literal block expected; none found.
Fixed RST.
4) rocky/remove-format-constraint-of-client-id.rst:13: WARNING: Title overline too short.
Fixed RST.
5) rocky/remove-format-constraint-of-client-id.rst:37: ERROR: Unexpected indentation.
Fixed RST.
6) rocky/subscription-filtering-tags.rst:82: WARNING: Bullet list ends without a blank line; unexpected unindent.
Fixed RST.
Change-Id: Ide32b348d68e35f8f531c30ddae680d085553b68
This work is aimed to enable Zaqar to send email subscription
without the third part tools.
Change-Id: Id775c3dae4ee92198cf1bb9e20f5f83e3ad27e44
implements: blueprint zaqar-email-delivery
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I47130ea63d4427074bf51957032c89c55f7a8dcf
Describe Zaqar how to remove the format constraint of
client id.
Change-Id: Ibb551d33cb4148c5ff3344a23467e4055fe6ba89
Implements: blueprint remove-format-constraint-of-client-id
By default, a subscriber of zaqar topic receives every message published
to the topic. To receive only a subset of the messages, a subscriber
assigns a filter policy to the topic subscription. So in this case,
zaqar need to support message filtering
Change-Id: I55e39c1eb403fc4d6287c3a54de3a46fd96fa7e1
blueprint: subscription-filtering-tags
We want to introduce a new resource called Topic into Zaqar.
Topic is a concept from AWS SNS, it will has
relevance with subscriptions.
User can send message to a topic, and then the subscribers
will get the message according to different protocols,
like http, email, sms, etc.
Change-Id: Iea78a20a2dde677620908f8d20a36b18d93d7664
Implements: bp introduce-topic-resource-for-notification
Currently pool group is used in pool and flavor resource,
but the pool group only supports a 1:1 mapping with flavor.
So it's not necessary to keep it since we can map
1 flavor : N pool directly.
For making a clarification to end user,
this bp proposes to remove useless pool group from Zaqar,
just keeps the pool resource.
Change-Id: I5927aea4e1ffa632bb78e3fa9d340c3d812bad2a
Implements: blueprint remove-pool-group-from-zaqar
Now, Zaqar will add a non-URL-encoded message body MD5 validation function.
This is essential for the security of the message body, it can prevent the
message from being tampered.
Change-Id: Ic01e37be1ab59a42d10c53ffadfb6569ffccce2b
blueprint: support-md5-of-body
Now there is two same template.rst under root folder
and specs folder. Just remove the one from root folder
to keep consistent with other projects.
Change-Id: I849ded5791bf9bd9ab5b1d3cb686fc02872b0815
Now one of the big function gaps of Zaqar is the delayed queue.
Currently, all the message posted to the queue will be visible
immediately. That's enough for most of the user cases. However,
for some user case, user want the message to be unavailable to
end users for a specific period of time.
Change-Id: I2610a8f89568f8af1cb292f0c8dea8f7deb4e4a3
blueprint: delayed-queues
Update doc links according to OpenStack document migration.
Use https instead of http for docs links.
Closes-Bug:#1717171
Change-Id: I97ea62e22d8ae0913562fdd51226e1464416a66d
1) Update doc links according to OpenStack document migration
2) Use https instead of http for docs links
Change-Id: I9f6943d01b4e408d8873d1dfb0afd2a3032f7fc7
Now we have decided to update the default value
of maximum_delay from 60 to 30 seconds in
notification retry policy.
That could reduce the unnecessary workload in Zaqar.
Change-Id: I21a2bc9415eb3956c09dfc9d61eadaca8e187d97
Closes-Bug: #1709231
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
