Overview

Scope

What is this release trying to address?

High Level Summary

• Addressing one of the long term goal to simplify the onboarding experience for MS in DCAE. Introducing new MicroService, Onboarding & Design (MOD) Platform in DCAE for Frankfurt, which will replace DCAE-DS currently under SDC
• Policy Integration : Enable update flow support via Dmaap
• Acumos-DCAE Adapter Integration (POC)
• Support ONAP usecases, functional requirement targeted for Frankfurt
• Addressing DCAE back logs (El-ALTO - Tracker) + security fixes

Following new services is targeted for R6 additions.

• PM-Subscription Handler
• TCA-gen2

SDK Enhancement

• Dmaap pub/sub
• Configbindingservice

Enhancement to existing DCAE components

• VES Collector (security)
• PRH (common sdk)
• SON-handler
• DFC (security)

Frankfurt 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 

• 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

    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

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.

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.

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.

• 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 Outgoing Dependencies

API this project is delivering to other projects.

• 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, ...).

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.

• 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).

• 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.

• 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.