This commit migrate all event trigger policies into code [1].
Like oslo.config, with oslo.policy, we can define all of
default rules in code base and only change some rules
via policy file. Another thing that we should use yaml
format instead of json format.
This commit also remove policy.json file usage completely.
[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Dai Dang-Van <daidv@vn.fujitsu.com>
Change-Id: Icd674fdc248e5b9c63f9e7d0f47c53288291ff07
devstack has removed screen completely in
I8c27182f60b0f5310b3a8bf5feb02beb7ffbb26a. This patch cleans up any
remaining references to screen from the Mistral devstack plugin.
Change-Id: I56d6fe2c6957f9a6b5cc30d7570288ceed8b9f35
Depends-On: I8c27182f60b0f5310b3a8bf5feb02beb7ffbb26a
It does not make sense to use MISTRAL_BRANCH as the default setting
for MISTRAL_DASHBOARD_BRANCH. When testing a gerrit patch manually
with devstack, it bombs out because it can't find the gerrit ref.
Change-Id: Ic8527fc95673337b200e10279ea9f244323e61fa
Currently Mistral has own configuration for keystone
auth middleware, many parameters of which are deprecated [1].
It's not desired behavior and it is suggested to use recommended
devstack configuration function to prevent possible errors if
something is changed in keystone deployment in the future.
This patch fixes this situation and implements official
"configure_auth_token_middleware" function support.
[1] 712438ebf9/keystonemiddleware/auth_token/_auth.py (L29-L35)
Change-Id: I5f50ca6b773b61c35f93488e64a1b95d3ace9c2c
Closes-bug: #1697662
The rabbit options are deprecated, transport_url should be used. The
right interface is ini_rpc_backend, let's use that.
Change-Id: I39aee6e2a3152062a471a8f984445b9d9af4bf85
The puppet module puppet-mistral is moving to use a proper keystone
authtoken module. This supports that transition. A follow on patch
will remove the transition code.
Change-Id: Ief32ae01372c8c8d32fc5e2c89a2927510983a5b
use identity_uri to set up keystone connection settings to
avoid wrong keystone uri settings.
Change-Id: I4b0836a6a241de2ddebf175445fd86a0bf8dcf85
Closes-bug: #1684050
Add support for enabling WSGI in Apache for the devstack plugin. This
will allow an additional CI gate.
Change-Id: I953dbdab71029b392f8846c50fa3d801c293cc5a
The devstack mistral compatibility was broken by a recent patch in
devstack. This patch is intended to fix the issue by removing the
dependency on deleted env variables.
Change-Id: I768168fa95f5bc010815af5ff03117edb245137b
Closes-Bug: #1644194
This test class doesn't fully test event engine functions, because
we can not send real notifications to the internal message queue to
trigger the specified workflows.
So, before notification is supported in Mistral, we can only test the API
functions.
Change-Id: I4289dac17f19cd2ce3c214c5625f3b7d9db605de
Implements: blueprint event-notification-trigger
It enables user to set flag
'MISTRAL_USE_KOMBU_DRIVER' in local.conf on their
devstack. With this flag set to 'TRUE', mistral
would autamiatically be installed with kombu driver
enabled.
This change is needed for adding new devstack gate
that would test kombu driver
Change-Id: I462aa17107a9a55396a87a8c46fa3a8dac338fac
Mistral api access can be restricted base on role
by modifying /etc/mistral/policy.json file.
Change-Id: I4c78ca4cc04d25f46aea55948bce339cfe460ff0
Implements: blueprint mistral-customize-authorization
After pip upgrading following error has occured during
mistral installation:
Invalid requirement, parse error at "'[-e]'"
I assume that this is because of extra '-e' flag that was passed
in mistral script and that is redundant ('-e' flag will be added
automatically in setup_develop function).
Change-Id: Ifed16935b045c723881a9da157a8759eea421c2c
For implemetation of ha gate and ha/destructive scenarios it would
be better to run mistral services in separate processes to easily manage
them.
Change-Id: I85ec81d11a2ecef5a256f93526d8c8498f2ebae0
Partially-implements: blueprint mistral-ha-gate
oslo_messaging has created separate config file sections for
messaging configuration.
refer to:
https://review.openstack.org/#/c/219356/
Change-Id: I1ceec1657d2d0b1b1df5ebfb8c85fd3d977afdfa
After this commit 'gate-mistral-devstack-dsvm' will install
mistral from commit and latest released python-mistralclient,
'gate-mistralclient-devstack-dsvm' will install python-mistralclient
from commit and mistral from master.
Partially implements: blueprint mistral-making-dsvm-gates-voting
Change-Id: Ia0c9bb84412b39c571565db1f00188c4e0db71fc
Since all mistral requirements are match with global requirements
it is more correct to use setup_develop function.
Info about this function and difference with setup_package
function can be found here:
https://github.com/openstack-dev/devstack/blob/master/inc/python
Change-Id: I8b283df8734675f92d9bc8266bafe7cece6fb5f9
Start using devstack's feature 'Externally Hosted Plugins' [1], that allows
to install Mistral using upstream Devstack without need to put some additional
files manually.
To enable Mistral with Devstack just put following in local[rc] file:
enable_plugin mistral https://github.com/openstack/mistral
[1] http://docs.openstack.org/developer/devstack/plugins.html#externally-hosted-plugins
Implements blueprint devstack-plugin
Change-Id: Ia2f188a6eb369a495a7e0f20534fdd02bafcf49a