NONRTRIC - Using S3 storage for ICS

Documentation updates.

Signed-off-by: PatrikBuhr <patrik.buhr@est.tech>
Issue-ID: NONRTRIC-811
Change-Id: I221d3be8c8f4c5e84a8755abd15d0dfa905002b1

diff --git a/docs/Architecture.png b/docs/Architecture.png
index 40d1eb4..6bf98dc 100644 (file)
Binary files a/docs/Architecture.png and b/docs/Architecture.png differ

diff --git a/docs/Architecture.pptx b/docs/Architecture.pptx
index 593266a..1ee2fc8 100644 (file)
Binary files a/docs/Architecture.pptx and b/docs/Architecture.pptx differ

diff --git a/docs/overview.rst b/docs/overview.rst
index d6d0a1f..b62f58f 100644 (file)
--- a/docs/overview.rst
+++ b/docs/overview.rst
@@ -28,6 +28,8 @@ One information type can be supported by zero to many data producers and can be
 .. image:: ./Architecture.png
    :width: 500pt
 
+Information Jobs and types are stored persistently by ICS in a local database. This can be either using Amazon S3 - Cloud Object Storage or file system.
+
 *********************
 Summary of principles
 *********************
@@ -37,7 +39,6 @@ Summary of principles
 * Data filtering is done at the producer.
 * A Data Consumer can create a data subscription (Information Job) regardless of the status of the data producers. The producers can come and go without any need for the Data Consumer to take any action.
   A subscription indicates the need for a type of data and the system should do its best to fulfill this.
-* Information Jobs and types are stored persistently by ICS in a local database.
 
 
 *******