Since pip 23.1, the wsgi_script from PBR are not installed anymore
(see [1])
So, instead, rely on the wsgi.py app which is directly bundled in
mistral source code.
[1] https://discuss.python.org/t/adding-support-for-wsgi-scripts-entrypoint/30905/11
Change-Id: Ideed8421427e865f8010b7bfca58c3f010ac6bd6
Signed-off-by: Arnaud M <arnaud.morin@gmail.com>
Since upgrade of etcd3 (see [1]), the v3aplha endpoint has been
deprecated but tooz commit (see [2]) is not yet released.
Until then, we should force the api_version=v3 to make sure the
coordination between engine is working correctly.
Closes-Bug: #2040048
Signed-off-by: Arnaud Morin <arnaud.morin@ovhcloud.com>
Change-Id: Ieade7a30a192910fc3870b173017efd481f0b18f
For python3, `python-nose` has been changed to `python3-nose` in Ubuntu
Jammy Jellyfish. This change is to update the package name to avoid an
error on exit.
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
Change-Id: I4c21b6527f37918397f7fb425075eb6c07534237
In RedHat8, python-nose is separated to 2 packages of
python2 and python3.
This patch changed devstack plugin to use the separated packages.
Change-Id: I1a3608a52c37718715cdfecc8cc2d4a7e76b1714
This config is read by tempest test weather to test
the service api that was added in ussuri
Depends-On: https://review.opendev.org/704274
Change-Id: I98ef8d60b40c13ffa0a6690841f1e27f092dfdea
This way we can test the service api later on gate
In order to use etcd in gate few changes were made:
* All identifiers must be byte type (group type, member id)
* Tooz has a built-in mechanizm for heartbeat no need to implement it
* Need to use eventlet monkey patch since etcd client uses blocking
methods
* Services name must be identical to LAUNCH_OPTIONS used in cli
* Gate coordination url should be define with a schema of etcd+http
which is the etcd gateway and works better then just etcd
Change-Id: I772651e33eada4a5c2149bfa867095c277eddeed
The default 0.0.0.0 will be good only ipv4
for ipv6 gate will fail. MISTRAL_SERVICE_HOST has always
the right ip, it is also used in apache mode so lets use
it also in standalone mode.
Change-Id: I492ccaa876c25cdb434858cb215cc94ae5b65972
In devstack if we install the client then copy the bash
completion script to its folder.
also use the standart devstack function to install the
mistral client
Change-Id: I69ca615ed446214463f8fa7a3e303ff0bf32b460
keystone_authtoken/auth_uri is deprecated [1]. Use www_authenticate_uri
instead.
keystonemiddleware in requirements and lower constraints should be increased
because www_authenticate_uri was introduced in keystonemiddleware 4.18.0.
[1] https://review.openstack.org/#/c/508522/
Change-Id: I99b0ee941d702a28fb4f392d9747d0e2257a42c8
Closes-Bug: #1788174
If mistral-lib is not processed as a required-project, it won't get
treated properly as a depends-on. This should fix that.
Change-Id: I1f42836ec549a3e56681af29738868bf5896e971
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
Arnaud M