openstack/kolla-ansible.git/tests/templates/inventory.j2, branch stable/2026.1

Drop zun and kuryr

2026-04-27T05:18:03+00:00

Zun is broken in 2026.1, it has been released broken and there are no reviews on the patch to fix it [1]. [1]: https://review.opendev.org/c/openstack/zun/+/982362 Depends-On: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/986150 Change-Id: I8ced621754d03c44b7672dd94fc3d7d2173ac734 Signed-off-by: Michal Nasiadka

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

Merge "cinder: Change default destination for cinder-volume/backup containers"

2026-04-20T09:15:13+00:00

Merge "Implement neutron-ovn-vpn-agent"

2026-04-17T15:06:26+00:00

cinder: Change default destination for cinder-volume/backup containers

2026-04-17T13:43:47+00:00

Kolla-Ansible defaulted for long time to deploy cinder-volume/backup containers on storage group, which is good for Cinder LVM deployments. Problem is - majority of deployments does not use Cinder LVM backend - they use mainly Ceph (based on OpenStack User Survey) and probably some other proprietary vendors which are API driven. Let's change the default to reflect reality. If a user has cinder lvm enabled - we will deploy it as it was before If a user has both cinder lvm and something else enabled - we will deploy cinder-volume and cinder-backup in both places (cinder group and storage group) If a user doesn't have cinder lvm enabled - we deploy only in the cinder group Change-Id: Ia4a874de8f1b8eab8ff688eab4c6af013449c18c Signed-off-by: Michal Nasiadka

Implement neutron-ovn-vpn-agent

2026-04-17T09:07:00+00:00

This patch implements vpnaas for OVN environments. It deploys a standalone neutron-ovn-vpn-agent on neutron nodes. The container no longer requires 'privileged: true'. Running as the 'neutron' user with specific kernel capabilities ensures the agent can manage network namespaces and interfaces without full privileges. Added capabilities: - NET_ADMIN # manage interfaces, IPs, routing, firewall - SYS_ADMIN # create/manage network namespaces - SYS_PTRACE # allow 'ip netns exec' attach to processes - DAC_OVERRIDE # bypass file read/write restrictions - DAC_READ_SEARCH # allow directory traversal and file read - SETPCAP # retain capabilities for privileged ops Added security options: - apparmor=unconfined # disable AppArmor confinement - seccomp=unconfined # disable seccomp filtering - label=disable # disable SELinux/labeling Depends-On: https://review.opendev.org/c/openstack/kolla/+/924302 Closes-Bug: #2048392 Change-Id: I961b1407ae1402d146f0c09924df8e007e331af5 Signed-off-by: Joachim de Groot Signed-off-by: Piotr Milewski

Merge "Add OpenStack Network Exporter for Prometheus"

2026-04-16T15:54:22+00:00

Add OpenStack Network Exporter for Prometheus

2026-04-16T08:24:57+00:00

This is for gathering OVS/OVN related metrics. See: https://github.com/openstack-k8s-operators/openstack-network-exporter Depends-On: https://review.opendev.org/c/openstack/kolla/+/951971 Change-Id: I5752b3fe6457dcf2f191326a85c548584b5675b1 Signed-off-by: Doug Szumski

common: Rename role to kolla_toolbox

2026-04-14T18:03:27+00:00

Renaming it to kolla_toolbox to comply with Ansible Galaxy role naming standard Change-Id: I5e3cbcd5e8028574eeab148f1e2222378f121a22 Signed-off-by: Michal Nasiadka

Merge "kolla-logs: break out from common role"

2026-04-09T18:48:51+00:00