devstack is now replacing usage of wsgi script by wsgi module. This
replaces the way to load the api wsgi app following that transition.
Change-Id: Id799bacb71483d2e337c049e1db7f85735eb5a1e
... to reduce own logic in our devstack plugin. Note that this adds
apache web server in front of zaqar-api run by uwsgi, following
the standard architecture in devstack.
Change-Id: I0e7f48c8568fe461304e6e39d9f61c4268154a6f
This reverts commit 5a7636786ec4cc8bdf490c11b94b52f377edebb3.
Reason for revert: We do not handle href links properly and this breaks other services depending on Zaqar.
Change-Id: I5fb0f2f25c280dd69cfb99d9f9b320df552462dc
After this change, Zaqar-wsgi will not be forced to port 8888 by
devstack. Use apache proxy now and the endpoint will be like:
http://IP/messaging by default.
Change-Id: I413cd24a9ef70a8bbada46d63d5dfdff09366b3e
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:
1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.
2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.
Also replace policy.json to policy.yaml ref from doc and tests.
[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: I595b8c7cad7bb02486c8f0dd29fdc40789fc8e50
TEMPEST_SERVICES global variable is not supported
by devstack since long back.
- I380dd20e5ed716a0bdf92aa02c3730359b8136e4
- I9c24705e494689f09a885eb0a640efd50db33fcf
Service availability of tempest known services will be
set by devstack with local check.
- I02be777bf93143d946ccbb8e9eff637bfd1928d4
This commit removes the unused TEMPEST_SERVICES setting
Related-Bug: #1743688
Change-Id: Iee8b10716efc6d48e97a3bcf3dafcc722239b2e3
The plugin has been split into its own repository[1] in accordance with
Queens Goal "Split Tempest Plugins into Separate Repos/Projects[2]".
This patch removes the local copy as well as the setuptools entry point.
We can also now remove the autodoc_tree_excludes pbr option since
there's no more plugin to exclude and it defaults to [setup.py].
[1] http://git.openstack.org/cgit/openstack/zaqar-tempest-plugin
[2] https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html
Implements: blueprint zaqar-tempest-plugin
Change-Id: Ia52d7f0a18e4b55260dc994f0802a96109280e24
By default, CORS middleware can allow requests from any origin. So it's not
necessary to use the 'enabled' option.
Closes-bug: #1677049
Co-Authored-By: wangxiyuan<wangxiyuan@huawei.com>
Change-Id: Id80e17466400937bba9fbb4aa2a2b65de9d62252
Add the new middleware CORS for Zaqar
It only supports for WSGI.
Websocket doesn't need this feature.
Change-Id: Ifc6d2d1c5dde5152cab6e3aa2f3cf9f207481267
Implements: blueprint support-cors
This adds the ability to send keystone authentified notifications using
trusts. To do so, you specify the posted URL with the "trust+" prefix,
and Zaqar will create and store a trust when subscribing to a queue, if
the trust not provided in the subscription options
It also add a capability to the webhook task to be able to send more
structured data in the notification, allowing to include the Zaqar
message in the data.
blueprint mistral-notifications
DocImpact
Change-Id: I12b9c1b34cdd220fcf1bdc2720043d4a8f75dc85
Add a sample configuration for running the wsgi transport using uwsgi,
and make devstack uses it, while running zaqar-server with websocket
transport.
This allows running both websockets and wsgi transports on devstack.
Change-Id: Ifac7461ec6b0501b1b9021030d9c173cf368a59b
Zaqar can be installed in two ways using devstack:
- using old approach called "hooks"
- using new approach called "devstack plugin"
So, if we try to install it using only devstack plugin enabling it as following:
"enable_plugin zaqar https://github.com/openstack/zaqar"
in localrc file, then we get nothing in a result. Because Devstack plugin tries
to enable zaqar using 'enable_service zaqar' [1].
But, then, devstack performs action verifying that 'zaqar-server' is
enabled. [2]
This leads to that zaqar is not installed at all.
For the moment, Zaqar installation works in CI because 'zaqar-server' is
enabled by other means using hooks.
[1]: https://github.com/openstack/zaqar/blob/bfcc60c1/devstack/settings#L4
[2]: https://github.com/openstack/zaqar/blob/bfcc60c1/devstack/plugin.sh#L246
Change-Id: I3c55756171e772d5c9e69066e0434ace5da0f852
Closes-Bug: #1476583
Instead of using `zaqar-server` as the service name in devstack, use
zaqar. This will allow for future services to be added.
Change-Id: I65667da3783130876ed781b2659000b82fa15e37
Depends-On: If5c91ebe136017cea2eeecf62a580d050e49617d
This, besides making devstack slimner, will give us more control on
what's in the plugin and it'll allow us to experiment with different
configurations.
Change-Id: I38c6cf71e2ae73f60e4494d853fee5796aa1f0f8
