As of today blazar warns out on startup that using the in-process token
cache is deprecated for quite a while. In order to get rid of this warning
we add memcached configuration for keystone token.
Change-Id: Ibd80231bdb1dfe2e66e69c4538a2129c7f84c92f
In order to be more flexible regarding required plugins, we implement a
new variable that will allow to set a list of enabled filters for blazar.
With that we also enable floatingip plugin that has been added to Blazar
a while ago.
Change-Id: Iaff9284eec3a57a6470afb5e912cad17970baa2f
This change implements and enables by default quorum support
for rabbitmq as well as providing default variables to globally tune
it's behaviour.
Change-Id: If9a9ee764dd41767aaa1285903eb3c21cc0da40c
While <service>_galera_port is defined and used for db_setup
role, it's not in fact used in a connection string for oslo.db.
Change-Id: I753c328569e1ee6d69a0ad2168b6493a3c7438f9
Implement support for service_tokens. For that we convert
role_name to be a list along with renaming corresponding variable.
Additionally service_type is defined now for keystone_authtoken which
enables to validate tokens with restricted access rules
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/845690
Change-Id: I3a1c2d87a39eaf342411f3b607bc909f924944cb
- Implemented new variable ``connection_recycle_time`` responsible for SQLAlchemy's connection recycling
- Set new default values for db pooling variables which are inherited from the global ones.
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/819424
Change-Id: Ib4a0581c5bbe2b14abcd80f97ac2e36ec0dbf4b1
With PKI role in place in most cases you don't need to explicitly
provide path to the CA file because PKI role ensures that CA is trusted
by the system overall. In the meanwhile in PyMySQL [1] you must either
provide CA file or cert/key or enable verify.
Since current behaviour is to provide path to the custom CA we expect
certificate being trusted overall. Thus we enable cert verification when
galera_use_ssl is True.
[1] 78f0cf99e5/pymysql/connections.py (L267)
Change-Id: I7042118a17d533c472f09bb2098bbc3c01195477
The notification driver setup was resulting in the driver and connection string
on the same line. This is caused by the case statement and how jinja formats
the template when a case statement is present. This change modifies how the
driver string is created using a ternary, which will eliminate the case
statement and render the value of the diver correctly.
Change-Id: I9614af2d8a7e908327d2c8ee64f75070dbccfb08
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This patch add the conditional inclusion of the notification
section of the service configuration. This ensures that oslo.messaging
notifications use the correct transport for deployments that have
separate rpc and notify messaging backends. For example, if the
transport_url is not provided in the notification section of the
service configuration, the transport_url specified in the default
section will be used instead.
This patch conditionally selects the notifier driver. The noop
driver will be selected when notification publishing is disabled.
The messagingv2 driver is selected when notification publishing is
enabled.
Change-Id: I2b4c4a119fa300fb5b64eaaf947e3c688bdb6e84
Closes-Bug: #1794320
The functional test check the responsiveness of the Blazar API. A
return of 204 code from the API verifies the success.
Rest of the changes ensure compliance with all the standards required
to make the linter and docs tests pass.
Change-Id: I640877817ad1ae312436932af87ad15094616f12
This removes the systemd service templates and tasks from this role and
leverages a common systemd service role instead. This change removes a
lot of code duplication across all roles all without sacrificing features
or functionality. The intention of this change is to ensure uniformity and
reduce the maintenance burden on the community when sweeping changes are
needed.
Change-Id: Ife802766cefa8862f2b0e42f06c100b30d65edf8
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>