Overview

Scope

What is this release trying to address?

Release Focus

DCAE Focus for R11 is on following

• Address DCAE transformation carry-over items
  • Common Template Enhancement for dcaegen2-services-common (For support for dynamic configuration update via ConfigMap)
  • DR Feed configuration cleanup
  • Bug fixes for MOD/Helm-gen (log.path setting override)
• Support TSC approved ONAP Usecases and Features (details below)
• Alignment with TSC/SECCOM Global requirements & TSC/SECCOM Best Practice
• OpenSSF Best Practice progression (target Gold badging)
• SBOM Report integration with CI and validation*
• Continue AAF certificate dependency removal (by making it a configurable property)
• Microservice enhancements in support for ONAP usecases/features 
  • SliceAnalysis Ms (under E2E Slicing/IBN/CCVPN), SON-Handler (5G SON)
• Enable automated static-check code review/scan with CI/verify job 
• Improving code coverage across all DCAE components
• DCAE backlog reduction

Kohn Usecases with DCAE impact

Kohn Features with DCAE Impact

Kohn Spec with DCAE Impact

Kohn POC (DCAE impact)

Best Practices/GLOBAL Requirements

Note: The above commitment should be consistent with Kohn Impact View per Component at M2.

New Services/Components

Following new services will be delivered under E2E Slicing usecase for IBN based closed Loop support.

• ML MS (REQ-1215)
  • Repository : https://git.onap.org/dcaegen2/services/tree/components/ml-prediction-ms (introduced as new subproject under existing repo)

Retirement/Deprecation

• Acumos Adapter

      DCAE MOD under assessment for EOL with London release

DCAE MOD was introduced in Frankfurt release to address following requirements:

1. 1. Simplified and streamlined onboarding for DCAE components/microservice and distribute the deployment artifact with DCAE-Core Platform (Cloudify)
   2. Provide Common Catalog for reusable DCAE microservices for Designer to leverage
   3. Enable automated onboarding for ML microservices from Acumos. 

With DCAE platform transformation feature, requirement #1 and #2 are less critical as the onboarding/deployment are easily managed through Helm-Charts and catalog supported through Chartmuseum (or any other registry)/With Also with Acumos project archived under LF (end of 2021), DCAE team will be assessing the need for continuation/support of DCAE MOD going forward.  

Note: Certain MOD components are on java8 due to upstream dependency with Apache/Nifi project on java8 and have SECCOM exception currently.

Platform Maturity

 Platform Maturity (i.e., S3P items)  Kohn 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

As DCAE transformation is underway, two different deployment options will be available. The MVP of DCAE will vary based on deployment choice and will include the necessary subcomponents supporting the primary objectives: meeting platform maturity goals and supporting the use cases.

Helm Deployment (dcaegen2-services)

• •   VESCollector
  •   TCA-gen2
  •   PRH
  •   HV_VES

      DCAE-MOD deployment is optional and will include following component (controlled via helm chart configuration under OOM)

• • Genprocessor
  • MOD/NiFI UI
  • Distributorapi
  • Runtimeapi
  • Onboardingapi

      Note: DCAE-MOD is possible candidate for retirement with Kohn release.

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

With DCAE Helm transformation initiate completed, achieved the major goal on platform simplification. As ONAP progresses for supporting new usecase, will assess them for support.

Following are some initiatives under consideration

• • Policy/CLAMP: Continue integration for Control Loop design for Helm-based deployment of DCAE Services*
  • Assess DCAEMOD platform continued support/retirement
  • Prometheus Integration
  • TICK/ELK Integration

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Note: Only default platform components and bootstrapped MS is listed on table above. DCAE also include dynamic service components deployed based on usecases. For a complete set of available DCAE MS - refer https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/release-notes.html#deliverables

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 Resources and Repositories (Deprecated) in the centralized page.

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/CLAMP - Policy - For managing application configuration policy. 
  • 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 Amsterdam architecture diagram_1.0.0.pptx.

 DCAE Interfaces

Platform Maturity

Kohn Release Platform Maturity

Refering to 2017-06-28 CII badging for ONAP.pptx and Platform Maturity Requirements (aka Carrier Grade), 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; all components are required to maintain 55% codecoverage at the minumum. 
      • https://sonarcloud.io/organizations/onap/projects?search=dcaegen2
    • Functional test plan
      • DCAE R11 Kohn Testplan
    • CSIT tests will continue to be supported for existing components and new components
      • DCAE has number of CSIT - https://jenkins.onap.org/view/CSIT/; these will be continued to be validated during course of development for this release.
    • Pairwise testing will be done in the WindRiver Dev lab; below wiki page captures the test planned
      • DCAE R11 Kohn Pairwise Test
    • DCAE also has number of Smoke test (Example - https://logs.onap.org/onap-integration/daily/onap_daily_pod4_master/01-18-2021_08-01/) enabled for several components/flows; these test are validated part of gating for new container releases
      • Bulk-PM
      • HV-VES
      • VES
      • PRH flow
      • MOD

• 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

Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:dcae

• Release Milestone

The milestones are defined at the Release Planning: Kohn 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

           Kohn Documentation

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 TSC Charter OBSOLETE 7 1 CLEAN.pdf.