openstack/neutron
Code Issues Proposed changes

Fix "config-routed-networks" document errors

Browse Source 
Fixed "config-routed-networks" document errors reported in [1].

Related-Bug: #1923592

[1]https://review.opendev.org/c/openstack/neutron/+/791178

Change-Id: I3a0e83c1ca273582233fb7788c81e4ba298bc6d0
This commit is contained in:
Rodolfo Alonso Hernandez 2021-06-09 15:37:48 +00:00
parent f450886ff9
commit c0846c6518
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/admin/config-routed-networks.rst
View File

@ -540,7 +540,7 @@ underlying network infrastructure, not managed by Neutron.
Could be the case that the user needs to split the communication between
several hosts. It is possible to create tenant networks and connect them using
a router. To access to the router provider network, it should be connected
a router. To access to the routed provider network, it should be connected
as router gateway.
.. code-block:: bash
@ -554,14 +554,14 @@ as router gateway.
└─────────────────────┘
The routed provider network, acting as router gateway, contains all subnets
associated to the segments. In a deployment without router provided networks,
associated to the segments. In a deployment without routed provided networks,
the gateway port has L2 connectivity to all subnet CIDRs. In this case, the
gateway port has only connectivity to the attached segment subnets and its
L2 broadcast domains.
The L3 agent will create, inside the router namespace, a default route in the
gateway port fixed IP CIDR. For each other subnet no belonging to the port
fixed IP address, a onlink route is created. These routes use the gateway port
gateway port fixed IP CIDR. For each other subnet not belonging to the port's
fixed IP address, an onlink route is created. These routes use the gateway port
as routing device and allow to route any packet with destination on these
CIDRs through this port.