Currently, Zaqar has tree versions of APIs,
V1, V1_1 and V2. The V1 is the oldest apis that
there is no need for them right now. All new features
are implemented under V2 APIs. So it’s time to remove
V1 APIs and optimize the Zaqar's codes.
Change-Id: Ib227ffd428935cd1849c5bf84a22bfa4f542bc8e
Implements: blueprint remove-v1-api-code
This requirement came from a true scenario when
people use the subscription function of Zaqar,
for example, text messages, they need to return
some extra information like message authentication
code in confirming process.
Change-Id: Ia2a665207d4b267798d9d998d0284c2e68b247a4
Implements: blueprint support-extra-specs-to-subscription-confirming
a few cleanups:
- Remove obsolete sections from setup.cfg
- Switch to using sphinx-build
- Remove install_command from tox.ini, the default is fine
- Update pbr requirement
- Fix build problems
- Switch to py38 for testing following Victoria testing platforms
Change-Id: I1ff3853020d69aeceb8b81c21ce608b269015ece
This spec will support to encrypt messages before storing them
into backends. This will enhance the security of messaging service.
Implements: blueprint encrypted-messages-in-queue
Signed-off-by: wanghao <sxmatch1986@gmail.com>
Change-Id: I2fce18ef574acdee52446ce241083d0cdb1e0cd9
Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I9d8b24733842e364fc6ef05b9e9adebae2a66ee5
Zaqar will support query queues with 'with_count' to
return the amount of the queues. This will help users to
quickly get the exact total number of queues which they own.
Change-Id: Ic1ff218e4e975b4f6e16ebe4192f406efaeb94fe
Implements: blueprint query-queues-with-count
Signed-off-by: wanghao <sxmatch1986@gmail.com>
This commit does multiple fix
1. Doc building still use deprcated oslosphinx and incompatible
version of yasfb which lead to error-
sphinx.errors.ExtensionError: Could not import extension yasfb (exception: cannot import name 'logging')
Replace oslosphinx with openstackdocstheme to fix the error.
2. Switch py27 job with py37
3. fix the pep8 error
Change-Id: I33ad4d0a2924082b7c56ac7c7973ad02ac6e9df5
There are many references to review.openstack.org, and while the
redirect should work, we can also go ahead and fix them.
Change-Id: I397b58c562079444553d393387d7c6323b06fba4
In Queens, we support the old way to use pool_group and the
new way without it in Flavor both. In Stein, we will remove
the pool_group totally and only keep the new way in Flavor
and Pool.
Change-Id: Ie0bf6e4b5e6ca7b97037b2ea493465803f4eb898
Implements: bp remove-pool-group-totally
Quotes around {posargs} cause the entire string to be combined into one
arg that gets passed to stestr. This prevents passing multiple args
(e.g. '--concurrency=16 some-regex')
Change-Id: Ie3379b54b354984348a10ec32bf6d245d1c04847
Closes-Bug: #1801816
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: Ife18281cb3f1a28d1ccc52196ca708e7ace14395
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Delete Message with claim id means that when a user deletes a message, the
message must be claimed. If you want to delete a message, you will have to use
both message id and claim id. This can improve the security of the message.
Change-Id: I81f505e6ac3ee8f8ab42ce0c1b80ecc878f67b78
blueprint: delete-message-with-claim-id
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
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I756e2fde7a70682f079c477e9a9c426e3605f5f2
Story: #2002586
Task: #24346
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
wanghao