DCAE R4 M1 Release Planning

DCAE R4 M1 Release Planning

Overview

Project Name

Enter the name of the project

Project Name

Enter the name of the project

Target Release Name

Dublin

Project Lifecycle State

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

Participating Company 

AT&T, Nokia, Ericsson, Tech Mahindra, Wipro, Huawei, Cisco, ChinaMobile

Scope

What is this release trying to address?

DCAE Dublin release has following primary objectives:

Adding new mS suite of collectors /event processors/analytics for supporting use cases identified by ONAP and integration. 

 

Following new services are targeted for R4 additions.

Collectors

  • RESTConf collector

Event Processors

  • VES/Universal Mapper

  • PM-Mapper

Analytics/RCA

  • SON-Handler (former PCI-Handler) 

  • Heartbeat (STRETCH GOAL)

  • TCA-Gen2  (STRETCH GOAL)

 

Common SDK design for DCAE services

  • Dmaap pub/sub

  • Configbindingservice

  • A&AI client (STRETCH GOAL)

  • Cert-based TLS (STRETCH GOAL)

 

Enhancement to existing DCAE components

  • VES Collector (security)

  • HV_VES (logging)

  • PRH (common sdk + BBS)

  • DataFileCollector (security enhancement + resiliency support)

 

DCAE Platform Enhancement

  • Support helm chart deployment in DCAE-C using custom helm plugin

  • Transitioning Cloudify blueprint to Helm for DCAE platform component (InventoryAPI, DeploymentHandler, PolicyHandler, ServicechangeHandler, CBS)

  • DCAE Healthcheck enhancement

In addition the following features will be worked as STRETCH GOAL

  • PNDA Platform integration with DCAE for application deployment support via helm

  • Integration with DMAAP BusController for Topic provisioning

  • Support for Multi-site K8S cluster deployment via K8s plugin (dependency on AAI, MultiCloud)

  • Contribution of blueprint generator tool in ONAP/DCAE
     

   Note:  Work on STRETCH GOAL will progress through R4 however they cannot be committed yet for delivery (due to resource constraint /external dependencies /unclear requirement). These will be evaluated around M3 and will be either committed or deferred.

 

(Added - 02/18/19) - Datalake as POC was approved by TSC. DCAE support for DL project is being tracked under this link  - DataLake POC

 

Use Cases

DCAE will provide support for the following use cases,

 

Functional Requirement 

  •  

    •  

      • New Policy API  support (Policy handler, Plugin, Deploymenthandler*) - (STRETCH GOAL)

      • ToscaLab (python) support SDC team for ONAP contribution  (DESCOPED)

      • Blueprint generator

      • K8s Plugin 

      • Dmaap plugin

      • Dashboard

      • Deployment Handler

         

Non-Functional Requirement 

  • PNF/xNF Authentication (Committed based on Nokia's contribution)

Platform Maturity

 Green color → Target level ( details see Platform Maturity below)

  •  

    •  

      • Performance:  Level 1

      • Stability: Level 2 (stetch with new ~52% coverage requirement for Dublin)

      • Resiliency: Level 2

      • Security: Level 1+

      • Scalability: Level 1

      • Manageability: Level 1+

      • Usability: Level 2                   

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.

DCAE Service specific components

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.  The value of DCAE lies in the number of types of data being collected, the number of analytics algorithms, the number of open/close control loops, and how well/easy they are supported for ONAP uses.

Long term roadmap will include 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

models in SDC and 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

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

 

Deliverable

Repository

 Maven Group ID

Components Description

restconf

dcaegen2/collectors/restconf

org.onap.dcaegen2.collectors.restconf

RESTConf Collector

son-handler

dcaegen2/services/son-handler

org.onap.dcaegen2.services.son-handler

SON-Handler MS

pm-mapper

dcaegen2/services/pm-mapper

org.onap.dcaegen2.services.pm-mapper

Mapper to process files from DR and transform to VES

tca-gen2

dcaegen2/analytics/tca-gen2  

org.onap.dcaegen2.analytics.tca-gen2

Standalone(SA) TCA

mapper

dcaegen2/services/mapper 

org.onap.dcaegen2.services.mapper 

Mapper Micro Services for snmp traps/restconf input to VES

heartbeat

dcaegen2/services/heartbeat 

org.onap.dcaegen2.services.heartbeat 

Missing Heartbeat Micro Services

ONAP Dependencies

List the other ONAP projects you depend on.

 

DCAE depends on the the following components as part of the general ONAP architecture:

  • SDC: For blueprint generation and distribution into DCAE-C

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

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 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+  (Dublin recommendation 2 - cannot be committed due to Resource constraint)

 

  •  

    • 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

Level 2 (Stetch with new ~52% coverage requirement for Dublin)

Level 2  - Dependent on integration team support

 

 

  •  

    • 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

 

Security

1

1+ (Dublin recommendation 2 - cannot be committed for following reason)

  • Resource constraint

  • CADI library not available for Python 

  • Process of AAF certificate distribution in K8S between ONAP components and external (xNF) to be defined

    DCAE team will integrate with Buscontroller integration for dynamic topic provisioning and AAF based role setting as STRETCH GOAL

 

 

  •  

    • 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+ (Dublin recommendation 2 - cannot be committed for following reason)

  • Resource constraint to support #2 and #4 under Level2
    (Level 2 - #1 and #3 will be targeted for Dublin)

 

 

  •  

    • 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

2 (STRETCH GOAL- based on resource availability)

 

 

 

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 Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

SDC model distribution API

API for retrieving TOSCA model of close loop

Currently Available

To fill out

Link toward the detailed API description

Policy Engine

API for retrieving configuration policy updates

TBD

TBD

NA

A&AI

API invoked for information enhancements

Currently Available

Currently Available

 

DMaaP Message Router

API for topic publish / subscribe

Currently Available

Currently Available

 

DMaaP Bus Controller

DMaaP Bus Controller is a part of DMaaP that provides topic provisioning; this is the API for topic provisioning.

Currently Available

Currently Available

 

 OOF

 PCI Optimization API http://{OOF-host}:{port}/api/oof/v1/pci

 TBD

 TBD

 

 ConfigDB (SDNC)

http://{ConfigDB-host/IP}:{port}/SDNCConfigDBAPI/getNbrList/{cellId}/{ts} (Get neighbor list for  a cell Id)

http://{ConfigDB-host/IP}:{port}/SDNCConfigDBAPI/getPnfName/{cellId}/{ts} (Get the PNF name for a cell Id)

 TBD