Minor documentation updates 90/114990/2
authorelinuxhenrik <henrik.b.andersson@est.tech>
Tue, 17 Nov 2020 10:02:10 +0000 (11:02 +0100)
committerelinuxhenrik <henrik.b.andersson@est.tech>
Tue, 17 Nov 2020 11:40:34 +0000 (12:40 +0100)
Updated architecture picture.
Remove unused pictures.
Update consumed APIs.

Change-Id: Icede1f1326dde1287014207842eb6bc06cd6858a
Issue-ID: CCSDK-2966
Signed-off-by: elinuxhenrik <henrik.b.andersson@est.tech>
docs/architecture/architecture.rst
docs/consumedapis/consumedapis.rst
docs/media/ONAP-A1ControllerArchitecture.png [new file with mode: 0644]
docs/media/o-ran-onap-integration.png [deleted file]
docs/media/oran_architecture.png [deleted file]
docs/media/yaml_logo.png [deleted file]
docs/offeredapis/offeredapis.rst

index 3997950..bfe827b 100644 (file)
@@ -21,8 +21,8 @@ Global NBI architecture for Frankfurt release
 Following illustration provides a global view about Non-Real-Time-RIC architecture,
 integration with other ONAP components and API resource/operation provided.
 
-.. image:: ../media/o-ran-onap-integration.png
-   :width: 800pt
+.. image:: ../media/ONAP-A1ControllerArchitecture.png
+   :width: 500pt
 
 
 ***************
index bcf7267..8357e43 100644 (file)
@@ -5,14 +5,32 @@ Consumed APIs
 =============
 
 
-Policy Management Service application is interacting with one ONAP API.
+Policy Management Service application is interacting with two ONAP APIs and the A1-P API.
 
 *******
 CBS API
 *******
 
-This API is used to get the dynamic configuration of the service, such as available Near-RT RICs.
+The CBS API is used to get the dynamic configuration of the service, such as available Near-RT RICs.
 
 ::
 
     CBS_GET_ALL
+
+*********
+DMAAP API
+*********
+
+The DMaaP API is used to provide the possibility to interact with the Policy Management Service through DMaaP Message
+Router.
+
+::
+
+    DMAAP_GET_EVENTS
+
+********
+A1-P API
+********
+
+The A1-P API is used to communicate with the Near-RT RICs (north bound). All endpoints of the OSC A1 REST API and the
+standard A1 REST API version 1.1 are used.
diff --git a/docs/media/ONAP-A1ControllerArchitecture.png b/docs/media/ONAP-A1ControllerArchitecture.png
new file mode 100644 (file)
index 0000000..5951662
Binary files /dev/null and b/docs/media/ONAP-A1ControllerArchitecture.png differ
diff --git a/docs/media/o-ran-onap-integration.png b/docs/media/o-ran-onap-integration.png
deleted file mode 100644 (file)
index 5c66ae6..0000000
Binary files a/docs/media/o-ran-onap-integration.png and /dev/null differ
diff --git a/docs/media/oran_architecture.png b/docs/media/oran_architecture.png
deleted file mode 100644 (file)
index 3f99e09..0000000
Binary files a/docs/media/oran_architecture.png and /dev/null differ
diff --git a/docs/media/yaml_logo.png b/docs/media/yaml_logo.png
deleted file mode 100644 (file)
index 0492eb4..0000000
Binary files a/docs/media/yaml_logo.png and /dev/null differ
index 14fb881..0efe5ce 100644 (file)
@@ -21,7 +21,7 @@ Global ORAN architecture
 Following illustration provides a global view about **ORAN** architecture,
 integration with other ONAP components and API resource/operation provided.
 
-.. image:: ../media/oran_architecture.png
+.. image:: ../media/ONAP-A1ControllerArchitecture.png
    :width: 500pt