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
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
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
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: I884777826d6ed40d58f75ec5dfba93a876752dfe
Closes-bug: #1697662
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
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
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
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
Eyal