Fix broken links

Issue-ID: NONRTRIC-1042
Change-Id: I576f7abe7d9fd0a5ad27039fe01a4e7aa26c836d
Signed-off-by: saul.gill <saul.gill@est.tech>

diff --git a/docs/overview.rst b/docs/overview.rst
index 60515a0..da5d94c 100644 (file)
--- a/docs/overview.rst
+++ b/docs/overview.rst
@@ -114,7 +114,7 @@ Maintains (persistent) cache of RAN's A1 Policy information.
 Implementation:
 
 - Implemented as a Java Spring Boot application.
-- Wiki: `A1 Policy Management Service in ONAP <https://wiki.onap.org/pages/viewpage.action?pageId=84672221>`_ .
+- Wiki: `A1 Policy Management Service in ONAP <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16444961/O-RAN+A1+Policies+in+ONAP>`_ .
 - Repo: *nonrtric/plt/a1policymanagementservice*.
 - Documentation at the :doc:`A1 Policy Management Service documentation site <a1policymanagementservice:index>`.
 
@@ -133,7 +133,7 @@ Mediation point for A1 interface termination in SMO/NONRTRIC.
 Implementation:
 
 - Repo: *nonrtric/plt/sdnca1controller*
-- Wiki: `A1 Adapter/Controller Functions in ONAP <https://wiki.onap.org/pages/viewpage.action?pageId=84672221>`_ .
+- Wiki: `A1 Adapter/Controller Functions in ONAP <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16444961/O-RAN+A1+Policies+in+ONAP>`_ .
 
 A1 Interface / Near-RT-RIC Simulator
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

diff --git a/docs/use-cases.rst b/docs/use-cases.rst
index c9f4d39..d1e7d7d 100644 (file)
--- a/docs/use-cases.rst
+++ b/docs/use-cases.rst
@@ -23,7 +23,7 @@ O-RU Front-Haul Recovery
 
 This use case is a non-real-world closed-loop use case to demonstrate automated recovery when the front-haul connection between an O-DU and O-RU is reset.
 An application in the NONRTRIC senses the fault from the O-RU (O1-FM) and initiates a NETCONF reset operation (O1-CM) using the OAM controller.
-More details about the use case can be found on the O-RAN SC wiki: `RSAC <https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=20878423>`_ and `OAM <https://wiki.o-ran-sc.org/display/OAM/Closed+loop+use+case>`_.
+More details about the use case can be found on the O-RAN SC wiki: `RSAC <https://lf-o-ran-sc.atlassian.net/wiki/spaces/RICNR/pages/15075523/Control+Loops+for+O-RU+Fronthaul+Recovery+usecase+G+Release>`_ and `OAM <https://wiki.o-ran-sc.org/display/OAM/Closed+loop+use+case>`_.
 
 Non-RT RIC provides multiple implementation versions of the recovery part of the use case. One in the form of a python
 script, one utilizing the ONAP Policy Framework, and one Go version that utilizes Information Coordination Service (ICS).
@@ -42,7 +42,7 @@ All parts are Dockerized and can be started as individual containers, in the sam
 ONAP Policy Solution
 ++++++++++++++++++++
 
-There is also another solution for performing the front-haul recovery that is based on `ONAP Policy Framework <https://wiki.onap.org/display/DW/Policy+Framework+Project>`_.
+There is also another solution for performing the front-haul recovery that is based on `ONAP Policy Framework <https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16230647/Policy+Framework+Project>`_.
 A TOSCA Policy has been created that listens to DMaaP Message Router, makes a decision on an appropriate remedy and then signals the decision as a configuration change message via
 REST call to the OAM controller.