Kolla Ansible 22.1.0 Modernizes OpenStack Automation with Upstream Core Bumps and Role Refactoring

The OpenStack project has published Kolla Ansible 22.1.0 as part of its 2026.1 release series, delivering targeted improvements and maintenance updates for containerized OpenStack deployment automation. The new release formally updates its supported automation engine baseline to Ansible 12 (ansible-core 2.19) and Ansible 13 (ansible-core 2.20). Alongside this runtime bump, the update brings substantial role restructuring: the long-standing `common` role and inventory group have been renamed to `kolla_toolbox`, log rotation and collection tasks have been extracted into dedicated `cron` and `kolla_logs` roles, and host bootstrapping tasks have transitioned into `ansible-collection-kolla`. The release also prunes legacy and unmaintained services, including Zun, Kuryr, InfluxDB v1, and the legacy Neutron Linux Bridge mechanism driver, while standardizing API services on uWSGI. For DevOps practitioners and cloud infrastructure teams maintaining large-scale OpenStack footprints, these changes address both operational reliability and code health. Raising the baseline to newer ansible-core releases ensures that deployment workflows benefit from upstream performance enhancements, better variable scoping, and the latest security patches. Concurrently, decomposing large deployment roles into distinct, single-purpose roles simplifies debugging and speeds up orchestration tasks across multi-node environments. This release highlights a broader, well-established industry trend across the infrastructure as code (IaC) landscape: the modularization of enterprise automation. As the Ansible ecosystem has decoupled the foundational core engine from domain-specific collections, large orchestration projects like Kolla Ansible must continuously refactor their legacy playbooks into modular collections and container-aware structures. By eliminating deprecated components like first-generation InfluxDB and legacy network drivers, the project reduces technical debt and streamlines integration with modern cloud-native monitoring and networking layers. In practice, infrastructure teams planning an upgrade must evaluate their current inventories and custom playbooks before applying 22.1.0. Any existing overrides targeting the `kolla-toolbox` group or deployment tags must be renamed to match the new `kolla_toolbox` syntax. Operators should also verify their control plane health checks—particularly around Nova Scheduler restarts, where default retry windows have been extended—to avoid transient container health alert failures during automated rollout operations.