Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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

 

Note: Features highlighted in RED need further discussion with owners; not committed yet

Non-Functional Requirement 

  • 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 (Policy libraryDCAEGEN2-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 
  • 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)
  • 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-service30415
      dashboard30418


Platform Maturity

 Platform Maturity (i.e., S3P items)  Frankfurt Release Platform Maturity

...

It is not expected to have a detailed project plan.

DateSprint
Project
#No of days
DeliverableTo fill outTo fill outTo fill out
 Deliverable

  -  

DCAE Frankfurt Sprint 114
  • Seed code for new components
  • jjb definition for verify/merge/sonar/clm

  -  

DCAE Frankfurt Sprint 215 
  • Atleast 80% of Functional delivery
  • Atleast 30% of release/compliance (coverage & security)
  • Successful container build (new components)

  -  

DCAE Frankfurt Sprint 315
  • 95% of Functional delivery
  • Atleast 70% of release/compliance (coverage & security)
  • API definition formalized
  • Integration test plan completed

  -  

DCAE Frankfurt Sprint 4 15

M2/M3 checkpoint

  • API definition formalized and shared with impacted teams
  • 100% Functionality
  • Documentation repo updates (API updates & new MS/component) - Frankfurt Documentation
  • Deployment artifacts (helm for platform component; spec file and/or blueprint for service component)  & onap integration


 -  

DCAE Frankfurt Sprint 515 M4 - 03/12

  -  

DCAE Frankfurt Sprint 6 (RC prep) 15RC0
  • 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

...