...
| 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, TechMNokia, Ericsson, Wipro |
Scope
What is this release trying to address?
...
Note: Features highlighted in RED need further discussion with owners; not committed yet
Frankfurt Usecases with DCAE Impact
Image Added
Non-Functional Requirement
Platform Maturity
...
- 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
- 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
- Mongodb support for tca-gen2
- Deployment optimization (Plugin load, reduce bootstrap, Cloudify version syncup)
- Python 3.x (5.0.5 - Cloudify mock available; 5.1 – full python 3.x)
- Automated test improvement (csit/robot)
- DCAE Helm chart org (and transfer dependent on OOM team)
- Multi-site registry alignment
- DCAE TLS init container improvement
- Dynamic cert generation through AAF
- CMP-v2 cert generation support
- OTI
- Platform (k8splugin, stateful set support, DTI-handler, CBS*, kube2pyconsul, PG*, Nginxproxy, bp-gen)
- MS (SNMPPoller)
- DL Handlers integration
- MOD Integration
- Sonar coverage improvement (60% target for Frankfurt)
Platform Maturity
Platform Maturity (i.e., S3P items) https://wiki.onap.org/display/DW/Dublin+Release+Platform+Maturity
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|
| Performance | 1 | 1+ (Dublin recommendation 2 - cannot be committed due to Resource constraint) |
| - Level 0: no performance testing done
- Level 1: baseline performance criteria identified and measured (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component)
- Level 2: performance improvement plan created
- Level 3: performance improvement plan implemented for 1 release (improvement measured for equivalent functionality & equivalent hardware)
|
| Stability | 2 | Level 2 (Stetch with new ~52% coverage requirement for Dublin) Level 2 - Dependent on integration team support
|
| - Level 0: none beyond release requirements
- Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load)
- Level 2: 72 hour platform-level soak test (random test transactions with 80% code coverage; steady load)
- Level 3: track record over 6 months of reduced defect rate
|
| Resiliency2 | 20 – none1 – manual failure and recovery (< 30 minutes)2 – automated detection and recovery (single site)3 – automated detection and recovery (geo redundancy) | Security | 1 | 1+ (Dublin recommendation 2 - cannot be committed for following reason)
Resource constraintCADI library not available for Python Process of AAF certificate distribution in K8S between ONAP components and external (xNF) to be defined
DCAE team will integrate with Buscontroller integration for dynamic topic provisioning and AAF based role setting as STRETCH GOAL |
| - 0 – none
- 1 – manual failure and recovery (< 30 minutes)
- 2 – automated detection and recovery (single site)
- 3 – automated detection and recovery (geo redundancy)
|
| Security | 1 | 1+ |
| - Level 0: None
- Level 1: CII Passing badge
- Including no critical and high known vulnerabilities > 60 days old
- Level 2: CII Silver badge, plus:
- All internal/external system communications shall be able to be encrypted.
- All internal/external service calls shall have common role-based access control and authorization using CADI framework.
- Level 3: CII Gold badge
|
| Scalability | 1 | 1
|
| - Level 0: no ability to scale
- Level 1: supports single site horizontal scale out and scale in, independent of other components
- Level 2: supports geographic scaling, independent of other components
- Level 3: support scaling (interoperability) across multiple ONAP instances
|
| Manageability | 1 | 1+ (Dublin recommendation 2 - cannot be committed for following reason) |
| Resource constraint to support #2 and #4 under Level2
( 2 - #1 and #3 will be targeted for Dublin)- Level 1:
- All ONAP components will use a single logging system.
- Instantiation of a simple ONAP system should be accomplished in <1 hour with a minimal footprint
- Level 2:
- A component can be independently upgraded without impacting operation interacting components
- Component configuration to be externalized in a common fashion across ONAP projects
- All application logging to adhere to ONAP Application Logging Specification v1.2
- Implement guidelines for a minimal container footprint
- Level 3
- Transaction tracing across components
|
| Usability | 1 | 2 (STRETCH GOAL- based on resource availability)
|
| - Level 1:
- User guide created
- Deployment documentation
- API documentation
- Adherence to coding guidelines
- Level 2:
- Level 3
- Consistent UI across ONAP projects
- Usability testing conducted
- API Documentation
- Level 4
|
...
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project=dcaegen2 and issuetype in (bug) and fixversion='Casablanca Frankfurt Release' and status != 'Closed' |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
...