Overview
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, 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
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
Platform Maturity
Platform Maturity (i.e., S3P items) Frankfurt 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
The MVP of DCAE will include the necessary subcomponents supporting the primary objectives: meeting platform maturity goals and supporting the use cases.
- Cloudify Manager
- Consul (deployed/managed by OOM)
- DeploymentHander
- Policy-Handler
- ServiceChangeHandler
- Inventory-API
- Postgres
- ConfigBinding Service
- Dashboard
- DCAE-MOD
- genprocessor
- webui
- distributorapi
- runtimeapi
- onboardingapi
- blueprint-generator
DCAE Service specific components
- VESCollector
- TCA (Analytics application)/TCA-gen2
- PRH
- HV_VES
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
Stories
Longer term roadmap
DCAE is the collection and analytics platform serving ONAP. Improving upon the DCAE MS catalog to add new services for data collection, analytics and the number of open/close control loops.
Other long term goal includes below
- PNDA integration and facilitating application deployment via Helm.
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 |
blueprints | Executable/SourceCode |
plugins | SourceCode |
cli | SourceCode/Tool/Documentation |
deployment-handler | SourceCode/Docker image |
servicechange-handler | SourceCode/Docker image |
inventory-api | SourceCode/Docker image |
policy-handler | SourceCode/Docker image |
configbinding | SourceCode/Docker image |
ves | SourceCode/Docker image |
snmptrap | SourceCode/Docker image |
tca | SourceCode/jar/Docker image |
hv-ves-collector | SourceCode/jar/Docker image |
data-file-collector | SourceCode/jar/Docker image |
prh | SourceCode/jar/Docker image |
dcae-mod | SourceCode/jar/Docker image/Documentation |
pmsh | SourceCode/jar/Docker image |
tca-gen2 | SourceCode/jar/Docker image |
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 Resouce and Repositories in the centralized page.
In addition to existing platform/service component, following new components are targeted for Frankfurt.
Deliverable | Repository | Maven Group ID | Components Description |
pmsh | dcaegen2/services | org.onap.dcaegen2.services.pmsh | PM Subscription Handler |
tca-gen2 | dcaegen2/analytics/tca-gen2 | org.onap.dcaegen2.analytics.tca-gen2 | Standalone TCA |
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 - For managing application configuration policy
- CLAMP - For CL flow related MS instantiation and configuration
- 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 ONAP Archiecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, 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 | How, Evidences | Comments |
---|---|---|---|---|
Performance | 1 | 1 |
| |
Stability | 2 | 2 |
| |
Resiliency | 2 | 2 |
| |
Security | 1 | 1+ (Most DCAE components are complaint; will address remaining in Frankfurt based on resource availability) |
| |
Scalability | 1 | 1 |
| |
Manageability | 1 | 1+ (Except logging, all other requirements are met) |
| |
Usability | 1 | 1+ |
|
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) |
---|---|---|---|---|
SDC model distribution API | API for retrieving TOSCA model of close loop | Currently Available | To fill out | Link toward the detailed API description |
Policy Engine | API for retrieving configuration policy updates | 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 |
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 | R3 | |
DCAE Deployment Handler | NB API for invoking the deployment of DCAE subcomponents | Currently Available | R3 | |
DCAE Inventory | API for Add/Delete DCAE copy's TOSCA models | Currently Available | R3 | |
Healthcheck | API for querying DCAE component healthcheck | Currently Available | R4 | |
DCAE Onboarding API | API for publishing DCAE spec into MOD | Will be available around M3 | R6 | |
DCAE Inventory | API for CLAMP to retrieve flow information | Will be available around M3 | R6 |
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 |
Cloudify Manager | cloudifyplatform/community | 19.01.24 |
Consul | ||
CDAP | caskdata/cdap-standalone | 4.1.2 |
PNDA | 4.5 | |
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
- CSIT tests will continue to be supported for existing components
- Pairwise testing will be done in the WindRiver Dev lab similar to what was done in last release
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 |
---|---|
OTI Function delivery | OTI functionality is planned to be introduced in phase. For Frankfurt, seed code for OTI-Handler and EventPRoc will be delivered. The complete e2e functionality will be available in next release. There is no impact to Frankfurt usecase by this functionality. |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
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 |
---|---|---|
Cloudify support for Python 3.x not available during Frankfurt timeframe. This impacts migration of Cloudify and associated plugins in Frankfurt (DCAEGEN2-1546) | Continue El-Alto version of Cloudify and Plugins under python 2.7 | None |
Resources
Fill out the Resources Committed to the Release centralized page
Release Milestone
The milestones are defined at the Release Level 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 | Sprint | #No of days | Deliverable |
---|---|---|---|
- | DCAE Frankfurt Sprint 1 | 14 |
|
- | DCAE Frankfurt Sprint 2 | 15 |
|
- | DCAE Frankfurt Sprint 3 | 15 |
M2/M3 checkpoint - 1/21 |
- | DCAE Frankfurt Sprint 4 | 15 |
|
- | DCAE Frankfurt Sprint 5 | 15 | M4
|
- | DCAE Frankfurt Sprint 6 (RC prep) | 15 | RC0
|
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
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 Charter.