/
DCAE R6 M1 Release Planning

DCAE R6 M1 Release Planning

Jan 09, 2020



Overview

Project Name

Enter the name of the project

Project Name

Enter the name of the project

Target Release Name

Frankfurt

Project Lifecycle State

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

Participating Company 

AT&T, Nokia, Ericsson, Wipro, IBM, TechM, Orange, ChinaMobile, Huawei

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 

  • 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



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

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

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.

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 

blueprints

Executable/SourceCode

plugins

SourceCode

cli

SourceCode/Tool/Documentation

deployment-handler

SourceCode/Docker image

servicechange-handler

SourceCode/Docker image

inventory-api

SourceCode/Docker image

policy-handler

SourceCode/Docker image

configbinding

SourceCode/Docker image

ves

SourceCode/Docker image

snmptrap

SourceCode/Docker image

tca

SourceCode/jar/Docker image

hv-ves-collector

        SourceCode/jar/Docker image

data-file-collector

        SourceCode/jar/Docker image

prh

        SourceCode/jar/Docker image

dcae-mod

       SourceCode/jar/Docker image/Documentation

pmsh

       SourceCode/jar/Docker image

tca-gen2

       SourceCode/jar/Docker image

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.



Deliverable

Repository

 Maven Group ID

Components Description

pmsh

dcaegen2/services

org.onap.dcaegen2.services.pmsh

PM Subscription Handler

tca-gen2

dcaegen2/analytics/tca-gen2  

org.onap.dcaegen2.analytics.tca-gen2

Standalone TCA









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.

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)

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

    • Level 3: track record over 6 months of reduced defect rate

Resiliency

2

2



  •  

    • 0 – none

    • 1 – manual failure and recovery (< 30 minutes)

    • 2 – automated detection and recovery (single site)

    • 3 – automated detection and recovery (geo redundancy)

Security

1

1+  (Most DCAE components are complaint; will address remaining in Frankfurt based on resource availability)





  •  

    • Level 0: None

    • Level 1: CII Passing badge

      • Including no critical and high known vulnerabilities > 60 days old

    • Level 2: CII Silver badge, plus:

      • All internal/external system communications shall be able to be encrypted.

      • All internal/external service calls shall have common role-based access control and authorization using CADI framework.

    • Level 3: CII Gold badge 

Scalability

1

1





  •  

    • Level 0: no ability to scale

    • Level 1: supports single site horizontal scale out and scale in, independent of other components

    • Level 2: supports geographic scaling, independent of other components

    • Level 3: support scaling (interoperability) across multiple ONAP instances

Manageability

1

1+  (Except logging, all other requirements are met)





  •  

    • Level 1:

    • All ONAP components will use a single logging system.

    • Instantiation of a simple ONAP system should be accomplished in <1 hour with a minimal footprint

    • Level 2:

      • A component can be independently upgraded without impacting operation interacting components

      • Component configuration to be externalized in a common fashion across ONAP projects

      • All application logging to adhere to ONAP Application Logging Specification v1.2

      • Implement guidelines for a minimal container footprint

    • Level 3

      • Transaction tracing across components

Usability

1

1+





  •  

    • Level 1:

      • User guide created