Versions Compared

Old Version 5

changes.mady.by.user Vijay Kumar

Saved on

compared with

New Version 6

changes.mady.by.user Vijay Kumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: DCAE R6 M1 updates


Table of Contents
outlinetrue

Overview

Project NameEnter the name of the project
Target Release NameFrankfurt
Project Lifecycle StateIncubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company AT&T, Nokia, Ericsson, Wipro, IBM, TechM

Scope

What is this release trying to address?

...

  • Addressing one of the long term goal in simplifying to simplify the onboarding experience for MS in DCAE. Introducing new MicroService, Onboarding & Design Platform (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

...

  • 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
    • DCAEGEN2-1774 - Optimize VES schema load by retain in-memory than loading file each time (dint find corresponding jira, created new today)
    • DCAEGEN2-608 608   - Performance/benchmarking
    • DCAEGEN2-1776 1776  - Remove certOnly and basicAuth from authentication methods
    • DCAEGEN2-1779  - 1779 Switch VES collector's K8s health checks to HTTPS
  • TCA-gen2 delivery and replace TCA/cdap
    • Mongodb support for tca-gen2
  • Deployment optimization (Plugin load, reduce bootstrap, Cloudify version syncup)
  • Python 3.x (5.0.5 - Cloudify mock available; 5.1 – full python 3.x)
  • Automated test improvement (csit/robot)
  • DCAE Helm chart org (and OOM-1574)
    • (transfer dependent on OOM team)

...

 Platform Maturity (i.e., S3P items)  https://wiki.onap.org/display/DW/Dublin+Release+Platform+Maturity

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

...

    •   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)
    •   PRH
    •   HV_VES

...

Deliverable NameDeliverable 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.

...

In addition to existing platform/service component, following new components are targeted for DublinFrankfurt.


son-handlerpm-mapperpm-mapper
DeliverableRepository Maven Group ID

Components Description

restconfpmsh

dcaegen2/collectors/restconfservices

org.onap.dcaegen2.collectorsservices.restconf

RESTConf Collector

pmsh

PM Subscription Handler

tca-gen2dcaegen2/servicesanalytics/sontca-handlergen2  

org.onap.dcaegen2.

services

analytics.

son

tca-

handler		SON-Handler MS

gen2

Standalone TCA
heartbeatdcaegen2/services/heartbeat org.onap.dcaegen2.services.pm-mapperMapper to process files from DR and transform to VES
tca-gen2dcaegen2/analytics/tca-gen2  

org.onap.dcaegen2.analytics.tca-gen2

Standalone(SA) TCA
mapperdcaegen2/services/mapper org.onap.dcaegen2.services.mapper Mapper Micro Services for snmp traps/restconf input to VES
heartbeatdcaegen2/services/heartbeat org.onap.dcaegen2.services.heartbeat Missing Heartbeat Micro Services

...

heartbeat Missing Heartbeat Micro Services

ONAP Dependencies

List the other ONAP projects you depend on.

...

Anyone reading this section should have a good understanding of all the interacting modules.TBA


Image Added



Image Added


Image Added

 

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.

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance11+
    • 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)
Stability2

Level 2

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
Resiliency22
    • 0 – none
    • 1 – manual failure and recovery (< 30 minutes)
    • 2 – automated detection and recovery (single site)
    • 3 – automated detection and recovery (geo redundancy)
Security1

1+



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

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
Manageability1

1+



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

2 (STRETCH GOAL- based on resource availability)



    • Level 1:
      • User guide created
      • Deployment documentation
      • API documentation
      • Adherence to coding guidelines
    • Level 2:
    • Level 3
      • Consistent UI across ONAP projects
      • Usability testing conducted
      • API Documentation
    • Level 4


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

...

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
SDC model distribution APIAPI for retrieving TOSCA model of close loopCurrently AvailableTo fill outLink toward the detailed API description
Policy EngineAPI for retrieving configuration policy updatesCurrently AvailableCurrently AvailableNA
Policy (PDP) API to push DCAE MS configuration/policy modelsCurrently AvailableCurrently Available
A&AIAPI invoked for information enhancementsCurrently AvailableCurrently Available
DMaaP Message RouterAPI for topic publish / subscribeCurrently AvailableCurrently Available
DMaaP Bus ControllerDMaaP Bus Controller is a part of DMaaP that provides topic provisioning; this is the API for topic provisioning.Currently AvailableCurrently Available
 OOF

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

 http://{pcims-host}:{port}/callbackUrl Call back URL for SON-MS (to provide PCI optimization results)

 Currently Available Currently Available
 ConfigDB (SDNC) ConfigDB

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)		 Currently AvailableCurrently Available

  • API Outgoing Dependencies

API this project is delivering to other projects.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
VES IngestionAPI for VNFs to send VES dataCurrently AvailableR3
DCAE Deployment HandlerNB API for invoking the deployment of DCAE subcomponentsCurrently AvailableR3
DCAE InventoryAPI for Add/Delete DCAE copy's TOSCA modelsCurrently AvailableR3
HealthcheckAPI for querying DCAE component healthcheck Currently AvailableR4

    • 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

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

Describe the plan to integrate and test the release deliverables within the overall ONAP system. Confirm that resources have been allocated to perform such activities.

healthcheck Currently AvailableR4
DCAE Onboarding APIAPI for publishing DCAE spec into MODWill be available around M3R6
DCAE InventoryAPI for CLAMP to retrieve flow informationWill be available around M3R6

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

NameDescriptionVersion
NIFIApache NIFI
Cloudify Manager

Consul

CDAP

PNDA




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
      • CSIT tests will continue to be supported for existing components
      • Pairwise testing will be done in the WindRiver Dev lab similar to what was done in last release

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

Gaps identifiedImpact
To fill outTo fill out

  • Known Defects and Issues

Provide a link toward the list of all known project bugs.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=dcaegen2 and issuetype in (bug) and fixversion='Frankfurt Release' and status != 'Closed'
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

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

Risk identifiedMitigation PlanContingency Plan

To fill outTo fill out

  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

The milestones are defined at the Release Level 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.

...

DateProjectDeliverable
To fill outTo fill outTo fill out

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

...

titleNote

...

Other Information

    • Vendor Neutral

...