/
DCAE R10 Jakarta M2 Release Planning

DCAE R10 Jakarta M2 Release Planning

Jan 30, 2022

 

Overview

Project Name

Enter the name of the project

Project Name

Enter the name of the project

Target Release Name

Jakarta

Project Lifecycle State

Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information

Participating Company 

AT&T, Nokia, Ericsson, Wipro, Samsung, Huawei, DT

Scope

What is this release trying to address?

Release Focus

DCAE Focus for R10 is on following

  • Complete DCAE transformation to Helm

    • Common Template 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

  • Support TSC approved ONAP Usecases and Features (details below)

  • 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 

 

Jakarta Usecases with DCAE impact

REQ#

DCAE Commit Status

DCAE Impact Assessment

DCAE JIRA #

REQ-1085 - E2E Network Slicing use case enhancements for Jakarta release

YES

1. Slice selection taking into consideration resource occupancy levels (NSI/NSSI Selection based on resource occupancy levels - DCAE changes)
2. IBN based Closed loop for Network Slicing

Commitment from WIPRO  

DCAEGEN2-3021

REQ-1042 - 5G SON use case enhancements for Jakarta release

NO

No new impact for DCAE in J release

  1. Development of PM/FM/CM VES message formats which are aligned with O-RAN O1

  2. Modifications of SON-Handler MS to work with updated PM/FM message formats

DCAEGEN2-2986

Jakarta Features with DCAE Impact

REQ#

DCAE Commit Status

DCAE Impact Assessment

DCAE JIRA #

REQ-1076 - CCVPN Jakarta Enhancements for Intent-based Cloud Leased Line and Closed-loop

YES

Slice Analysis enhancement

  1. Support bandwidth evaluation and CL event generation

  2. AAI Interface for bandwidth update notification

Commitment from HUAWEI for Development; Wipro team support reviews

DCAEGEN2-3063

REQ-1074 - Smart Intent Guarantee based on Closed-loop in R10

YES

Same as REQ-1076 

+

Introduction of ML/MS mS (POC)

Commitment from Wipro

DCAEGEN2-3063+ 

DCAEGEN2-3067 (POC)

REQ-1038 - DCAE Transformation to support Helm (Phase3/final)

YES

Cloudify/platform-handlers deprecation; MOD helm integration

Commitment from AT&T, Nokia, Ericsson, Wipro, Huawei, 

DCAEGEN2-2773

Jakarta Spec with DCAE Impact

REQ#

DCAE Commit Status

DCAE Impact Assessment

DCAE JIRA #

 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

NA

No

CMPv2 Enhancement - support for VES/DFC/HV-VES cert dynamically

DCAEGEN2-2886

NA

Deferred

VES 7.2.1 support for DCAE Microservices (outside of collectors)

DCAEGEN2-2975

NA

Deferred

DMAAP SDK standardization for DCAE Microservices

DCAEGEN2-3030

NA

Stretch-goal

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)

Commitment from Nokia, Wipro

DCAEGEN2-3031

NA

Stretch-goal

AAF certificate dependency to be removed by making it a configurable property for MS

Commitment from Nokia

DCAEGEN2-3037

Jakarta POC (DCAE impact)

REQ#

DCAE Commit Status

DCAE Impact Assessment

DCAE JIRA #

NA

YES

Trial use of the black formatting and pylint checking tools on python code

Commitment from AT&T 

DCAEGEN2-2994

 

 

 

 

Best Practices/GLOBAL Requirements

REQ#

DCAE Commit Status

DCAE Impact Assesment

DCAE JIRA #

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

Global-REQ 

YES

CII badging score improvement

Commitment from AT&T 

DCAEGEN2-2829

REQ-439 - CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES

Global-REQ

YES

Tcagen2, DFC, RESTConf, MOD-runtimeAPI, Mapper, PM-Mapper, PRH, SON-Handler, KPI-Computation MS, Slice-Analysis MS

Commitment from AT&T, Nokia, Wipro

DCAEGEN2-3006

REQ-437 - COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8)

Global-REQ

YES

 

(No new impact for DCAE in J release)

DCAEGEN2-3020

REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11)

Global-REQ

No

  • dcaemod-designtool

  • dcaemod-nifi-registry

Exception will be filed with SECCOM for waivers due to upstream (NIFi) dependency

DCAEGEN2-3019

REQ-432 - IPv4/IPv6 dual stack support in ONAP

YES

Enhance ONAP common-service template - add IPv4/IPv6 support

(No new impact for DCAE in J release)

OOM-2749 

REQ-441/REQ-1070 - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA - JAKARTA RELEASE

Global-REQ

YES

Healthcheck and SNMPTRap container

 

Commitment from AT&T 

DCAEGEN2-2958

REQ-1073 - Using basic image from Integration  

YES

VESCollector, RESTConf, Slice-Analysis MS need to be switched to use integration base image

 

Commitment from Nokia, Huawei, Wipro, AT&T

REQ-1072 - Standardized logging fields

Stretch-goal

No change planned for existing Ms, however will be handled for new ML/MS POC delivery; 

Commitment from Wipro

Tracked under DCAEGEN2-3067

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

New Services introduced for this release 

Following new services will be delivered as POC in R10

 

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)

 

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

 

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

     * - Will be assessed at M3 depending on Helm migration feature status.

 

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

key summary type created updated due assignee reporter priority status resolution
Refresh

Stories

key summary type created updated due assignee reporter priority status resolution
Refresh

Longer term roadmap

 

Complete DCAE transformation initatives and backlog items.

Release Deliverables

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

Deliverable Name

Deliverable Description

Deliverable Name

Deliverable Description

Component spec

All ms added into DCAE should provide meta data representation of the component itself; will be used to generate

design flow under MOD and enable blueprint generation 

configbinding

SourceCode/Docker image

policy side-car

SourceCode/Docker image

dcae-healthcheck

SourceCode/Docker image

dcae-mod

SourceCode/jar/Docker image/Documentation

VES Collector

SourceCode/Docker image/helm charts

HV_VES Collector

SourceCode/jar/Docker image/helm charts

PRH

SourceCode/jar/Docker image/helm charts

TCA-GEN2

SourceCode/jar/Docker image/helm charts

DFC

SourceCode/Docker image/helm charts

RESTConf

SourceCode/Docker image/helm charts

PM-MAPPER

SourceCode/Docker image/helm charts

VES-MAPPER

SourceCode/Docker image/helm charts

DL Components (DES,

DL-ADMIN, DL-FEEDER)

SourceCode/Docker image/helm charts

SLICE ANALYSIS

SourceCode/Docker image/helm charts

KPI-MS

SourceCode/Docker image/helm charts

HEARTBEAT MS

SourceCode/Docker image/helm charts

SON-HANDLER MS

SourceCode/Docker image/helm charts

PMSH

SourceCode/Docker image/helm charts

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:

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 .

 

 

 

 DCAE Interfaces

Platform Maturity

 

Jakarta Release Platform Maturity

 

Refering to 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.

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

Performance

1

1

 

  •  

    • 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

2

 

 

 

  •  

    • Level 0: none beyond release requirements

    • Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load)