...

Scope

What is this release trying to address?

Release Focus

DCAE Focus for R9 R10 is on following

...

• Complete DCAE

...

• transformation

...

• to Helm
  • Common Template

...

• CMPv2 Certificate
• Policy Sidecar
• PG credentials management through K8S secret
• ConfigMap Support
• DMaap Config Support (dynamic)

...

• Bulk PM flow - DataFile, PM-Mapper, PMSH
• E2E Slicing - KPI-MS, Slice-Analysis, DL Handlers (Feeder, Admin, DES)
• Son-Handler, Heartbeat, VES-Mapper, RESTCOnf, SNMPTrap, BBS-Ep

...

• Helm charts generation through MOD  (POC)
• ONAP Internal Helm Registry support

• • Enhancement for dcaegen2-services-common (filebeat removal + general add-on capabilities)
  • Continue removal of Consul dependency & application config standardization via configmap
  • MOD Support for Helm chart generation/distribution
  • Deprecate Cloudify and related Handlers from ONAP deployment
  • Integration Testsuite migration to use helm chart
• TSC/SECCOM Global requirements 
  • STDIO complaince for Heartbeat and SNMPTRap MS
• TSC/SECCOM Best Practice
  • Integration base image alignment for VES/RESTConf/SliceAnalysis MS
• Reducing DCAE backlogs  & security fixes
• Microservice enhancements in support for ONAP usecases/features 

• TSC/SECCOM Global requirements
• Reducing DCAE backlogs  + security fixes

Jakarta Usecases with DCAE impact

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
Image AddedREQ-

721

1085 - E2E Network Slicing use case enhancements for Jakarta release

YESEnhancements in KPI MS

TBC

Enhancements in Slice Analysis MS (CPS integration)

1. Slice selection taking into consideration resource occupancy levels 2. IBN based Closed loop for Network Slicing Commitment from WIPRO   , China

Mobile 

Mobile

DCAEGEN2-

2771

3021

Image AddedREQ-

720

1042 - 5G SON use case enhancements for Jakarta release

YES

SON-Handler Enhancements (CPS integration and VES alignment)

TBC

Development of PM/FM/CM VES message formats which are aligned with O-RAN O1 Modifications of SON-Handler MS to work with updated PM/FM message formats Commitment from WIPRO

DCAEGEN2-

2522

2986
Image AddedREQ-1076 - CCVPN Jakarta Enhancements for Intent-based Cloud Leased Line and Closed-loop	TBC

Jakarta Features with DCAE Impact

Jakarta Spec with DCAE Impact

Jakarta POC (DCAE impact)

...

• Migrate all remaining DCAE services to helm
• DCAE svc template extension to support generic functions
• Archiving Cloudify workflow related handlers

Commitment from AT&T, Nokia, Ericsson, Wipro, Independent, Orange/Samsung (OOM)

...

DCAEGEN2-2630

Smart Intent Guarantee based on Closed-loop in R10	TBC	DCAE impacts requires clarification
Image AddedREQ-1038 - DCAE Transformation to support Helm (Phase3/final)	YES	Cloudify/platform-handlers deprecation; MOD helm integration	DCAEGEN2-2773

Jakarta Spec with DCAE Impact

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
Image Added REQ-935 Bulk PM / PM Data Control Improvements	YES	PMSH functional enhancement and support for dynamic filter/subscription change via API Commitment from Ericsson	DCAEGEN2-2908 DCAEGEN2-2906
	TBC	CMPv2 Enhancement - support for VES/DFC/HV-VES cert dynamically	DCAEGEN2-2886
	TBC	VES 7.2.1 support for DCAE Microservices (outside of collectors)	DCAEGEN2-2975
	TBC	DMAAP SDK standardization for DCAE Microservices
	TBC	Migrate DCAE MS to use standard topics (i.e unauthenticated) - PM-Mapper, Slice-Analysis, KPI-MS This will aid in Dmaap/Strimzi migration/Servicemesh complaincy and addressing Multiple subscriber issue (DCAEGEN2-2937)
	TBC	ServiceMesh Compatibility - Switch components deployment default to HTTP

Jakarta POC (DCAE impact)

...

REQ#

DCAE Commit Status

DCAE Impact

Assesment

Assessment

DCAE JIRA #

REQ-443 - CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL

YES

Sonar security fixes (RESTConf)

CII badging score improvement

DCAEGEN2-2829

Trial use of the black formatting and pylint checking tools on python code Commitment from AT&T	DCAEGEN2-2994
	TBC	AAF certificate dependency to be removed by making it a configurable property for MS

Best Practices/GLOBAL Requirements

Note: The above commitment is consistent with Jakarta Impact View per Component (as of 06/09/2021) 

Platform Maturity

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

...

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

Platform Maturity

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

• 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

      Helm/Cloudify Deployment (dcaegen2)

• •   Cloudify Manager
  •   Consul (deployed/managed by OOM)
  •   DeploymentHander
  •   Policy-Handler
  •   ServiceChangeHandler
  •   Inventory-API
  •   Postgres
  •   ConfigBinding Service
  •   Dashboard

DCAE Service specific components

• •   VESCollector
  •   TCA-gen2
  •   PRH
  •   HV_VES

      Following platform component will be continued to be deployed via helm until all DCAE MS are migrated to new Config management solution via SDK

• • ConfigBinding Service
  • Consul

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

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

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

Epics

Stories

...

Complete DCAE transformation initatives and backlog items.

...

• • DCAE/OOM: Remove consul dependency after all DCAE service are migrated to the latest SDK
  • Policy/CLAMP: Continue integration for Control Loop design for Helm-based deployment of DCAE Services*
  • DCAE: Chart migration from OOM repo to DCAE & ONAP CI/CD integration for helm chart builds
• Integration: Robot test suites migration to support helm services*
DCAE: Archive Cloudify and associated handlers/plugins and disable under ONAP deployment
• • DCAE MOD support for Java11 compatibility 

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

...

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. 
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 Amsterdam architecture diagram_1.0.0.pptx.

Image Added

 DCAE Interfaces

Image Added

...

Indicate where your project fit within the Amsterdam architecture diagram_1.0.0.pptx.

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.

Image Removed

Target Architecture (REQ-685)

...

Platform Maturity

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

...

...

...