From aebe78405e40cc21e84ce5b91328bd7ff1380dde Mon Sep 17 00:00:00 2001 From: Guoqiang Ding Date: Fri, 24 Nov 2017 15:33:46 +0800 Subject: [PATCH] Update the doc link Change-Id: Ibb60cff222cb9ac947467dbed160d6d5e7231ff5 --- doc/source/admin/bgp-speaker.rst | 8 ++++---- doc/source/admin/system-design.rst | 6 +++--- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/source/admin/bgp-speaker.rst b/doc/source/admin/bgp-speaker.rst index e1c50050..f4d28d2d 100644 --- a/doc/source/admin/bgp-speaker.rst +++ b/doc/source/admin/bgp-speaker.rst @@ -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>`_. diff --git a/doc/source/admin/system-design.rst b/doc/source/admin/system-design.rst index 16c23f23..3148f936 100644 --- a/doc/source/admin/system-design.rst +++ b/doc/source/admin/system-design.rst @@ -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 `_ 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 `_