openstack/kolla-ansible.git/doc/source/reference/networking, branch stable/2025.1

[stable-2025.1] valkey: Add ansible role

2026-04-10T12:47:45+00:00

This is a non-trivial backport of Valkey deployment that is required for migration to Rocky Linux 10 before upgrading to Flamingo/Gazpacho. Additional subcommand and playbook to migrate from Redis to Valkey will be added in a follow-up. Cephadm bits backported from I51823808c4e4ac08ae8f080aacf6a3759589571d Co-Authored-By: Bartosz Bezak Change-Id: I613d471e5f1e6d563d3853761d8432cba60f3c4c Signed-off-by: Michal Nasiadka Signed-off-by: Bartosz Bezak

ovn-db: Add OVN_NB_DB and OVN_SB_DB env variables

2025-10-08T16:13:23+00:00

It will make running ovn-nbctl and ovn-sbctl working on all nodes irrespective of their cluster role. Excerpt from ovn-nbctl: --db database The OVSDB database remote to contact. If the OVN_NB_DB en‐ vironment variable is set, its value is used as the de‐ fault. Otherwise, the default is unix:/ovnnb_db.sock, but this default is unlikely to be useful outside of single-ma‐ chine OVN test environments. Closes-Bug: #2116313 Change-Id: I85f7bfd0aaa6f2d426ddb28950acbbca9d385aac Signed-off-by: Michal Nasiadka (cherry picked from commit bdd98eca87890666f66b8b3d920f7ce0948ace44)

Run ML2/OVS agents processes in separate containers

2025-04-30T17:14:17+00:00

It's an experimental feature, disabled by default (but enabled by default in our CI). It's based on TripleO ,,version'' that was their fix for the linked bug. Closes-Bug: #1891469 Depends-On: https://review.opendev.org/c/openstack/kolla/+/946215 Change-Id: Iaa1e687152db8351bc0e9b10e66f412860ac13a5

ovn: Add support for OVN SB Relay

2025-03-20T13:50:53+00:00

Add support for deploying OVN SB relays [1]. This is enabled by default to improve large scale scenarios. Default mechanism deploys one relay group per 50 ovn-controller hosts and uses random but idempotent method to choose a relay for a given host. neutron-server and Octavia will connect directly to SB cluster, not via the relays. kolla-ansible check subcommand does not support ,,iterated'' containers for now - but will be introduced in a subsequent patch. [1]: https://docs.ovn.org/en/latest/tutorials/ovn-ovsdb-relay.html Co-Authored-By: Krzysztof Tomaszewski Depends-On: https://review.opendev.org/c/openstack/kolla/+/928898 Change-Id: Id7d6973668d8b2b194913b533f8cb756c6708536

docs: Correct typo in variable name

2025-02-19T20:52:20+00:00

This commit addresses a typo in the documentation where the variable "neutron_physical_network" was incorrectly used. The correct variable name is "neutron_physical_networks", which reflects the actual value used in the code. Closes-Bug: #2088062 Change-Id: I5d4a7895d54aebcf0612e72d315defeda37bb178

Docs update - kolla-ansible cli parameters

2024-12-18T13:31:42+00:00

With rewrite of kolla-ansible CLI to Python in I9749b320d4f5eeec601a055b597dfa7d8fb97ce2 the order of parameters have to be: `kolla-ansible ` Change-Id: I1bd4a7f96f77c34fb46ca21f37023dddf73e8f05 Closes-bug: 2087920

Merge "Fix octavia-interface timeout"

2024-09-18T14:43:48+00:00

Fix octavia-interface timeout

2024-07-17T13:57:54+00:00

Added Restart=on-failure policy to octavia-interface systemd unit Added octavia_interface_wait_timeout variable to control TimeoutStartSec in octavia-interface systemd unit Change-Id: I9de6c27131ce78e85aac56ea5d91d9740fd58354 Closes-Bug: 2067036

Add support for customising Neutron physical network names

2024-06-19T13:15:51+00:00

Previously Kolla Ansible hard-coded Neutron physical networks starting at physnet1 up to physnetN, matching the number of interfaces in neutron_external_interface and bridges in neutron_bridge_name. Sometimes we may want to customise the physical network names used. This may be to allow for not all hosts having access to all physical networks, or to use more descriptive names. For example, in an environment with a separate physical network for Ironic provisioning, controllers might have access to two physical networks, while compute nodes have access to one. This change adds a neutron_physical_networks variable, making it possible to customise the Neutron physical network names used for the OVS, OVN, Linux bridge and OVS DPDK plugins. The default behaviour is unchanged. Change-Id: Ib5b8ea727014964919c6b3bd2352bac4a4ac1787

Re-add the neutron-fwaas

2024-04-29T07:43:16+00:00

neutron-fwaas has become active again Depends-On: https://review.opendev.org/c/openstack/kolla/+/914855 Change-Id: Ie5a7b2da9a351e8f47a1ae830bb2fee0a8e35e38