openstack
/
neutron
Code Issues Proposed changes

[Docs] Fix info about provider bridge name in the bridge_mappings 

Previously in all our install guides there were info that name of the
physical interface should be put in the bridge_mappings config option in
ths OVS agent's config. This wasn't correct as bridge_mappings expects
there bridge name instead.

Change-Id: I0698aa4621a15c1927ad2c352501cea02e6ee70c
This commit is contained in:
Slawek Kaplonski 2023-10-26 11:25:53 +02:00
parent 53f4fd6b9f
commit 842f2f8e6c
12 changed files with 191 additions and 59 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
doc/source/install/compute-install-option1-obs.rst
View File

@ -13,19 +13,30 @@ networking infrastructure for instances and handles security groups.
complete the following actions:
* In the ``[ovs]`` section, map the provider virtual network to the
provider physical network interface:
provider physical bridge:
.. path /etc/neutron/plugins/ml2/openvswitch_agent.ini
.. code-block:: ini
[ovs]
bridge_mappings = provider:PROVIDER_INTERFACE_NAME
bridge_mappings = provider:PROVIDER_BRIDGE_NAME
.. end
Replace ``PROVIDER_INTERFACE_NAME`` with the name of the underlying
provider physical network interface. See :doc:`environment-networking-obs`
for more information.
Replace ``PROVIDER_BRIDGE_NAME`` with the name of the bridge connected to
the underlying provider physical network.
See :doc:`environment-networking-obs`
and :doc:`../admin/deploy-ovs-provider` for more information.
* Ensure ``PROVIDER_BRIDGE_NAME`` external bridge is created and
``PROVIDER_INTERFACE_NAME`` is added to that bridge
.. code-block:: bash
# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME
# ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAME
.. end
* In the ``[securitygroup]`` section, enable security groups and
configure the Open vSwitch native or the hybrid iptables firewall driver:

19
doc/source/install/compute-install-option1-rdo.rst
View File

@ -13,20 +13,31 @@ networking infrastructure for instances and handles security groups.
complete the following actions:
* In the ``[ovs]`` section, map the provider virtual network to the
provider physical network interface:
provider physical bridge:
.. path /etc/neutron/plugins/ml2/openvswitch_agent.ini
.. code-block:: ini
[ovs]
bridge_mappings = provider:PROVIDER_INTERFACE_NAME
bridge_mappings = provider:PROVIDER_BRIDGE_NAME
.. end
Replace ``PROVIDER_INTERFACE_NAME`` with the name of the underlying
provider physical network interface. See :doc:`environment-networking-rdo`
Replace ``PROVIDER_BRIDGE_NAME`` with the name of the bridge connected to
the underlying provider physical network.
See :doc:`environment-networking-rdo` and :doc:`../admin/deploy-ovs-provider`
for more information.
* Ensure ``PROVIDER_BRIDGE_NAME`` external bridge is created and
``PROVIDER_INTERFACE_NAME`` is added to that bridge
.. code-block:: bash
# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME
# ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAME
.. end
* In the ``[securitygroup]`` section, enable security groups and
configure the Open vSwitch native or the hybrid iptables firewall driver:

21
doc/source/install/compute-install-option1-ubuntu.rst
View File

@ -13,19 +13,30 @@ networking infrastructure for instances and handles security groups.
complete the following actions:
* In the ``[ovs]`` section, map the provider virtual network to the
provider physical network interface:
provider physical bridge:
.. path /etc/neutron/plugins/ml2/openvswitch_agent.ini
.. code-block:: ini
[ovs]
bridge_mappings = provider:PROVIDER_INTERFACE_NAME
bridge_mappings = provider:PROVIDER_BRIDGE_NAME
.. end
Replace ``PROVIDER_INTERFACE_NAME`` with the name of the underlying
provider physical network interface. See :doc:`environment-networking-ubuntu`
for more information.
Replace ``PROVIDER_BRIDGE_NAME`` with the name of the bridge connected to
the underlying provider physical network.
See :doc:`environment-networking-ubuntu` and
:doc:`../admin/deploy-ovs-provider` for more information.
* Ensure ``PROVIDER_BRIDGE_NAME`` external bridge is created and
``PROVIDER_INTERFACE_NAME`` is added to that bridge
.. code-block:: bash
# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME
# ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAME
.. end
* In the ``[securitygroup]`` section, enable security groups and
configure the Open vSwitch native or the hybrid iptables firewall driver:

21
doc/source/install/compute-install-option2-obs.rst
View File

@ -13,21 +13,22 @@ networking infrastructure for instances and handles security groups.
complete the following actions:
* In the ``[ovs]`` section, map the provider virtual network to the
provider physical network interface and configure the IP address of
provider physical bridge and configure the IP address of
the physical network interface that handles overlay networks:
.. path /etc/neutron/plugins/ml2/openvswitch_agent.ini
.. code-block:: ini
[ovs]
bridge_mappings = provider:PROVIDER_INTERFACE_NAME
bridge_mappings = provider:PROVIDER_BRIDGE_NAME
local_ip = OVERLAY_INTERFACE_IP_ADDRESS
.. end
Replace ``PROVIDER_INTERFACE_NAME`` with the name of the underlying
provider physical network interface. See :doc:`environment-networking-obs`
for more information.
Replace ``PROVIDER_BRIDGE_NAME`` with the name of the bridge connected to
the underlying provider physical network.
See :doc:`environment-networking-obs`
and :doc:`../admin/deploy-ovs-provider` for more information.
Also replace ``OVERLAY_INTERFACE_IP_ADDRESS`` with the IP address of the
underlying physical network interface that handles overlay networks. The
@ -36,6 +37,16 @@ networking infrastructure for instances and handles security groups.
the management IP address of the compute node. See
:doc:`environment-networking-obs` for more information.
* Ensure ``PROVIDER_BRIDGE_NAME`` external bridge is created and
``PROVIDER_INTERFACE_NAME`` is added to that bridge
.. code-block:: bash
# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME
# ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAME
.. end
* In the ``[agent]`` section, enable VXLAN overlay networks and enable
layer-2 population:

21
doc/source/install/compute-install-option2-rdo.rst
View File

@ -13,21 +13,22 @@ networking infrastructure for instances and handles security groups.
complete the following actions:
* In the ``[ovs]`` section, map the provider virtual network to the
provider physical network interface and configure the IP address of
provider physical bridge and configure the IP address of
the physical network interface that handles overlay networks:
.. path /etc/neutron/plugins/ml2/openvswitch_agent.ini
.. code-block:: ini
[ovs]
bridge_mappings = provider:PROVIDER_INTERFACE_NAME
bridge_mappings = provider:PROVIDER_BRIDGE_NAME
local_ip = OVERLAY_INTERFACE_IP_ADDRESS
.. end
Replace ``PROVIDER_INTERFACE_NAME`` with the name of the underlying
provider physical network interface. See :doc:`environment-networking-rdo`
for more information.
Replace ``PROVIDER_BRIDGE_NAME`` with the name of the bridge connected to
the underlying provider physical network.
See :doc:`environment-networking-rdo`
and :doc:`../admin/deploy-ovs-provider` for more information.
Also replace ``OVERLAY_INTERFACE_IP_ADDRESS`` with the IP address of the
underlying physical network interface that handles overlay networks. The
@ -36,6 +37,16 @@ networking infrastructure for instances and handles security groups.
the management IP address of the compute node. See
:doc:`environment-networking-rdo` for more information.
* Ensure ``PROVIDER_BRIDGE_NAME`` external bridge is created and
``PROVIDER_INTERFACE_NAME`` is added to that bridge
.. code-block:: bash
# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME
# ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAME
.. end
* In the ``[agent]`` section, enable VXLAN overlay networks and enable
layer-2 population:

21
doc/source/install/compute-install-option2-ubuntu.rst
View File

@ -13,21 +13,22 @@ networking infrastructure for instances and handles security groups.
complete the following actions:
* In the ``[ovs]`` section, map the provider virtual network to the
provider physical network interface and configure the IP address of
provider physical bridge and configure the IP address of
the physical network interface that handles overlay networks:
.. path /etc/neutron/plugins/ml2/openvswitch_agent.ini
.. code-block:: ini
[ovs]
bridge_mappings = provider:PROVIDER_INTERFACE_NAME
bridge_mappings = provider:PROVIDER_BRIDGE_NAME
local_ip = OVERLAY_INTERFACE_IP_ADDRESS
.. end
Replace ``PROVIDER_INTERFACE_NAME`` with the name of the underlying
provider physical network interface.
See :doc:`environment-networking-ubuntu` for more information.
Replace ``PROVIDER_BRIDGE_NAME`` with the name of the bridge connected to
the underlying provider physical network.
See :doc:`environment-networking-ubuntu` and
:doc:`../admin/deploy-ovs-provider` for more information.
Also replace ``OVERLAY_INTERFACE_IP_ADDRESS`` with the IP address of the
underlying physical network interface that handles overlay networks. The
@ -36,6 +37,16 @@ networking infrastructure for instances and handles security groups.
the management IP address of the compute node. See
:doc:`environment-networking-ubuntu` for more information.
* Ensure ``PROVIDER_BRIDGE_NAME`` external bridge is created and
``PROVIDER_INTERFACE_NAME`` is added to that bridge
.. code-block:: bash
# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME
# ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAME
.. end
* In the ``[agent]`` section, enable VXLAN overlay networks and enable
layer-2 population:

21
doc/source/install/controller-install-option1-obs.rst
View File

@ -226,19 +226,30 @@ networking infrastructure for instances and handles security groups.
complete the following actions:
* In the ``[ovs]`` section, map the provider virtual network to the
provider physical network interface:
provider physical bridge:
.. path /etc/neutron/plugins/ml2/openvswitch_agent.ini
.. code-block:: ini
[ovs]
bridge_mappings = provider:PROVIDER_INTERFACE_NAME
bridge_mappings = provider:PROVIDER_BRIDGE_NAME
.. end
Replace ``PROVIDER_INTERFACE_NAME`` with the name of the underlying
provider physical network interface. See :doc:`environment-networking-obs`
for more information.
Replace ``PROVIDER_BRIDGE_NAME`` with the name of the bridge connected to
the underlying provider physical network.
See :doc:`environment-networking-obs`
and :doc:`../admin/deploy-ovs-provider` for more information.
* Ensure ``PROVIDER_BRIDGE_NAME`` external bridge is created and
``PROVIDER_INTERFACE_NAME`` is added to that bridge
.. code-block:: bash
# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME
# ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAME
.. end
* In the ``[securitygroup]`` section, enable security groups and
configure the Open vSwitch native or the hybrid iptables firewall driver:

21
doc/source/install/controller-install-option1-rdo.rst
View File

@ -224,19 +224,30 @@ networking infrastructure for instances and handles security groups.
complete the following actions:
* In the ``[ovs]`` section, map the provider virtual network to the
provider physical network interface:
provider physical bridge:
.. path /etc/neutron/plugins/ml2/openvswitch_agent.ini
.. code-block:: ini
[ovs]
bridge_mappings = provider:PROVIDER_INTERFACE_NAME
bridge_mappings = provider:PROVIDER_BRIDGE_NAME
.. end
Replace ``PROVIDER_INTERFACE_NAME`` with the name of the underlying
provider physical network interface. See :doc:`environment-networking-rdo`
for more information.
Replace ``PROVIDER_BRIDGE_NAME`` with the name of the bridge connected to
the underlying provider physical network.
See :doc:`environment-networking-rdo`
and :doc:`../admin/deploy-ovs-provider` for more information.
* Ensure ``PROVIDER_BRIDGE_NAME`` external bridge is created and
``PROVIDER_INTERFACE_NAME`` is added to that bridge
.. code-block:: bash
# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME
# ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAME
.. end
* In the ``[securitygroup]`` section, enable security groups and
configure the Open vSwitch native or the hybrid iptables firewall driver:

21
doc/source/install/controller-install-option1-ubuntu.rst
View File

@ -225,19 +225,30 @@ networking infrastructure for instances and handles security groups.
complete the following actions:
* In the ``[ovs]`` section, map the provider virtual network to the
provider physical network interface:
provider physical bridge:
.. path /etc/neutron/plugins/ml2/openvswitch_agent.ini
.. code-block:: ini
[ovs]
bridge_mappings = provider:PROVIDER_INTERFACE_NAME
bridge_mappings = provider:PROVIDER_BRIDGE_NAME
.. end
Replace ``PROVIDER_INTERFACE_NAME`` with the name of the underlying
provider physical network interface. See :doc:`environment-networking-ubuntu`
for more information.
Replace ``PROVIDER_BRIDGE_NAME`` with the name of the bridge connected to
the underlying provider physical network.
See :doc:`environment-networking-ubuntu`
and :doc:`../admin/deploy-ovs-provider` for more information.
* Ensure ``PROVIDER_BRIDGE_NAME`` external bridge is created and
``PROVIDER_INTERFACE_NAME`` is added to that bridge
.. code-block:: bash
# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME
# ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAME
.. end
* In the ``[securitygroup]`` section, enable security groups and
configure the Open vSwitch native or the hybrid iptables firewall driver:

21
doc/source/install/controller-install-option2-obs.rst
View File

@ -237,21 +237,22 @@ networking infrastructure for instances and handles security groups.
complete the following actions:
* In the ``[ovs]`` section, map the provider virtual network to the
provider physical network interface and configure the IP address of
provider physical bridge and configure the IP address of
the physical network interface that handles overlay networks:
.. path /etc/neutron/plugins/ml2/openvswitch_agent.ini
.. code-block:: ini
[ovs]
bridge_mappings = provider:PROVIDER_INTERFACE_NAME
bridge_mappings = provider:PROVIDER_BRIDGE_NAME
local_ip = OVERLAY_INTERFACE_IP_ADDRESS
.. end
Replace ``PROVIDER_INTERFACE_NAME`` with the name of the underlying
provider physical network interface. See :doc:`environment-networking-obs`
for more information.
Replace ``PROVIDER_BRIDGE_NAME`` with the name of the bridge connected to
the underlying provider physical network.
See :doc:`environment-networking-obs`
and :doc:`../admin/deploy-ovs-provider` for more information.
Also replace ``OVERLAY_INTERFACE_IP_ADDRESS`` with the IP address of the
underlying physical network interface that handles overlay networks. The
@ -260,6 +261,16 @@ networking infrastructure for instances and handles security groups.
the management IP address of the controller node. See
:doc:`environment-networking-obs` for more information.
* Ensure ``PROVIDER_BRIDGE_NAME`` external bridge is created and
``PROVIDER_INTERFACE_NAME`` is added to that bridge
.. code-block:: bash
# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME
# ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAME
.. end
* In the ``[agent]`` section, enable VXLAN overlay networks and enable
layer-2 population:

21
doc/source/install/controller-install-option2-rdo.rst
View File

@ -239,21 +239,22 @@ networking infrastructure for instances and handles security groups.
complete the following actions:
* In the ``[ovs]`` section, map the provider virtual network to the
provider physical network interface and configure the IP address of
provider physical bridge and configure the IP address of
the physical network interface that handles overlay networks:
.. path /etc/neutron/plugins/ml2/openvswitch_agent.ini
.. code-block:: ini
[ovs]
bridge_mappings = provider:PROVIDER_INTERFACE_NAME
bridge_mappings = provider:PROVIDER_BRIDGE_NAME
local_ip = OVERLAY_INTERFACE_IP_ADDRESS
.. end
Replace ``PROVIDER_INTERFACE_NAME`` with the name of the underlying
provider physical network interface. See :doc:`environment-networking-rdo`
for more information.
Replace ``PROVIDER_BRIDGE_NAME`` with the name of the bridge connected to
the underlying provider physical network.
See :doc:`environment-networking-rdo`
and :doc:`../admin/deploy-ovs-provider` for more information.
Also replace ``OVERLAY_INTERFACE_IP_ADDRESS`` with the IP address of the
underlying physical network interface that handles overlay networks. The
@ -262,6 +263,16 @@ networking infrastructure for instances and handles security groups.
the management IP address of the controller node. See
:doc:`environment-networking-rdo` for more information.
* Ensure ``PROVIDER_BRIDGE_NAME`` external bridge is created and
``PROVIDER_INTERFACE_NAME`` is added to that bridge
.. code-block:: bash
# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME
# ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAME
.. end
* In the ``[agent]`` section, enable VXLAN overlay networks and enable
layer-2 population:

21
doc/source/install/controller-install-option2-ubuntu.rst
View File

@ -240,21 +240,22 @@ networking infrastructure for instances and handles security groups.
complete the following actions:
* In the ``[ovs]`` section, map the provider virtual network to the
provider physical network interface and configure the IP address of
provider physical bridge and configure the IP address of
the physical network interface that handles overlay networks:
.. path /etc/neutron/plugins/ml2/openvswitch_agent.ini
.. code-block:: ini
[ovs]
bridge_mappings = provider:PROVIDER_INTERFACE_NAME
bridge_mappings = provider:PROVIDER_BRIDGE_NAME
local_ip = OVERLAY_INTERFACE_IP_ADDRESS
.. end
Replace ``PROVIDER_INTERFACE_NAME`` with the name of the underlying
provider physical network interface.
See :doc:`environment-networking-ubuntu` for more information.
Replace ``PROVIDER_BRIDGE_NAME`` with the name of the bridge connected to
the underlying provider physical network.
See :doc:`environment-networking-ubuntu`
and :doc:`../admin/deploy-ovs-provider` for more information.
Also replace ``OVERLAY_INTERFACE_IP_ADDRESS`` with the IP address of the
underlying physical network interface that handles overlay networks. The
@ -263,6 +264,16 @@ networking infrastructure for instances and handles security groups.
the management IP address of the controller node. See
:doc:`environment-networking-ubuntu` for more information.
* Ensure ``PROVIDER_BRIDGE_NAME`` external bridge is created and
``PROVIDER_INTERFACE_NAME`` is added to that bridge
.. code-block:: bash
# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME
# ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAME
.. end
* In the ``[agent]`` section, enable VXLAN overlay networks and enable
layer-2 population: