openstack/kolla-ansible.git/ansible/roles/neutron/templates/ml2_conf.ini.j2, branch stable/2026.1

Remove unsupported ovn_emit_need_to_frag option

2026-09-08T13:34:59+00:00

This option was removed from Neutron in 2026.1 [1]. It was true by default since 2025.1 anyway [2]. [1] https://review.opendev.org/c/openstack/neutron/+/962881 [2] https://review.opendev.org/c/openstack/neutron/+/930608 Change-Id: I7b393ad92eb82506023cffbfd43888d37b305c9a Signed-off-by: Pierre Riteau (cherry picked from commit 93cab7f37a3b8fd308efb933c357b40dd18a948a)

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

Fix boolean representation in all configurations

2025-03-13T17:19:27+00:00

In the past, we agreed to use lowercase letters for boolean representation. This patch implements exactly that, just changing True -> true, False -> false. Change-Id: Ia601d84283dd8bc45e56e1029106de8836139173

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

Configure OVN to emit "need to frag" packets in case of MTU mismatch

2023-08-29T10:08:53+00:00

It is useful when external network's MTU is lower then internal geneve networks. Host kernel needs to be in version >= 5.2 for this option to work. All Kolla supported host operating systems have higher kernel version. Change-Id: Id64e99b07e2bb5e6c97b784f4ffedafc7e7de188

Fix incorrect config of linuxbridge multiple external networks

2021-07-27T09:11:42+00:00

multiple external networks are supported by linuxbridge and OVS. Currently the config template only works for OVS Closes-Bug: #1863935 Change-Id: I9da331e007c25c4a760839c566831769a68507a9

OVN Support

2020-04-09T05:40:12+00:00

Implement OVN Ansible role. Implements: blueprint ovn-controller-neutron-ansible Depends-On: https://review.opendev.org/713422 Change-Id: Icd425dea85d58db49c838839d8f0b864b4a89a78

Split out OVS/Linuxbridge agent configs from ml2_conf.ini

2019-11-27T13:42:48+00:00

Change-Id: I799993728112a525e34cfbc4e786a10f0ed03be9

Remove Neutron integration with ONOS

2019-11-18T15:39:19+00:00

Change-Id: Ie35ea07b8b6f95cbb56eb722ae2366c00243e562

Remove OpenDaylight role

2019-11-18T11:57:32+00:00

Opendaylight support has been deprecated in Train - time to remove it. Change-Id: I3a61bfbcbf366c327ea3e25d2424bc3fedca29f0