kayobe/releasenotes/notes/neutron-physical-networks-861c2eca701360e8.yaml
Mark Goddard ad64ebc921 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 extends the 'physical_network' network attribute to make 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.

Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/922320
Change-Id: I214444c60653f484fcda6275cc725879d14f9e7a
2024-09-06 10:00:50 +00:00

11 lines
353 B
YAML

---
features:
- |
Adds support for customising Neutron physical network names using the
``physical_network`` network attribute.
upgrade:
- |
The ``physical_network`` attribute must now be applied consistently
to all external networks in Kayobe configuration. If any external
network has the attribute, then all others must also.