openstack/neutron-dynamic-routing
Code Issues Proposed changes

Update the doc link

Browse Source 
Change-Id: Ibb60cff222cb9ac947467dbed160d6d5e7231ff5
This commit is contained in:
Guoqiang Ding 2017-11-24 15:33:46 +08:00
parent 183c3fa484
commit aebe78405e
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/admin/bgp-speaker.rst
View File

@ -26,8 +26,8 @@ BGP Speaker
===========
BGP Speaker acts as a route server using BGP routing protocol. It advertises
routes to the BGP peers which are added to the BGP Speaker. Now there is a
framework that allows different `BGP drivers <../design/drivers.html>`_
to be plugged into a `dynamic routing agent <../design/agent-scheduler.html>`_.
framework that allows different `BGP drivers <../contributor/dragent-drivers.html>`_
to be plugged into a `dynamic routing agent <./agent-scheduler.html>`_.
Currently, BGP Speaker only advertises routes for a network to which it is associated.
A BGP Speaker requires association with a "gateway" network to determine eligible routes.
@ -125,7 +125,7 @@ and pass on the configuration request to the dynamic routing agent for further p
The implementation of a BGP Speaker is driver specific. During the driver interface
initialization process, needed configurations are read from the configuration file
and BGP Speaker object instance is created. For details refer to
`BGP drivers <../design/drivers.html>`_.
`BGP drivers <../contributor/dragent-drivers.html>`_.
BGP Speaker Life Cycle
~~~~~~~~~~~~~~~~~~~~~~
@ -165,4 +165,4 @@ For details refer to `Route Advertisement <./route-advertisement.html>`_.
How to work
-----------
For details refer to `Testing <../others/testing.html>`_.
For details refer to `Testing <../contributor/testing.html>`_.

6
doc/source/admin/system-design.rst
View File

@ -40,7 +40,7 @@ It advertises three classes of routes:
* Prefix routes for directly routable tenant networks with address scopes, the
nexthop is the centralized router, the same for DVR and CVR.
For details refer to `Route Advertisement <../functionality/route-advertisement.html>`_.
For details refer to `Route Advertisement <./route-advertisement.html>`_.
Neutron dynamic routing consists of `service plug-in <https://docs.openstack.org/neutron/latest/contributor/internals/plugin-api.html>`_
and agent. The service plug-in implements the Networking service extension and
@ -100,7 +100,7 @@ protocols are supported.
BGP
+++
Three kinds of APIs are available for BGP functionality.For details refer to the
`API document <./api.html>`_.
`API document <../reference/index.html>`_.
* BGP Speaker APIs to advertise Neutron routes outside the Openstack network.
* BGP Peer APIs to form peers with the remote routers.
@ -123,7 +123,7 @@ Dynamic Routing Agent (DR Agent)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dynamic routing can reside on hosts with or without other Networking service agents.
It manages and configures different dynamic routing stack through
`Common Driver API <./drivers.html>`_.
`Common Driver API <../contributor/dragent-drivers.html>`_.
.. note::
Currently, only integration with `Ryu <http://ryu.readthedocs.io/en/latest/library_bgp_speaker.html>`_