...
| REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
| YES | Slice Analysis enhancement
Commitment from HUAWEI/ChinaTelecom |
| |
| TBD | Impact on DCAE components for migrating from exiting MR clients to use kafka native towards the strimzi cluster. Commitment from EST |
| |
DCAE Helm Transformation - Post migration activities | YES | Complete the post-migration updates. Commitment from AT&T |
Kohn Spec with DCAE Impact
| REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
| YES | PMSH functional enhancement and support for dynamic filter/subscription change via API Commitment from Ericsson | |
| NA | YES | VES 7.2.1 support for DCAE Microservices (outside of collectors) - TCAgen2 Commitment from Wipro | |
| NA | YES | DMAAP SDK standardization for DCAE Microservices
Commitment from Huawei for SliceAnalysis mS, KPI-ms and SON-handler - In discussion with Wipro | |
| NA | Stretch-goal | AAF certificate dependency to be removed by making it a configurable property for MS
Stretch goals: Nokia for DCAEGEN2-3039 (DFC), Huawei for DCAEGEN2-3095 (RESTConf) | |
| NA | YES | Sonarcoverage improvements for DCAE components
Commitment from AT&T, Wipro, HUAWEI, ChinaTelecom, Nokia | |
| NA | YES | Automated review tool integration with CI/verify Commitment from AT&T |
Kohn POC (DCAE impact)
| REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
...
| 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 | |
REQ-439 - CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES Global-REQ | TBC | <Pending SECCOM analysis/report> Commitment TBD | TBA |
REQ-437 - COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8) Global-REQ | YES | (No new impact for DCAE in K release) | NA |
REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) Global-REQ | No |
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 J release) | OOM-2749 |
REQ-441/REQ-1070 - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA - JAKARTA 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 J 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 |
...
- 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
DCAE MOD was introduced in Frankfurt release to address following requirements:
- Simplified and streamlined onboarding for DCAE components/microservice and distribute the deployment artifact with DCAE-Core Platform (Cloudify)
- Provide Common Catalog for reusable DCAE microservices for Designer to leverage
- 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.
Platform Maturity
Platform Maturity (i.e., S3P items) Kohn Release Platform Maturity
...
- Genprocessor
- MOD/NiFI UI
- Distributorapi
- Runtimeapi
- Onboardingapi
* - Will be assessed at M3 depending on Helm migration feature statusNote: 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.
...
Jira server ONAP Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=dcaegen2 and issuetype in (epic) and fixversion='Jakarta Kohn Release' serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Jira server ONAP Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=dcaegen2 and issuetype in (story) and fixversion = 'Jakarta Kohn Release' serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Longer term roadmap
Complete DCAE transformation initatives and backlog items.
...
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*
- DCAE: Chart migration from OOM repo to DCAE & ONAP CI/CD integration for helm chart builds
- Assess DCAEMOD platform continued support/retirement
- Prometheus Integration
- TICK/ELK IntegrationDCAE MOD support for Java11 compatibility
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
...