openstack/kolla-ansible.git/kolla_ansible/tests, branch stable/2026.1

Support multiple Nova Compute Ironic instances

2026-04-24T13:47:26+00:00

Adds support for deploying multiple instances of the Nova Compute Ironic service on the same host. This is useful in large baremetal deployments, where the sharding and/or conductor group feature is used to scale out the service. A further patch to support deploying multiple Ironic conductor instances will follow. Co-Authored-By: Bartosz Bezak Co-Authored-By: Bertrand Lanson Change-Id: Ibbddfd87e831a3775c3ed66c80b18e5070cedc90 Signed-off-by: Doug Szumski

Switch from passlib to internal bcrypt filter

2026-03-03T12:10:33+00:00

Change-Id: I1c0312aa7bdfb78fedef6c98463f25e6460f4587 Co-Authored-By: Pierre Riteau Signed-off-by: Michal Nasiadka

Merge "Try not to return loopback addresses with kolla_address in ipv4"

2026-01-30T10:37:10+00:00

glance: Switch to use uWSGI

2025-12-12T09:56:07+00:00

Glance is removing their warning around running in WSGI [1], so let's switch. [1]: https://review.opendev.org/c/openstack/glance/+/963294 Change-Id: Iae2c5ef5251d6695daf3262ed208c4bd914d7fb3 Signed-off-by: Michal Nasiadka

Try not to return loopback addresses with kolla_address in ipv4

2025-10-23T17:30:19+00:00

kolla_address does not check if the returned ip address is a loopback for ipv4 addresses, this change checks, and always try to return the first non loopback address, defaulting to the primary in case only loopbacks are available. Closes-Bug: #2085699 Change-Id: Ie8a8b6156e6db025aba94e80a4b3aa2bf72d73ef Signed-off-by: Bertrand Lanson

prometheus: Support overriding address of scrape targets

2025-02-21T14:20:17+00:00

In many cases we use the kolla_address filter to look up the IP address of the current host or another host on a particular network interface. This filter uses the host's facts to determine the IP, meaning that we must have gathered facts for the host, even if it is outside of a requested --limit. This is a limitation, since it requires that all hosts must be reachable, even if we are not directly configuring them. Most instances of this cross-host fact referencing involve a controller, since they host clustered services. The only instance found to affect compute nodes is in the prometheus role, where Prometheus server needs to know the IP address of all targets in its scrape configs. If we are able to specify the address of the scrape targets as a static variable such as a host variable, then facts would not be required for compute nodes outside of the --limit. Removing the requirement to have facts for all compute nodes has benefits for performance (gathering facts for all hosts can take a long time) and fault tolerance (we can operate when some compute hosts are unreachable). This change modifies the kolla_address filter to accept an optional override_var argument which can be used to specify the name of a host variable that may override the returned IP address. This is used in the Prometheus server configuration to allow specifying the IP address used by Prometheus server when collecting metrics from exporter using a 'prometheus_target_address' host variable. If specified, this takes precedence over the API interface address currently used. This makes it possible to statically override prometheus_target_address and avoid the cross-host fact reference. This is not a complete solution because it is not yet possible to skip the cross-host fact gathering step. Partial-Bug: #2041860 Change-Id: I207ca56362de00d8ec578333eab9e1a72e7bcd19

Fix proxysql get mariadb_backup_database_password

2023-11-16T08:35:06+00:00

Implements: Kolla Ansible Closes-Bug: #2043554 Change-Id: I5648a79b4aa1960f1984a5179e3dfc3f0982c709

haproxy: support single external frontend

2023-06-28T23:44:00+00:00

Use case: exposing single external https frontend and load balancing services using FQDNs. Support different ports for internal and external endpoints. Introduced kolla_url filter to normalize urls like: - https://magnum.external:443/v1 - http://magnum.external:80/v1 Change-Id: I9fb03fe1cebce5c7198d523e015280c69f139cd0 Co-Authored-By: Jakub Darmach

Add proxysql support for database

2022-07-29T13:05:21+00:00

Kolla environment currently uses haproxy to fullfill HA in mariadb. This patch is switching haproxy to proxysql if enabled. This patch is also replacing mariadb's user 'haproxy' with user 'monitor'. This replacement has two reasons: - Use better name to "monitor" galera claster as there are two services using this user (HAProxy, ProxySQL) - Set password for monitor user as it's always better to use password then not use. Previous haproxy user didn't use password as it was historically not possible with haproxy and mariadb-clustercheck wasn't implemented. Depends-On: https://review.opendev.org/c/openstack/kolla/+/769385 Depends-On: https://review.opendev.org/c/openstack/kolla/+/765781 Depends-On: https://review.opendev.org/c/openstack/kolla/+/850656 Change-Id: I0edae33d982c2e3f3b5f34b3d5ad07a431162844

adds firewalld configuration based on enabled services

2022-07-27T11:28:40+00:00

This change introduces automated configuration of firewalld and adds a new filter for extracting services from the project_services dict. the filter selects any enabled services and their haproxy element and returns them so they can be iterated over. This commit also enables automated configuration of firewalld from enabled openstack services and adds them to the defined zone and reloads the system firewall. Change-Id: Iea3680142711873984efff2b701347b6a56dd355