In Puppet 3 there was a need to use absolute
names to prevent issues. Since Puppet 4 everything
is absolute by default which makes this not needed.
We need to change this everywhere so that we can
revert the pin in [1] that now prevents us from
using the latest version of the puppet-lint check
puppet-lint-absolute_classname_check that properly
checks that we dont use absolute names.
[1] https://review.opendev.org/#/c/697742/
Change-Id: I78b74fbeb08be7234189e4d266412fb7fb7a73c0
Moves all the <module>::debug parameters
to be set in <module>::logging::debug instead.
This is so that we can remove the deprecated
logging options in the init classes of all the
modules.
Change-Id: I107be315a6e1a0429c32d02b9a1df8a8957bb7ab
puppet-mistral switched to www_authenticate_uri in
[1], update puppet-openstack-integration for the same.
[1] https://review.openstack.org/#/c/558436/
Change-Id: I77c6dcbbc256bc279beeb2d718046a504b5ca817
This patch refactors all creation of RabbitMQ resources such
as users and ACLs to a define called openstack_integration::mq_user.
This will make sure RabbitMQ is automatically installed as well,
as there are times where dependencies to RabbitMQ are added to things
like Keystone which break Beaker tests in other repos (but we don't
know they're broken until the change merges).
In addition, instead of setting up dependencies on the tagged services,
we use the anchors provided which should hopefully test against them
as well.
Change-Id: Ib122ddd105529de5e12389cc9db2e4e09ec4ad54
Introduce configuration parameters to specify the oslo.messaging
rpc or notification backend as one of rabbit, amqp. The default
config is to use rabbit broker for both rpc and notification. Selection
of amqp for rpc will use brokerless qpid-dispatch router.
This patch:
* Adds notification_transport_url parameter across services where needed
* Adds rpc and notification parameters to config
* Adds qdr for rpc amqp1 configuration
* Modifies scenario001 for dual messaging backends
* supports ssl config
Depends-On: Id6ebc4ce8b0ffdb0be92a758dbf89c84c3274725
Change-Id: Ia2a79a2e1482f6f72426bc81c8e6d2a04cb211e3
Mistral running on mod_wsgi should only have 1 thread per worker. This
sets threads to 1 and reenabled all Mistral smoke tests.
Change-Id: I2f423b42cbff35449e8f59dcbde113dc88038f78
Closes-Bug: #1671505
This reverts commit 4d6b918cefaad43ef1c3d0ee018bca067b2cc5e2.
It activates Mistral testing again, module one test that fails all the
time:
https://bugs.launchpad.net/mistral/+bug/1654555
Change-Id: I763fd9b13ba94d1e76682a7a1c4264d7507c922c
The rabbit_host, rabbit_hosts, rabbit_userid, rabbit_password,
rabbit_port and rabbit_virtual_host parameters are being deprecated.
This change updates the p-o-i tests to use the default_transport_url for
the rabbit connection instead.
Change-Id: Icb15ad3b5d75a35afcb685f4ae03c5755031fc3d
Depends-On: I43ac3079da9e52179457ca1a34f4faee60d5617b
Depends-On: Ie63457370ae37ef5af5878b1a97b8bafa80a8189
Depends-On: Ia0c5b5072431bbc186c8b96b7f034e68e9248af3
Depends-On: I43500ac7be4296ea534266fa14ca37fc700b0092
Depends-On: If4dfe8b82518fc4e590731a805ee3115b11f4f47
Depends-On: I00d4782693c1f67b82673624d4d36822c9762303
Depends-On: If83c0f0e61a08061334536399a42767a305966b7
Do not merge, testing with v3 auth
* Deploy Mistral on scenario003
* Run Tempest tests for Mistral
* Bump repo to recent RDO repo that contains a fix in Mistral to make
Tempest tests working.
Change-Id: Ia43427cc207ee5b7b95e9610f06a568992fb58cd
