openstack/openstack-ansible
Code Issues Proposed changes

docs: remove Linux Bridge

Browse Source 
second iteration for reference documentation.

Change-Id: Idc22feb8964c02d38c65c311818c71e2d14da53b
This commit is contained in:
Ivan Anfimov
2025-05-02 12:14:49 +00:00
parent c816bf2fc0
commit 4a936c2de6
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/reference/architecture/container-networking.rst
View File

@@ -116,9 +116,9 @@ interfaces to provider bridges:
- ``host_bind_override``
- ``network_interface``
The ``host_bind_override`` override is used for LinuxBridge-based deployments,
and requires a physical interface name which will then be used by the
LinuxBridge agent for flat and vlan-based provider and tenant network traffic.
The ``host_bind_override`` key is used to replace an LXC-related interface
name with a physical interface name when a component is deployed on bare metal hosts.
It will be used to populate ``network_mappings`` for Neutron.
The ``network_interface`` override is used for Open vSwitch and OVN-based deployments,
and requires a physical interface name which will be connected to the provider bridge

6
doc/source/reference/architecture/metal-networking.rst
View File

@@ -96,9 +96,9 @@ interfaces to provider bridges:
- ``host_bind_override``
- ``network_interface``
The ``host_bind_override`` override is used for LinuxBridge-based deployments,
and requires a physical interface name which will then be used by the
LinuxBridge agent for flat and vlan-based provider and tenant network traffic.
The ``host_bind_override`` key is used to replace an LXC-related interface
name with a physical interface name when a component is deployed on bare metal hosts.
It will be used to populate ``network_mappings`` for Neutron.
The ``network_interface`` override is used for Open vSwitch and OVN-based deployments,
and requires a physical interface name which will be connected to the provider bridge