Overview

Project Name	Enter the name of the project
Target Release Name	Kohn
Project Lifecycle State	Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company	AT&T, Nokia, Wipro, Huawei, ChinaTelecom, EST

Scope

What is this release trying to address?

Release Focus

DCAE Focus for R11 is on following

Address DCAE transformation carry-over items
- Common Template Enhancement for dcaegen2-services-common (For support for dynamic configuration update via ConfigMap)
- DR Feed configuration cleanup
- Bug fixes for MOD/Helm-gen (log.path setting override)
Support TSC approved ONAP Usecases and Features (details below)
Alignment with TSC/SECCOM Global requirements & TSC/SECCOM Best Practice
OpenSSF Best Practice progression (target Gold badging)
SBOM Report integration with CI and validation*
Continue AAF certificate dependency removal (by making it a configurable property)
Microservice enhancements in support for ONAP usecases/features
- SliceAnalysis Ms (under E2E Slicing/IBN/CCVPN), SON-Handler (5G SON)
Enable automated static-check code review/scan with CI/verify job
Improving code coverage across all DCAE components
DCAE backlog reduction

Kohn Usecases with DCAE impact

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
REQ-1215 - E2E Network Slicing use case enhancements for Kohn release	YES	AI/ML MS for IBN based closed Loop in E2E Network Slicing • Mainstreaming the ml-prediction-ms (New mS introduction) • Support for multiple slices (sNSSAIs) in training and prediction modules • Use CPS instead of Config DB • Remove RAN Simulator dependency Commitment from WIPRO	DCAEGEN2-3067
REQ-1212 5G SON use case enhancements for Kohn release	YES	CL message for ANR created by SON-Handler MS to be modified to align with A1-based flow/support Commitment from WIPRO	DCAEGEN2-3148
REQ-1268 - CCVPN Kohn Enhancements for Intent-based Cloud Leased Line and Transport Slicing	YES	DCAE SDK alignment for SliceAnalysis MS & enhanching AAI interface for supporting IBN CL Commitment from HUAWEI/ChinaTelecom	DCAEGEN2-3195

Kohn Features with DCAE Impact

REQ#

DCAE Commit Status

DCAE Impact Assessment

DCAE JIRA #

REQ-1214 Maintenance and Enhancement of Intent-driven Closed-loop Autonomous Networks in R11

YES

Slice Analysis enhancement

Enhancement with AAI Interface/processing for CL notification

Commitment from HUAWEI/ChinaTelecom

DCAEGEN2-3194

REQ-1207 DMaaP Enhancements for K release

Stretch-goal

Impact on DCAE components for migrating from exiting MR clients to use kafka native towards the strimzi cluster.

Dependent on resource availability

Commitment from EST

Kohn Spec with DCAE Impact

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
DCAE Helm Transformation - Post migration activities	YES	Complete the post-migration updates. Commitment from AT&T	DCAEGEN2-3119
NA	YES	VES 7.2.1 support for DCAE Microservices (outside of collectors) - TCAgen2 Commitment from Wipro	DCAEGEN2-2975
NA	Stretch-goal	AAF certificate dependency to be removed by making it a configurable property for MS DFC, RESTConf Stretch goals: Nokia for DCAEGEN2-3039 (DFC), Huawei for DCAEGEN2-3095 (RESTConf)	DCAEGEN2-3037
NA	YES	Sonarcoverage improvements for DCAE components SliceAnalysis mS, SNMPTrap, TCA-gen2, SON-Handler,DL-Handler, KPi-MS, VES-HV, VESCollector, MOD/onboardingAPI, SDK, Mapper, RESTConf, MOD/genprocessor, MOD/distributorapi Commitment from AT&T, Wipro, HUAWEI, ChinaTelecom, Nokia (* stretch-goal)	Sub-Jira under EPIC DCAEGEN2-3089
NA	YES	Automated review tool integration with CI/verify Commitment from AT&T	DCAEGEN2-3186
NA	YES	Enhancements to KPI Computation MS Support KPI to be defined spanning multiple resources Handle unavailability of required counter for calculation Commitment from Wipro	DCAEGEN2-3193 (sub-task to DCAEGEN2-2801)
REQ-358	Stretch-Goal	No root (superuser) access to database from application container TCAgen2 Commitment from Wipro	DCAEGEN2-2907
NA	YES	DMAAP SDK standardization for DCAE Microservices SliceAnalysis mS KPI-mS SON-Handler mS RESTConf* Commitment from Huawei, Wipro	DCAEGEN2-3030

Kohn POC (DCAE impact)

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
NA

Best Practices/GLOBAL Requirements

REQ#	DCAE Commit Status	DCAE Impact Assesment	DCAE JIRA #
REQ-443 - CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL Global-REQ	YES	CII badging score improvement Commitment from AT&T	DCAEGEN2-3209
REQ-1211- CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES Global-REQ	YES	Kohn DCAE (SECCOM) Commitment: AT&T, Wipro, HUAWEI, ChinaTelecom, Nokia	DCAEGEN2-3196
REQ-437 - COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8) Global-REQ	YES	(No new impact for DCAE in Kohn release)	DCAEGEN2-3196
REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) Global-REQ	No	dcaemod-designtool dcaemod-nifi-registry Exception will be filed with SECCOM for waivers due to upstream (NIFi) dependency	DCAEGEN2-3019 (J)
REQ-432 - IPv4/IPv6 dual stack support in ONAP	YES	Enhance ONAP common-service template - add IPv4/IPv6 support (No new impact for DCAE in Kohn release)	OOM-2749
REQ-441/REQ-1070 - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA - KOHN RELEASE Global-REQ	YES	New mS (ml-prediction-mS) will be complaint to the requirement. All other DCAE mS area already complaint STDOUT logging Commitment from Wipro	Tracked under DCAEGEN2-3067
REQ-1073 - Using basic image from Integration	YES	(No new impact for DCAE in Kohn release)	NA
REQ-1072 - Standardized logging fields	YES (for new Ms only)	No change planned for existing DCAE microservice. New mS (ml-prediction-mS) will be developed to be complaint to this Best-practice requirement. Commitment from Wipro	Tracked under DCAEGEN2-3067

Note: The above commitment should be consistent with Kohn Impact View per Component at M2.

New Services/Components

Following new services will be delivered under E2E Slicing usecase for IBN based closed Loop support.

ML MS (REQ-1215)
- Repository : https://git.onap.org/dcaegen2/services/tree/components/ml-prediction-ms (introduced as new subproject under existing repo)

Retirement/Deprecation

Acumos Adapter

DCAE MOD under assessment for EOL with London release

DCAE MOD was introduced in Frankfurt release to address following requirements:

1. Simplified and streamlined onboarding for DCAE components/microservice and distribute the deployment artifact with DCAE-Core Platform (Cloudify)
2. Provide Common Catalog for reusable DCAE microservices for Designer to leverage
3. Enable automated onboarding for ML microservices from Acumos.

With DCAE platform transformation feature, requirement #1 and #2 are less critical as the onboarding/deployment are easily managed through Helm-Charts and catalog supported through Chartmuseum (or any other registry)/With Also with Acumos project archived under LF (end of 2021), DCAE team will be assessing the need for continuation/support of DCAE MOD going forward.

Note: Certain MOD components are on java8 due to upstream dependency with Apache/Nifi project on java8 and have SECCOM exception currently.

Update 07/19/22

Following DCAE Team meeting discussion and ARC reviews, DCAE-MOD has been identified for retirement with London release. Official communication sent to ONAP DL's - https://lists.onap.org/g/onap-tsc/topic/dcae_mod_eol_with_london/92490689

Platform Maturity

Platform Maturity (i.e., S3P items) Kohn Release Platform Maturity

Green color → Target level ( details see Platform Maturity below)

Performance: Level 1
Stability: Level 2
Resiliency: Level 2
Security: Level 1+
Scalability: Level 1
Manageability: Level 1+
Usability: Level 1+

Minimum Viable Product

As DCAE transformation is underway, two different deployment options will be available. The MVP of DCAE will vary based on deployment choice and will include the necessary subcomponents supporting the primary objectives: meeting platform maturity goals and supporting the use cases.

Helm Deployment (dcaegen2-services)

- VESCollector
- TCA-gen2
- PRH
- HV_VES

DCAE-MOD deployment is optional and will include following component (controlled via helm chart configuration under OOM)

- Genprocessor
- MOD/NiFI UI
- Distributorapi
- Runtimeapi
- Onboardingapi

Note: DCAE-MOD is possible candidate for retirement with Kohn release.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

Epics

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Stories

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Longer term roadmap

With DCAE Helm transformation initiate completed, achieved the major goal on platform simplification. As ONAP progresses for supporting new usecase, will assess them for support.

Following are some initiatives under consideration

- Policy/CLAMP: Continue integration for Control Loop design for Helm-based deployment of DCAE Services*
- Assess DCAEMOD platform continued support/retirement
- Prometheus Integration
- TICK/ELK Integration

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Deliverable Name	Deliverable Description
Component spec	All ms added into DCAE should provide meta data representation of the component itself; will be used to generate design flow under MOD and enable blueprint generation
configbinding	SourceCode/Docker image
policy side-car	SourceCode/Docker image
dcae-healthcheck	SourceCode/Docker image
dcae-mod	SourceCode/jar/Docker image/Documentation
VES Collector	SourceCode/Docker image/helm charts
HV_VES Collector	SourceCode/jar/Docker image/helm charts
PRH	SourceCode/jar/Docker image/helm charts
TCA-GEN2	SourceCode/jar/Docker image/helm charts
DFC	SourceCode/Docker image/helm charts
RESTConf	SourceCode/Docker image/helm charts
PM-MAPPER	SourceCode/Docker image/helm charts
VES-MAPPER	SourceCode/Docker image/helm charts
DL Components (DES, DL-ADMIN, DL-FEEDER)	SourceCode/Docker image/helm charts
SLICE ANALYSIS	SourceCode/Docker image/helm charts
KPI-MS	SourceCode/Docker image/helm charts
HEARTBEAT MS	SourceCode/Docker image/helm charts
SON-HANDLER MS	SourceCode/Docker image/helm charts
PMSH	SourceCode/Docker image/helm charts
ML/Prediction Ms	SourceCode/Docker image/helm charts

Note: Only default platform components and bootstrapped MS is listed on table above. DCAE also include dynamic service components deployed based on usecases. For a complete set of available DCAE MS - refer https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/release-notes.html#deliverables

Sub-Components

List all sub-components part of this release. Activities related to sub-components must be in sync with the overall release.

Sub-components are repositories and are consolidated in a single centralized place. Edit the Resources and Repositories (Deprecated) in the centralized page.

ONAP Dependencies

List the other ONAP projects you depend on.

DCAE depends on the the following components as part of the general ONAP architecture:

- AAI: DCAE MS retrieves and updates VNF data from/to AAI
- DMaaP: Message bus for communication with other components in the solution
- Policy/CLAMP - Policy - For managing application configuration policy.
- OOF - For SON handler support

Architecture

High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

Indicate where your project fit within the Amsterdam architecture diagram_1.0.0.pptx.

DCAE Interfaces

Platform Maturity

Kohn Release Platform Maturity

Refering to 2017-06-28 CII badging for ONAP.pptx and Platform Maturity Requirements (aka Carrier Grade), fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

Area	Actual Level	Targeted Level for current Release	Comments
Performance	1	1	Level 0: no performance testing done Level 1: baseline performance criteria identified and measured (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component) Level 2: performance improvement plan created Level 3: performance improvement plan implemented for 1 release (improvement measured for equivalent functionality & equivalent hardware)
Stability	2	2	Level 0: none beyond release requirements Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load) Level 2: 72 hour platform-level soak test (random test transactions with 80% code coverage; steady load) Level 3: track record over 6 months of reduced defect rate
Resiliency	2	2	0 – none 1 – manual failure and recovery (< 30 minutes) 2 – automated detection and recovery (single site) 3 – automated detection and recovery (geo redundancy)
Security	1	1+	Level 0: None Level 1: CII Passing badge Including no critical and high known vulnerabilities > 60 days old Level 2: CII Silver badge, plus: All internal/external system communications shall be able to be encrypted. All internal/external service calls shall have common role-based access control and authorization using CADI framework. Level 3: CII Gold badge
Scalability	1	1	Level 0: no ability to scale Level 1: supports single site horizontal scale out and scale in, independent of other components Level 2: supports geographic scaling, independent of other components Level 3: support scaling (interoperability) across multiple ONAP instances
Manageability	1	1+ (Except logging, all other requirements are met)	Level 1: All ONAP components will use a single logging system. Instantiation of a simple ONAP system should be accomplished in <1 hour with a minimal footprint Level 2: A component can be independently upgraded without impacting operation interacting components Component configuration to be externalized in a common fashion across ONAP projects All application logging to adhere to ONAP Application Logging Specification v1.2 Implement guidelines for a minimal container footprint Level 3 Transaction tracing across components
Usability	1	1+	Level 1: User guide created Deployment documentation API documentation Adherence to coding guidelines Level 2: API Documentation All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines All existing APIs must be documented in Swagger 2.0 Level 3 Consistent UI across ONAP projects Usability testing conducted API Documentation All new API’s, all external APIs, and all existing API’s that are modified must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines Level 4 API Documentation All API’s for a given project must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines

API Incoming Dependencies

List the API this project is expecting from other projects. Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

API Name	API Description	API Definition Date	API Delivery date	API Definition link (i.e.swagger)
Policy Engine	API for retrieving configuration policy updates via Policy Sidecar	Currently Available	Currently Available	NA
Policy (PDP)	API to push DCAE MS configuration/policy models	Currently Available	Currently Available
A&AI	API invoked for information enhancements	Currently Available	Currently Available
DMaaP Message Router	API for topic publish /subscribe	Currently Available	Currently Available
DMaaP Bus Controller	DMaaP Bus Controller is a part of DMaaP that provides topic provisioning; this is the API for topic provisioning.	Currently Available	Currently Available
OOF	PCI Optimization API http://{OOF-host}:{port}/api/oof/v1/pci http://{pcims-host}:{port}/callbackUrl Call back URL for SON-MS (to provide PCI optimization results)	Currently Available	Currently Available
~~ConfigDB~~	~~http://{ConfigDB-host/IP}:{port}/SDNCConfigDBAPI/getNbrList/{cellId}/{ts} (Get neighbor list for a cell Id)~~ ~~http://{ConfigDB-host/IP}:{port}/SDNCConfigDBAPI/getPnfName/{cellId}/{ts} (Get the PNF name for a cell Id)~~	~~Currently Available~~	~~Currently Available~~	~~This will be replaced with CPS for Jakarta~~
CPS	Used by SON-handler and Slice-Analysis MS	Currently Available	Currently Available

API Outgoing Dependencies

API this project is delivering to other projects.

API Name	API Description	API Definition Date	API Delivery date	API Definition link (i.e.swagger)
VES Collector	API for VNFs to send VES data	Currently Available		No change for this release
Healthcheck	API for querying DCAE component healthcheck	Currently Available	R4	No change for this release
DCAE Onboarding API	API for publishing DCAE spec into MOD	Currently Available	R6	No change for this release
Data Extraction Service (DES)	API for data retrieval and simple computation from DL-Handler maintained storages (For R8, this will be used by DCAE components such Slice-Analyis MS) and UUI	Currently Available	R8	No change for this release
PMSH	API support for Subscription/Filters/Measurement group management	Currently Available	R10	No change for this release https://git.onap.org/dcaegen2/tree/docs/sections/apis/pmsh_swagger.json
SliceAnalysis Ms	API support for data aggregation based on NSI/NSSI; this will be consumed by OOF	Currently Available	R10	No change for this release https://git.onap.org/dcaegen2/tree/docs/sections/apis/swagger_slice_analysis.json https://lf-onap.atlassian.net/wiki/download/attachments/16493831/slice-analysis-swagger.yaml?version=1&modificationDate=1640159785000&api=v2

Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected. List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

Name	Description	Version
NIFI	Apache NIFI	1.9.x
Consul		version based on OOM

In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.

Testing and Integration Plans
- - Unit Test addition will be enforced part of new code submission; all components are required to maintain 55% codecoverage at the minumum.
    - https://sonarcloud.io/organizations/onap/projects?search=dcaegen2
  - Functional test plan
    - DCAE R11 Kohn Testplan
  - CSIT tests will continue to be supported for existing components and new components
    - DCAE has number of CSIT - https://jenkins.onap.org/view/CSIT/; these will be continued to be validated during course of development for this release.
  - Pairwise testing will be done in the WindRiver Dev lab; below wiki page captures the test planned
    - DCAE R11 Kohn Pairwise Test
  - DCAE also has number of Smoke test (Example - https://logs.onap.org/onap-integration/daily/onap_daily_pod4_master/01-18-2021_08-01/) enabled for several components/flows; these test are validated part of gating for new container releases
    - Bulk-PM
    - HV-VES
    - VES
    - PRH flow
    - MOD

Gaps

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release. List identified release gaps (if any), and its impact.

Gaps identified	Impact

Known Defects and Issues

Provide a link toward the list of all known project bugs.

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Risk identified

Mitigation Plan

Contingency Plan

Due to upstream dependency on NIFI project, some of MOD (NiFI) components (designtool/gen-processor/nifi-registry) will remain in java 8

Request exception for SECCOM.

Assess migration to use new MOD2 standalone components for onboarding (based on community resource/support)

MOD retirement under assessment

DCAEGEN2-3019 (J)

Resources

Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:dcae

Release Milestone

The milestones are defined at the Release Planning: Kohn and all the supporting project agreed to comply with these dates.

Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

Date to be completed by	Sprint	Deliverable
Key dates for KOHN release - Release Planning: Kohn
M2	DCAE Kohn Sprint 1 (Planning)	Finalize DCAE scope and committment API definition formalized and shared with impacted teams
M2-M3	DCAE Kohn Sprint 2 (Development)	50% or more of Functional delivery completed Atleast 60% of release/compliance (coverage & security) Integration test plan completed CSIT/automated test delivery SDK version to be baselined and released Documentation repo updates (API updates & new MS/component) - Kohn Documentation
M3	DCAE Kohn Sprint 3 (Code Freeze)	All code intended for release MUST be submitted into gerrit Minimum 80% code coverage 100% of release/compliance (Global Requirement & Best-Practice) Validate deployment/integration with ONAP/DCAE deploy Update OOM chart/documentation to reflect correct version Documentation update for deployment/configuration/architecture/logging
M4	DCAE Kohn Sprint 4 (Container Release/artifact)	Finalize containers/jars for release and submit patch to OOM for revisions
RC	Integration/Sign-Off	Fix Integration blockers and high priorty issue Demo for new components introduced Pair-wise testing Branching

Documentation, Training
- - Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
  - Highlight the team contributions to the overall Release Documentation and training asset
  - High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  - Documentation includes items such as:
    - Installation instructions
    - Configuration instructions
    - Developer guide
    - End User guide
    - Admin guide

Kohn Documentation

Other Information

- Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.

- Free and Open Source Software

FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible. List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ). In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

Each project must edit its project table available at Project FOSS.

Charter Compliance

The project team comply with the ONAP TSC Charter OBSOLETE 7 1 CLEAN.pdf.

Browser not supported