...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | KohnLondon |
| 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 |
...
- 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
...
London 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) 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 | YES | DCAE SDK alignment for SliceAnalysis MS & enhanching AAI interface for supporting IBN CL Commitment from HUAWEI/ChinaTelecom |
...
London Features with DCAE Impact
| REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
| YES | Slice Analysis enhancement
Commitment from HUAWEI/ChinaTelecom | ||
| 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 |
|
...
London 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 |
...
London POC (DCAE impact)
| REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
| NA |
...
Note: The above commitment should be consistent with Kohn London Impact View per Component at M2.
...
Platform Maturity (i.e., S3P items) Kohn London Release Platform Maturity
...
Note: DCAE-MOD is possible candidate for retirement with Kohn London 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.
...
DCAE Interfaces
Platform Maturity
Kohn London Release Platform Maturity
...
The milestones are defined at the Release Planning: KohnLondon and all the supporting project agreed to comply with these dates.
...
| Date to be completed by | Sprint | #No of days | Deliverable |
|---|---|---|---|
| Key dates for KOHN London release - Release Planning: KohnLondon | |||
| M2 | DCAE Kohn London Sprint 1 (Planning) |
| |
| M2-M3 | DCAE Kohn London Sprint 2 (Development) |
| |
| M3 | DCAE Kohn London Sprint 3 (Code Freeze) |
| |
| M4 | DCAE Kohn London Sprint 4 (Container Release/artifact) | Finalize containers/jars for release and submit patch to OOM for revisions | |
| RC | Integration/Sign-Off |
| |
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
Other Information
...