...
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, IBM, TechM, Orange, ChinaMobile, Huawei |
Scope
What is this release trying to address?
...
- VES Collector (security)
- PRH (common sdk)
- SON-handler
- DFC (security)
Frankfurt Features with DCAE Impact
Note: Features highlighted in RED need further discussion with owners; not committed yet
Frankfurt Usecases with DCAE Impact
Non-Functional Requirement
- 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
- VESCollector EnhancementsVESCollector 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)- DCAEGEN2-1548 - Python 3.x upgrade 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)
- (transfer dependent on OOM team)
- 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%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%
Platform Maturity
Platform Maturity (i.e., S3P items) https://wiki.onap.org/display/DW/Dublin+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 2
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)
- 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
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=dcaegen2 and issuetype in (epic) and fixversion='Frankfurt Release' and status != 'Closed' serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Stories
- (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
config-binding-service 30415 dashboard 30418
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
Jira server ONAP JIRA columns key,summary,type, Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=dcaegen2 and issuetype in (storyepic) and fixversion='Frankfurt Release' and status != 'Closed' serverId 425b2b0a-557c-3c0c-b515-579789cceedb
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.
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=dcaegen2 and issuetype in (story) and fixversion = 'Frankfurt Release' serverId 425b2b0a-557c-3c0c-b515-579789cceedb
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 | |
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 |
...
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.
...
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 | heartbeat | dcaegen2/services/heartbeat | org.onap.dcaegen2.services.heartbeat | Missing Heartbeat Micro Services |
ONAP Dependencies
List the other ONAP projects you depend on.
...
- 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
...
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 |
Level 2
Level 2 - Dependent on integration team support
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
...
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
---|---|---|---|---|
VES IngestionCollector | 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 |
...
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 | Consul | CDAP | PNDA||
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
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 |
---|---|
To fill out | To fill out |
Known Defects and Issues
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 Provide a link toward the list of all known project bugs.
...
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 |
---|
Resources
Fill out the Resources Committed to the Release centralized page.
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.
...
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.
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
...