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

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

trivial fix
Change-Id: Ib415382c9d33ebf0c877c7eb1e8a22b90c92a3a0
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: I9213197e468deb05a0e98536c658a465e967843a
Signed-off-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@advanced.host>

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

Change-Id: Ic391e0a716d560d8fb1c71578e968bedb1c9ac52
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: I256c0e3e12f8a2b5e957180c215703ce324db8fe
Co-authored-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>
Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>

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

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

This should allow to simplify and remove complex logic from the
integrated repo.
Change-Id: I4ddcc3c15c7fec696d6b689eaa234288436e8dd3
Signed-off-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@advanced.host>

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

For MR:
https://review.opendev.org/c/openstack/openstack-ansible-os_trove/+/951590
Change-Id: I14fae301c3093262671094e79323b7bef8abc450

If operator needs to enter guest agent instance for troubleshooting,
they need to create a keypair, upload it as Trove user specifically,
create a security group and define it's UUID in trove.conf
This process is quite cumbersome and time consuming, thus this
patch implements mentioned fuctionality and can be enabled
with a single variable.
Process is alike to what we have and been using for Octavia for a while.
Change-Id: I29984c565c808bca79ef39a02e79d9b015a70786

This fixes an issue, when a host group was passed to mq_setup role,
and delegate logic uses group name instead of host inside of the
group for delegating tasks.
While this patch might break already in-place workarounds, it's
quite important to fix the issue properly, as workarounds are not
trivial and requires quite some understanding of the process.
Closes-Bug: #2111406
Change-Id: Ic5747e29050cced51a71a4b4e71352f231758ed8

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

Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/942775
Needed-By: https://review.opendev.org/c/openstack/openstack-ansible-os_cinder/+/942783
Change-Id: I374856552c0b2d3fb2f49cb16b737c175585356d

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

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

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

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

As Trove is broken for 2024.1 due to db migration issues, we effectively
disabling upgade jobs by replacing metal template which include upgrades
with LXC template which does not.
This allows not to maintain job list independently in repo while not
introducing NV failing jobs to Gate pipeline.
Change-Id: I59cbe475a54ca9e12578886f2dac6921fd370d63

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

<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.
Change-Id: I6b168e0bfbc0cf0fa3847a5cdfd9f6dda3d1d64e

This unifies approach for common resource management, like image
uploads.
With that we also split network creation with information fetch about it
to include role only once and save execution time.
Change-Id: Ib0126a0ac70aa613296a8d6e1ca61b34e22b02c2

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

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

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

In order to allow definition of policies per service, we need to add variables
so 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: I9faab7b89cc870a3580c622d3a9bab79c7500e8e

As it's recommended to have an independent RabbitMQ cluster for Trove
Guestagent, we need to make it possible to easily use also different
user/password set for it.
It's also important to control quorum queues independently, as migration
between quorum queues and classic queues for guestagent cluster
is quite cumbersome and potentially should be avoided as might
bring severe disturbances.
Change-Id: Ib68778a8cb8535d7400be04f02d332ba0344d20e

While adding support for quorum queues it was missed to reflect changes
for guestagent settings, which leads to invalid configuration
Closes-Bug: #2056663
Change-Id: Id8a428686287ec4067c5eeec12d65329d0248669

While adding TLS support for RabbitMQ it was missed to configure
notifications for Trove guestagent.
Related-Bug: #2056663
Change-Id: Iad29d9f4f344861e3fa9a959c2c03d5a3f87c430

With efforts to create a resources in same, unified way,
we convert tempest role to use openstack_resources
for creating and managing openstack resources, like projects, flavors,
networks, images, etc. This should reduce maintenance costs
in case of futher collection updates and unify approach.
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/878794
Change-Id: I848ab09f8b6c81681f0ce0b5c0cc53b5653791c5

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

Right now we are not using any constraints for docs and releasenotes builds.
This has resulted in docs job failures once Sphinx 7.2.0 has been released.
The patch will ensure that constraints are used an we should not face
simmilar issue again.
TOX_CONSTRAINTS_FILE is updated by Release bot once new branch is created,
so it should always track relevant constraints.
Some extra syntax-related changes can apply, since patch is being passed
through ConfigParser, that does not preserve comments and align indenting.
Change-Id: I8c1c5c930a72ffd0d79ffeab46421c04b7ced0ca

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

By overriding the variable `trove_backend_ssl: True` HTTPS will
be enabled, disabling HTTP support on the trove 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: I15223354a28f0cc6c203f0cb3a19b9af834d4158

Change-Id: I53f50f5c7e56bdadd0456bfdeee1900a5fc91a89

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

With ansible-collection version 2.0 return of project_info module
has changed. We need to adopt usage of module return to the new format.
Change-Id: Ib4f3ced7f2175e5187f8c16f88fbfbcb3a472d0b

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

With commit [1] to collection output structure of networks_info module
has been changed. With that we adpot to the new format.
[1] 9272146cf7
Change-Id: Ia0d50b96a4af59352a89c566137d8b0208338b6b