DCAE Kohn rls note updates

second pass

Change-Id: I505679b27a3a160c22c5bc8f47d3b892a384cf51
Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com>
Issue-ID: DCAEGEN2-3236
Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com>

5 files changed, 22 insertions, 26 deletions

diff --git a/docs/sections/architecture.rst b/docs/sections/architecture.rst
index 04d41daa..370acac0 100644
--- a/docs/sections/architecture.rst
+++ b/docs/sections/architecture.rst
@@ -1,4 +1,4 @@
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.

+	.. This work is licensed under a Creative Commons Attribution 4.0 International License.

 .. http://creativecommons.org/licenses/by/4.0

 .. _architecture:

 

@@ -8,18 +8,14 @@ Architecture
 

 DCAE project provides intelligence for ONAP to support automation (via open-loop and CL) by performing network data collections, analytics & correlation and trigger actionable rootcause events.

 

-Prior to Jakara release, DCAE architecture comprised of DCAE Platform and DCAE Service components; DCAE Platform supported the functions to deploy, host and perform LCM applications of Service components.

-

-With Jakarta release, DCAE Platform component centered around Cloudify has been deprecated. All Microservice orchestration and lifecycle management will be handled through Helm/Kubernetes. 

+Prior to Jakarta release, DCAE architecture comprised of DCAE Platform and DCAE Service components; DCAE Platform supported the functions to deploy, host and perform LCM applications of Service components. With Jakarta release, these DCAE Platform components centered around Cloudify has been removed and all Microservice orchestration and lifecycle management are supported primarily through Helm/Kubernetes.

 

 The DCAE services components includes all the microservices - collectors, analytics and event processor which supports active data-flow  and processing as required by ONAP usecases. These Service components are the functional entities that realize the various 

 data collection needs, event processors for data standardization, analytics that assess collected data, and various auxiliary microservices that assist automated closed loop flows.

 

-The architecture of DCAE with Helm transformation is more flexible, microsservice oriented and supports model based component design and deployment through DCAE-MOD. Also with migration to helm, DCAE miroservice deployments can be handled independently, dependencies are captured under its helm charts.

+The architecture of DCAE with Helm transformation is more flexible, microsservice oriented and supports model based component design and deployment through DCAE-MOD. Also with migration to helm, DCAE microservice deployments can be handled independently, dependencies are captured under its helm charts.

 

-Prior to Jakarta release, DCAE components relied on Consul's distributed K-V to manage and store component configuration. However with Jakarta release, Consul dependency has been removed completely across all DCAE service components. 

-All Microservice configuration are resolved through files mounted via Configmap created part of 

-dcae-services helm chart deployment. 

+Under the Cloudify/DCAE Platform architecture, DCAE Service components relied on Consul's distributed K-V to manage and store component configuration. With Platform simplification under DCAE Transformation initiative for Kohn, Consul dependency has been removed across all DCAE service components. All Microservice configuration are currently resolved through files mounted via Configmap created part of dcae-services helm chart deployment. 

 

 

 DCAE Components

@@ -58,7 +54,7 @@ The figure below shows the DCAE architecture and how the components work with ea
   The following diagram has been created on https://app.diagrams.net/. There is an editable version of the diagram

   in repository under path docs/sections/images/architecture_diagram. Import this file to mentioned page to edit diagram.

 

-.. image:: images/R10_architecture_diagram.png

+.. image:: images/R11_architecture_diagram.png

  

 

 Deployment Scenarios

@@ -67,9 +63,9 @@ Deployment Scenarios
 Because DCAE service components are deployed on-demand following the control loop needs for managing ONAP deployed services, DCAE must

 support dynamic and on-demand deployment of service components based on ONAP control loop demands.  

 

-With DCAE Transformation to Helm completed in Jakarta/R10 release, all DCAE components deployment will be supported only via helm. 

+With DCAE Transformation to Helm completed in Jakarta/R10 release, all DCAE components deployment are supported only via helm. 

  Charts for individual MS are available under **dcaegen2-services** directory under OOM project

- (https://git.onap.org/oom/tree/kubernetes/dcaegen2-services/components). To keep the ONAP footprint minimal, only minimal set of MS

+ (https://git.onap.org/oom/tree/kubernetes/dcaegen2-services/components). To keep the ONAP footprint minimal, only minimal set of MS 

  (required for ONAP Integration usecases) are enabled by default on ONAP/DCAE deployment, which includes four DCAE services (HV VES

  collector, VES collector, PNF Registration Handler, and TCA (Gen2) analytics service).

 

@@ -78,9 +74,8 @@ More details of the DCAE deployment can be found under Installation section.
 Architectural Reference

 -----------------------

 

- - `ARC DCAE Component Description <https://wiki.onap.org/display/DW/ARC+DCAE+Component+Description+-+Jakarta-R10>`_

- - `R10 M2 ARC Proposal <https://wiki.onap.org/display/DW/DCAE+R10+M2+Architecture+Review>`_

-

+ - `ARC DCAE Component Description <https://wiki.onap.org/display/DW/ARC+DCAE+Component+Description+-+Kohn-R11>`_

+ - `R11 M2 ARC Proposal <https://wiki.onap.org/display/DW/DCAE+R11+Kohn+M2+Architecture+Review>`_

 

 Usage Scenarios

 ---------------

diff --git a/docs/sections/build.rst b/docs/sections/build.rst
index eda50be7..3f278599 100644
--- a/docs/sections/build.rst
+++ b/docs/sections/build.rst
@@ -1,4 +1,4 @@
-	.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+Y	.. This work is licensed under a Creative Commons Attribution 4.0 International License.
 .. http://creativecommons.org/licenses/by/4.0
 .. _build:
 
@@ -71,10 +71,6 @@ Below is a list of the repositories and their sub-modules, and the language they
 
 * dcaegen2.utils
 
- - onap-dcae-cbs-docker-client (Python)
- - onap-dcae-dcaepolicy-lib (Python)
- - python-discovery-client (Python)
- - python-dockering (Python)
  - scripts (bash)
 
 * dcaegen2.services.sdk (Java)
diff --git a/docs/sections/images/R11_architecture_diagram.PNG b/docs/sections/images/R11_architecture_diagram.PNG
new file mode 100644
index 00000000..d84fc7ba
--- /dev/null
+++ b/docs/sections/images/R11_architecture_diagram.PNG
diff --git a/docs/sections/installation_oom.rst b/docs/sections/installation_oom.rst
index 41cf34ab..b4db91bf 100644
--- a/docs/sections/installation_oom.rst
+++ b/docs/sections/installation_oom.rst
@@ -23,7 +23,7 @@ and invokes Kubernetes deployment operations for all the resources.
 All ONAP Helm charts are organized under the **kubernetes** directory of the **OOM** project, where roughly each ONAP component occupies a subdirectory.
 
 
-With DCAE Transformation to Helm completed in Jakarta/R10 release, all DCAE components deployment will be supported only via helm.  Charts for individual MS are available under **dcaegen2-services** directory under OOM project (https://git.onap.org/oom/tree/kubernetes/dcaegen2-services/components). With ONAP deployment, four DCAE services (HV VES collector, VES collector, PNF Registration Handler, and TCA (Gen2) analytics service) are bootstrapped via Helm charts.
+With DCAE Transformation to Helm completed in Jakarta/R10 release, all DCAE components deployment is supported only via helm.  Charts for individual MS are available under **dcaegen2-services** directory under OOM project (https://git.onap.org/oom/tree/kubernetes/dcaegen2-services/components). With ONAP deployment, four DCAE services (HV VES collector, VES collector, PNF Registration Handler, and TCA (Gen2) analytics service) are bootstrapped via Helm charts.
 
 Other DCAE Services can be deployed on-demand via their independent helm-charts. For on-demand helm chart, refer to steps described in :ref:`Helm install/upgrade section <dcae-service-deployment>`.
 
diff --git a/docs/sections/release-notes.rst b/docs/sections/release-notes.rst
index 0231fa64..c472394d 100644
--- a/docs/sections/release-notes.rst
+++ b/docs/sections/release-notes.rst
@@ -101,13 +101,16 @@ DCAEGEN2-3148 5G SON use case enhancements for Kohn release
     - CL message for ANR modified to align with A1-based flow/support
 
 DCAEGEN2-3195 CCVPN Kohn Enhancements for Intent-based Cloud Leased Line and Transport Slicing
-    - DCAE SDK alignment for SliceAnalysis MS & enhanching AAI interface for supporting IBN CL 
+    - DCAE SDK alignment for SliceAnalysis MS & enhancing AAI interface for supporting IBN CL 
 
 DCAEGEN2-3194 Maintenance and Enhancement of Intent-driven Closed-loop Autonomous Networks
     - Slice Analysis Enhancement with AAI Interface/processing for CL notification
 
 DCAEGEN2-3119 Helm Transformation - Post migration
-
+     - DCAE Common Template improvements
+     - Removed Cloudify and associated platform component charts 
+     - Removed Consul/CBS API dependency from each DCAE MS, enabling independent config management via respective charts
+     
 DCAEGEN2-2975 VES 7.2.1 support for DCAE Microservices
      - TCAgen2 enhanced to support VES 7.2.1
 
@@ -115,14 +118,15 @@ DCAEGEN2-3037 AAF certificate dependency removal
     - DFC Enhanced to support additional property to disable certificates checks
 
 DCAEGEN2-3030 DMAAP SDK standardization for DCAE Microservices
-    - SliceAnalysis MS, KPI-MS, SON-Handler MS switched to use DMAAP SDK
+    - SliceAnalysis MS, SON-Handler MS switched to use DMAAP SDK
 
 
 *Non-Functional*
 
-   - DCAEGEN2-3089 - Sonarcoverage improvements for DCAE components - SliceAnalysis mS, SNMPTrap, TCA-gen2, SON-Handler, KPi-MS, Mapper, RESTConf
-   - DCAEGEN2-3209 - CII Badging improvements
+   - DCAEGEN2-3089 - Sonarcoverage improvements for DCAE components - SliceAnalysis mS, SNMPTrap, TCA-gen2, SON-Handler, KPi-MS, Mapper, RESTConf  (meeting 80% or more coverage) 
+   - DCAEGEN2-3209 - CII Badging improvements (Silver badge completion)
    - DCAEGEN2-3196 - Vulnerability updates for several DCAE MS (TCA-gen2, DataFileCollector, HV-VES, RESTConf, VES, Mapper, PM-Mapper, PRH, SON-handler, KPI-MS, Slice-Analysis MS, DCAE-SDK, VES OpenAPI Manager)
+   - DCAEGEN2-3225 - SBOM Enablement for DCAE components  
 
 
 .. _kohn_deliverable:
@@ -158,7 +162,7 @@ Software Deliverables
    "dcaegen2/services", "components/datalake-handler", "onap/org.onap.dcaegen2.services.datalake.exposure.service:1.1.1"
    "dcaegen2/services", "components/pm-subscription-handler", "onap/org.onap.dcaegen2.services.pmsh:2.2.2"
    "dcaegen2/services", "components/slice-analysis-ms", "onap/org.onap.dcaegen2.services.components.slice-analysis-ms:1.1.5"
-   "dcaegen2/services", "components/kpi-ms", "onap/org.onap.dcaegen2.services.components.kpi-ms:1.0.9"
+   "dcaegen2/services", "components/kpi-ms", "onap/org.onap.dcaegen2.services.components.kpi-ms:1.0.10"
    "dcaegen2/services/heartbeat", "", "onap/org.onap.dcaegen2.services.heartbeat:2.4.1"
    "dcaegen2/services/mapper", "", "onap/org.onap.dcaegen2.services.mapper.vesadapter.universalvesadaptor:1.4.3"
    "dcaegen2/services/pm-mapper", "", "onap/org.onap.dcaegen2.services.pm-mapper:1.9.0"
@@ -193,6 +197,7 @@ Known Limitations, Issues and Workarounds
 -----------------------------------------
 
 
+   - DCAEGEN2-3184 DL-Feeder log error and configuration issue
 
 *Known Vulnerabilities*