kolla-ansible/releasenotes/notes/neutron-physical-networks-5b908bed9809c3b4.yaml
Mark Goddard 64dcfb7291 Add support for customising Neutron physical network names
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
2024-06-19 14:15:51 +01:00

7 lines
200 B
YAML

---
features:
- |
Adds a ``neutron_physical_networks`` variable for customising Neutron
physical network names. The default behaviour of using ``physnet1`` to
``physnetN`` is unchanged.