openstack/openstack-helm
Code Issues Proposed changes

[doc] Open vSwitch: Remove auto_bridge_add support

Browse Source 
We have two functionally identical places where we add bridges, one in
the neutron chart and one in the openvswitch chart.

It makes more sense to do it only in the neutron chart as that aligns
with the linux_bridge configuration and also is where the
bridge_mappings are specified.

Change-Id: Ia3ff1dd262ffaea64ff9a8380ca19b67af191428
Depends-on: xxx
This commit is contained in:
Chris Wedgwood 2018-09-10 02:24:36 +00:00
parent 399f99a721
commit 7b4bb40f77
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/devref/networking.rst
View File

@ -269,17 +269,19 @@ by :code:`neutron-ovs-agent`. The IP is set in init container and shared between
init container and main container with :code:`neutron-ovs-agent` via file
:code:`/tmp/pod-shared/ml2-local-ip.ini`.
Configuration of OVS bridges can be done via
`neutron/templates/bin/_neutron-openvswitch-agent-init.sh.tpl`. The
script is configuring the external network bridge and sets up any
bridge mappings defined in :code:`network.auto_bridge_add`. These
values should be align with
:code:`conf.plugins.openvswitch_agent.ovs.bridge_mappings`.
openvswitch-db and openvswitch-vswitchd
+++++++++++++++++++++++++++++++++++++++
This runs the OVS tool and database. OpenVSwitch chart is not Neutron specific,
it may be used with other technologies that are leveraging the OVS technology,
such as OVN or ODL.
Configuration of OVS is done via configuration scripts
`openvswitch/templates/bin/_openvswitch-vswitchd.sh.tpl`. The script is configuring
the external network bridge and sets up any bridge mappings defined in
:code:`network.auto_bridge_add`.
A detail worth mentioning is that ovs is configured to use sockets, rather
than the default loopback mechanism.