...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Frankfurt |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Nokia, Ericsson, Wipro, ChinaMobile, Fujitsu?T-Mobile, Huawei? |
Scope
What is this release trying to address?
...
Release Focus
DCAE Focus for R7 is on following
- ONAP R7 Usecase & Functional requirement
- TSC/SECCOM MUST-HAVE requirements
- General platform optimization
- DCAE Bootstrap/CM Manager optimization (moving plugins to CM)
...
- MOD catalog/UI redesign (POC)
...
- Addressing DCAE back logs + security fixes
Following new services is targeted for R6 additions.
SDK Enhancement
- Dmaap pub/sub
- Configbindingservice
Enhancement to existing DCAE components
- VES Collector (security)
- PRH (common sdk)
- SON-handler
- DFC (security)
Guilin Features with DCAE Impact
- Self-Serve Control Loops
- Policy Update Notifications
- 5G / OOF SON Enhancement
- 5G / Run-time Data Persistency
- Modeling: 5G / ORAN & 3GPP Standards Harmonization
- 5G / Bulk PM / PM Control
- 5G / Bulk PM / Secure Communication between xNFs and ONAP
- 5G / PM dictionary
- PNF / Plug and Play
Non-Functional Requirement
Guilin Usecases with DCAE impact
| REQ# | Description | DCAE Impact Assessment | DCAE JIRA # |
| REQ-345 | 5G OOF SON use case requirements for Guilin release | SON-Handler enhancement | DCAEGEN2-2312 |
| REQ-342 | E2E Network Slicing requirements for Guilin release | New MS introduction - DES (under DL-Handlers), Slice Analysis MS, PM-Mapper Enhancements | DCAEGEN2-1878 |
| REQ-325 | MDONS Extension in Guilin Release | 7/2 - Using VES Flow (DCAE impact is TO) | NA |
Following new services will be delivered in R7 to support REQ-342
Slice Analysis MS
Repository : https://git.onap.org/dcaegen2/services/tree/components/slice-analysis-ms
Data Extraction Service (DES)
Repository : https://git.onap.org/dcaegen2/services/tree/components/datalake-handler/des
Guilin Features with DCAE Impact
Functional Requirements
| REQ# | Description | DCAE Impact Assessment | DCAE JIRA # |
| REQ-381 | Bulk PM / PM Data Control Extension | PMSH and PM-Mapper enhancements | DCAEGEN2-2164 |
| REQ-327 | ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES | VESCollector + platform/deployment support via config-map | DCAEGEN2-1769 |
| REQ-326 | Self Serve Control Loops | MOD updates - Nifi backlog reduction - New MOD UI/catalog (POC) | DCAEGEN2-1993 DCAEGEN2-2314 (MOD-POC) |
| REQ-321 | CMPv2 Enhancements for R7 | DCAE Platform (k8splugin, CM/Bootstrap) Component_spec + Bp-gen MOD component OOM revision | DCAEGEN2-2250 |
| REQ-385 | IPv4/IPv6 dual stack support in ONAP | K8splugin change to support k8s 1.17+ | DCAEGEN2-2309 |
Non-Functional Requirement
| REQ# | Description | TSC Priority | DCAE Commit Status | DCAE Impact Assesment | DCAE JIRA # |
| REQ-380 | ONAP container repository (nexus) must not contain upstream docker images | MUST HAVE | YES | Add explicit references to dockerhub or nexus to all images | DCAEGEN2-2322 |
| REQ-379 | ONAP projects must use only approved and verified base images for their containers | MUST HAVE | Stretch-goal | HIGH RISK - LIST NOT CONFIRMED + MULTIPLE DCAE COMPONENT IMPACT https://wiki.onap.org/display/DW/Database%2C+Java%2C+Python%2C+Docker%2C+Kubernetes%2C+and+Image+Versions 1) Approved base image for NodeJS TBC 2) Policy-handler base image (python:3.6) + python:3.7-alpine 3) Cloudify base image (Community) support only 3.6 4) Bootstrap (centOS) + cloudify cli may not be compatiable alpine (python image is possible) 5) MOD components 6) NiFi - apache/nifi-registry:0.5.0 | DCAEGEN2-2323 |
| REQ-374 | ONAP shall use STDOUT for logs collection | PTL | Strech-goal | Multiple platform components impacts (CBS, DH, PH, Cloudify not complain). May need a generic way to map filebeat container o/p into std out. (Long- Stretch goal) - Depending on OOM team support | DCAEGEN2-2324 |
| REQ-373 | ONAP must complete update of the Python language (from 2.7 -> 3.8) | MUST HAVE | YES | Per TSC 2.7->3.8 important; 3.7-3.8 (nice to have)
| DCAEGEN2-2292 |
| REQ-366 | Containers must crash properly when a failure occurs | MUST HAVE | YES | MEDIUM RISK - Need further assessment on DCAE components impacted (Ericsson) | DCAEGEN2-2326 |
| REQ-365 | Containers must have no more than one main process | MUST HAVE | YES | MEDIUM RISK - Need further assessment on DCAE components impacted (Ericsson) Exception required for Cloudify due to upstream dependency. | DCAEGEN2-2327 |
| REQ-364 | Replace NodePorts with ingress controller as a default deployment option | PTL | Strech-goal | Need to be create DCAE jira if OOM team support is confirmed (may just need to update your tests to use urls instead of IPs) | NA |
| REQ-361 | Continue hardcoded passwords removal | MUST HAVE | YES | 1) Evaluate certInitializer integration impact for DCAE-tls init container | DCAEGEN2-1972 |
| REQ-360 | Application config should be fully prepared before starting the application container | PTL | NO | Okay for service components (as CBS is used); Platform component should be okay. MOD - to be verified (possibly MOD/Nifi container) + Dashboard Commitment based on impacted list and OOM team support | NOT Committed |
| REQ-358 | No root (superuser) access to database from application container | YES | Strech-goal | Need further assesment. Current list of component impact - Dashboard/Inventory/TCA-gen2/heartbeat/PM-Mapper/DL-feed/Son-handler - WIPRO | DCAEGEN2-2329 |
| REQ-351 | ONAP must complete update of the java language (from v8 -> v11) | MUST HAVE | YES | MEDIUM RISK : Due to number of DCAE components impacted. Some MOD components will need exception (due to NiFI upstream dependency) | DCAEGEN2-2223 |
| REQ-350 | Each ONAP project shall improve its CII Badging score by improving input validation and documenting it in their CII Badging site. | PTL | Strech-goal | DCAEGEN2-2332 | |
| REQ-349 | Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage | MUST HAVE | YES | Already complaint for Frankfurt components; new component/enhancement to adhere | DCAEGEN2-2333 |
| REQ-323 | Each project will update the vulnerable direct dependencies in their code base | MUST HAVE | YES | DCAEGEN2-2242 |
DCAE Backlog Reduction
- VESCollector Enhancements
- DCAEGEN2-1483 – Event publish order issue (stretch goal)
- DCAEGEN2-1484 - Set dynamic partitionkey
- DCAEGEN2-608 - Performance/benchmarking
- Deployment optimization
- (Plugin load, reduce bootstrap,
Cloudify upgrade)
- (Plugin load, reduce bootstrap,
- DCAE Dashboard Fixes and security updates
- DCAE Helm chart org (OOM-1574)
- DL Handlers Enhacements DCAEGEN2-1849
- VESCollector Enhancements
- DCAEGEN2-1594 – VESCollector healthcheck support when authentication is enabled; Validation blocked by DCAEGEN2-1757 – spring version issue
- DCAEGEN2-1483 – Event publish order issue
- DCAEGEN2-1484 - Set dynamic partitionkey (stretch goal)
- DCAEGEN2-1774 - Optimize VES schema load by retain in-memory than loading file each time (dint find corresponding jira, created new today)
- DCAEGEN2-608 - Performance/benchmarking
- DCAEGEN2-1776 - Remove certOnly and basicAuth from authentication methods
- DCAEGEN2-1779 - Switch VES collector's K8s health checks to HTTPS
- TCA-gen2 delivery and replace TCA/cdap (DCAEGEN2-1907)
- Mongodb support for tca-gen2
- Deployment optimization (Plugin load, reduce bootstrap,
Cloudify upgrade) Python 3.x Plugin upgrade (5.0.5 - Cloudify mock available; 5.1 – full python 3.x)- Python 3.x support (DCAEGEN2-1519)
- DCAEGEN2-1548 - Python 3.x upgrade for Policy Lib
- DCAE Dashboard Fixes and security updates
- Automated test improvement (csit/robot)
- DCAE Helm chart org (OOM-1574)
- Multi-site registry alignment (DCAEGEN2-1879) - (stretch goal)
- DCAE TLS init container improvement
- DCAEGEN2-917 - Dynamic cert generation through AAF
- REQ-136 - CMP-v2 cert generation support
- OTI Phase1 (contribute new platform component) (DCAEGEN2-1908)
- OTI Integration impacts following components (k8splugin, stateful set support, OTI-handler, OTI-EventProc, CBS*, kube2pyconsul, PG*, Nginxproxy, bp-gen). For Frankfurt, OTI-Handler and OTI-Event proc component seed code will be delivered and integrated with ONAP CI process. The full platform integration will be deferred to Guilin release.
- DL Handlers integration DCAEGEN2-1849
- MOD Integration DCAEGEN2-1852
- Sonar coverage improvement (60% target for Frankfurt) (stretch goal)
- dcaegen2-analytics-tca-gen2 – 56% (DCAEGEN2-1900)
- dcaegen2-collectors-snmptrap – 56% (DCAEGEN2-1903)
- dcaegen2-platform-inventory-api – 58% (DCAEGEN2-1906)
- dcaegen2-platform-plugins – 56% (DCAEGEN2-1904)
- dcaegen2-services-heartbeat – 57% (DCAEGEN2-1902)
- dcaegen2-services-son-handler – 55% (DCAEGEN2-1905)
- ccsdk-dashboard – 42.5% (DCAEGEN2-1901)
- Outstanding OJSI Jira (OJSI Tickets Status)
- Java 11 Upgrade (DCAEGEN2-1918) (stretch goal)
- Following additional TSC MUST have requirement will be handled in this release.
- Document current upgrade component strategy
- SECCOM Perform Software Composition Analysis - Vulnerability tables
- SECCOM Password removal from OOM HELM charts
- No DCAE impacts identified; will handle new charts contribution for MOD to align with Security needs.
SECCOM HTTPS communication vs. HTTP
Platform Maturity
Platform Maturity (i.e., S3P items) Frankfurt Release Platform Maturity
...