openstack/openstack-ansible-os_cloudkitty - openstack-ansible-os_cloudkitty - OpenDev: Free Software Needs Free Tools

Tests removed in:
I943b8e29a6b944de15f98f222128f566d498fd1d
Change-Id: I929a9cf042f89ff9aea8d390cdd75d0c8bffb10f
Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>

trivial fix
Change-Id: Ic8e74b3b36b8747976864fcaf048e73660e3b8d6
Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>

oslo.policy can not handle policy file removal. As a result, if policy
overrides were defined at some point, but then removed, causes service
outage.
While we could add a handler trigger to restart the service
on policy removal, it's better to simplify the logic and always place an
empty policy.yaml even if no overrides are defined.
Change-Id: I3e96cbc9150e5051db19b3a93d68baf243beb17c
Signed-off-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>

Change-Id: I8624c6008240fb24c8251e9a9e7c86ee6322c473
Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>

This removes tox evs which are dependent on a tests repo framework,
which was deprecated.
Change-Id: I943b8e29a6b944de15f98f222128f566d498fd1d
Co-authored-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>
Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>

run_tests.sh was part of functional testing framwork which was
deprecated.
Vagrantfile while running integrated tests, does not contain
any supported distro
and effectively unmaintained.
Change-Id: I13f1ac24fa5bd78a32211cc4362ec33b4618b9a3
Co-authored-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>
Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>

Change-Id: Ia5781b50cfc65706857e0e477e0db6b29835abbd
Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>

Provide a direct reference to the OpenStack-Ansible deploy guide, helping users understand how to integrate a new role into their deployment.
Change-Id: I774264ff5f2370793bb9b4cdb9200c1af40153e8

Change-Id: I0a7559daa17a0db9ef0ff7ed87a4f761c5d01a1d

The tags framework has been discontinued for a long time.
https://governance.openstack.org/tc/reference/tags/
https://governance.openstack.org/tc/resolutions/20211224-tags-framework-removal.html
Change-Id: Ifcba57c68571e58b995cd60f12829b1e9c14ce1a

Since ansible-core 2.10 it is recommended to use modules via FQCN
In order to align with recommendation, we perform migration
by applying suggestions made by `ansible-lint --fix=fqcn`
Change-Id: I64308bec4805e24f369cff7bb5f7d01e3ca96d4c

In order to reduce divergance with ansible-lint rules, we apply
auto-fixing of violations.
In current patch we replace all kind of truthy variables with
`true` or `false` values to align with recommendations along with
alignment of used quotes.
Change-Id: I3e5d17d5f424643bbb3af1c58cc596b85d108626

Support is removed in oslo.messaging so we remove support in
openstack-ansible roles.
Change-Id: Ie41de2e47a092fe249d0513e8fbc28ef9ee26a3e

With ansible-core 2.16 a breaking changes landed [1] to some filters
making their result returned in arbitrary order. With that, we were
relying on them to always return exactly same ordered lists.
With that we need to ensure that we still have determenistic behaviour
where this is important.
[1] https://github.com/ansible/ansible/issues/82554
Change-Id: I93c3b386388195b5b51c0d2c64864458bcfed326

Due to the shortcoming of QManager implementation [1], in case of uWSGI
usage on metal hosts, the flow ends up with having the same
hostname/processname set, making services to fight over same file
under SHM.
In order to avoid this, we prepend the hostname with a service_name.
We can not change processname instead, since it will lead to the fight
between different processes of the same service.
[1] https://bugs.launchpad.net/oslo.messaging/+bug/2065922
Change-Id: Ice4a0310c3218b4588b8f9a212882c713b966433

It appears, that produced gnocchiclient does not respect region_name
from the auth_section, thus it needs to be defined directly for the
fetcher.
We align collector for now with fetcher, to make change backportable.
Closes-Bug: #2067084
Change-Id: If3a37b6190449e18446e65ce3b8cb70cd9038c37

With addition of storage v2 versions and v2 API it's now less trivial
to rely on overrides for storage configuration, which most likely will be
needed regardless, since v1 storages are incompatible with /v2 API,
and latter one gets disabled whenever v1 storage is in use.
With that there's no dummy storage in /v2 for testing purposes, so
we are not able to have any reasonable default out of the box.
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/920058
Change-Id: Ic0d055c98ee6e35fb28b26de8cf3d20e7e79ad87

<service>-config tags are quite broad and have a long execution
time. Where you only need to modify a service's '.conf' file and
similar it is useful to have a quicker method to do so.
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/920058
Change-Id: Iae6fb286658fc924796a29fb08979cfe9113283b

Update the zed release notes configuration to build from
unmaintained/zed.
Change-Id: I0626c23aaa23e2d446db2b0a0cfa7c38dd783738

When rabbit_stream_fanout is set to true, rabbit_qos_prefetch_count
should be set to a positive value.
This also fixes defenition of transient_quorum_queue as if
rabbit_stream_fanout is enabled - transient_quorum_queue should be also
enabled. [1]
[1] https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_rabbit.py#L726-L736
Change-Id: I2c25783d4c65aa04ad9305adf2cbb6028e1dab57

During last release cycle oslo.messaging has landed [1] series of extremely
useful changes that are designed to implement modern messaging
techniques for rabbitmq quorum queues.
Since these changes are breaking and require queues being re-created,
it makes total sense to align these with migration to quorum queues by default.
[1] https://review.opendev.org/q/topic:%22bug-2031497%22
Change-Id: I520ae8cf928404a9ed077d6e6812c4f13d0102bb

In order to be able to globally enable notification reporting for all services,
without an need to have ceilometer deployed or bunch of overrides for each
service, we add `oslomsg_notify_enabled` variable that aims to control
behaviour of enabled notifications.
Presence of ceilometer is still respected by default and being referenced.
Potential usecase are various billing panels that do rely on notifications
but do not require presence of Ceilometer.
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/914144
Change-Id: I60746cedeec323bcede3bb5aa4968f0388e262bb

In order to allow definition of policies per service, we need to add variables
to service roles, that will be passed to openstack.osa.mq_setup.
Currently this can be handled by leveraging group_vars and overriding `oslomsg_rpc_policies` as a whole, but it's not obvious and
can be non-trivial for some groups which are co-locating multiple services
or in case of metal deployments.
Change-Id: I147c08178ed359f9e445ee41fb6c368706c94800

Cloudkitty has released it's v2 API couple of cycles ago with [1]. High time to
enable it as well.
[1] https://review.opendev.org/c/openstack/cloudkitty/+/832923
Change-Id: I11838780e84d6e721033b5c7aa77c8a0ca8ea121

This change implements and enables by default quorum support
for rabbitmq as well as providing default variables to globally tune
it's behaviour.
In order to ensure upgrade path and ability to switch back to HA queues
we change vhost names with removing leading `/`, as enabling quorum
requires to remove exchange which is tricky thing to do with running
services.
Change-Id: I722aefb5290a68311faf1d44c279151e8492466a

Change-Id: I64c16cfa138b6ef4a20fdfa16ca0c6bb73d345fb

With update of ansible-lint to version >=6.0.0 a lot of new
linters were added, that enabled by default. In order to comply
with linter rules we're applying changes to the role.
With that we also update metdata to reflect current state.
Depends-On: https://review.opendev.org/c/openstack/ansible-role-systemd_service/+/888223
Change-Id: Ib51c7ec8d83ffe82c98d1c8d3200ce4510775895

By overriding the variable `cloudkitty_backend_ssl: True` HTTPS will
be enabled, disabling HTTP support on the cloudkitty backend api.
The ansible-role-pki is used to generate the required TLS
certificates if this functionality is enabled.
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/879085
Change-Id: I0566028b4737306954b544d040b52cee1fddaa1f

At the moment we don't restart services if systemd unit file is changed.
We knowingly prevent systemd_service role handlers to execute
by providing `state: started` as otherwise service will be restarted twice.
With that now we ensure that role handlers will also listen for systemd
unit changes.
Change-Id: I5d491104173dc0217fac62618c13e8ac5a57233b

Add file to the reno documentation build to show release notes for
stable/zed.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/zed.
Sem-Ver: feature
Change-Id: Ie13e1d8fee402e06ee57311c1e360324db7ea38f

With ansible-core 2.13 it tries to substitude package resolution in apt
module.
However git-core is used in Debian as transitional name, but ansible
tries to select it and provide version, which is not correct behaviour.
But since git-core is not really valid anyway, we just replace it
to workaround ansible's imperfectness.
Change-Id: Ie4b8ce21c101551505eec1529235a57e9176d3c9

This line snuck in with I81413b5ff415ee3d0b5a33189335591146e8f698
probably to bring it in line with other OSA roles, but should already
be covered by the distribution_major_version line above.
Change-Id: I8ec073f36556c5d7da2be7aae23a192266d39a5d

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: Icb1de8c7e0a5196a4df457a5d4a3ca524d4622d0

With sphinx release of 5.0.0, they changed default for language variable
to 'en' from None. With that current None valuable is not valid and should
not be used.
Change-Id: I92ad4a90f367fe95899973912edb222e84903adc

Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/839989
Change-Id: I19d8215e653d42698806c645ac4ae7747c4ea35e

Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/839989
Change-Id: I7e79f669d4b65ce067c57bda06e1887c1125ee4e

Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/839989
Change-Id: Ie0e94e91fb0547b3d5d90e405956cb0ef59312e3

Use a first_found lookup instead of a with_first_found loop so that
the 'paths' parameter can be used.
This ensures that only vars from the role are included, and not vars
from a parent calling role. This can happen when a parent role has
a higher priority vars file available for inclusion than the role
it calls.
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/839989
Change-Id: I81413b5ff415ee3d0b5a33189335591146e8f698

Change-Id: I6c3de8e6b9ac1ef9a7deaabd0fa4decb085738d1