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
Set user_domain_name, project_domain_name and
project_name under [watcher_clients_auth]. This
is required to communicate with keystone v3.
Also set watcher_client_auth_uri and auth_url to
keystone versioned endpoint.
Depends-On: https://review.openstack.org/#/c/642973/
Change-Id: I2657791467f4a4cc40c6b82c753268eed7398253
Disable SSL as currently there are known issues in services
to work with python3 + SSL on Fedora.
Also fixed following:-
- watcher to work without SSL
- Handle source /etc/bashrc for users don't have .bashrc created
- Install python3-rbd in Fedora and RedHat > 7
Change-Id: I5b67f40ec3c687f5282c65e10b4a1ee1fe5528f3
puppet-watcher switched to www_authenticate_uri in
[1], update puppet-openstack-integration for the same.
[1] https://review.openstack.org/#/c/558437
Change-Id: Icef54f4ff165658fa519b1b84e7599d92638656d
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
According to https://review.openstack.org/#/c/419031/ the only
command to be executed to populate watcher DB is:
watcher-db-manage --config-file /etc/watcher/watcher.conf upgrade head
create_schema command is not longer needed, and in fact is not
creating table apscheduler_jobs properly.
Note that p-o-i jobs keep working because the version of APScheduler
currently in RDO creates table apscheduler_jobs automatically
in SQLAlchemyJobStore initialization. This is not longer true
in recent versions, so it will break as soon as APScheduler is
updated, so let's fix it.
[1] bf99bff8ea (diff-c47a8d544459e39b2dc3dfeb50a4ec6bR55)
Change-Id: If0338362f9b7b9c90390a836a40b0036adc958a3
We don't need this workaround anymore, we got a promotion with fixed package.
This reverts commit 2348c0c847b13374f032ee71dd17e792c43f0265.
Change-Id: I6f77b4f0978f80b05ad1b39257c490fa01fa7f05
Watcher recently added gnocchiclient as a requirement but packaging
does not have it yet so to clear up CI while we wait, let's just include
it for now.
Change-Id: Ic7d7f3bf7fec6e6689529836a6dd68bbaf8ae75c
