| Table of Contents |
|---|
...
| 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 |
...
| 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) Commitment from WIPRO | |||
| 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 | |||
| REQ-1268 - CCVPN Kohn Enhancements for Intent-based Cloud Leased Line and Transport Slicing | TBD | <DCAE impacts to be reviewed> | YES | DCAE SDK alignment for SliceAnalysis MS & enhanching AAI interface for supporting IBN CL Commitment from HUAWEI/ChinaTelecom |
Kohn Features with DCAE Impact
| REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
| YES | Slice Analysis enhancement
Commitment from HUAWEI/ChinaTelecom | ||
| TBDStretch-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 | |
| 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 (* stretch-goal) | Sub-Jira under EPIC DCAEGEN2-3089 |
| NA | YES | Automated review tool integration with CI/verify Commitment from AT&T | |
| NA | YES | Enhancements to KPI Computation MS
Commitment from Wipro | (sub-task to DCAEGEN2-2801) |
| REQ-358 | Stretch-Goal | No root (superuser) access to database from application container
Commitment from Wipro | |
| NA | YES | DMAAP SDK standardization for DCAE Microservices
Commitment from Huawei, Wipro | |
...
| 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 1211- CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES Global-REQ | TBC | <Pending SECCOM analysis/report> Commitment TBD | TBA | 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 K Kohn release) | NADCAEGEN2-3196 | |||
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 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 J 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 |
...
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.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.
| Info | ||
|---|---|---|
| ||
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+
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | 1 | 1 |
| |
| Stability | 2 | 2 |
| |
| Resiliency | 2 | 2 |
| |
| Security | 1 | 1+ |
| |
| Scalability | 1 | 1 |
| |
| Manageability | 1 | 1+ (Except logging, all other requirements are met) |
| |
| Usability | 1 | 1+ |
|
...
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) |
|---|---|---|---|---|
| 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 AvailableR11 | 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 AvailableR11 | R10 | No change for this release https://git.onap.org/dcaegen2/tree/docs/sections/apis/swagger_slice_analysis.json https://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/11774039616493831/slice-analysis-swagger.yaml?version=1&modificationDate=1640159785000&api=v2 |
Third Party Products Dependencies
...
| 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
...