Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added DL POC link

...

Project NameEnter the name of the project
Target Release NameDublin
Project Lifecycle StateIncubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company AT&T, Nokia, Ericsson, Tech Mahindra, Wipro, Huawei, Cisco (TBC), ChinaMobile

Scope

What is this release trying to address?

...

Collectors

  • RESTConf collector (Huawei)

Event Processors

  • VES/Universal Mapper (TechM)
  • PM-Mapper (Ericsson)

Analytics/RCA

  • SON-Handler (former PCI-Handler (Wipro) 
  • Heartbeat (AT&TSTRETCH GOAL)
  • TCA-Gen2 (AT&T) Gen2  (STRETCH GOAL)


Common SDK design for DCAE services

...

  • VES Collector (security)
  • HV_VES (logging)
  • PRH (common sdk + BBS)
  • DataFileCollector (security enhancement + resiliency support)

In addition the following features will be worked as STRETCH GOAL


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 helmPNDA Platform integration with DCAE for application deployment/configuration support
  • 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
  • Migration of static service components into deployment into helm chart 
  •  

   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
    - Partial commit ( Resource commitment pending)
      • (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 (Pending commitment Committed based on Nokia's contribution)

Platform Maturity

 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)

      • Performance:  Level 1
      • Stability: Level
    1+ (80% coverage cannot be met overall due to number of components; will be phased and approached for Dublin
      • 2 (stetch with new ~52% coverage requirement for Dublin)
      • Resiliency: Level 2
      • Security: Level 1+
      • Scalability: Level 1
      • Manageability: Level
    2 (STRETCH GOAL)
      • 1+
      • Usability:
    Level 2 (STRETCH GOAL)

...

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

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Resouce and Repositories in the centralized page.

...

DeliverableRepository Maven Group ID

Components Description

restconf

dcaegen2/collectors/restconf

org.onap.dcaegen2.collectors.restconf

RESTConf Collector

pcison-handlerdcaegen2/services/pcison-handlerorg.onap.dcaegen2.services.pcison-handlerPCISON-Handler MS
pm-mapperdcaegen2/services/pm-mapperorg.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

...

  • 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

...

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

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

Level 2  - Dependent on integration team support1+ (Dublin recommendation 2 - may not reach 80% code coverage due to number of repository in DCAE; will be phased and some component targeted for R4)



    • 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+ (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 
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

2 (STRETCH GOAL- based on resource availability)

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: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 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 updatesTBDTBDNA
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 Availableis the API for topic provisioning.Currently AvailableCurrently 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)
 TBDTBD  Currently Available
    • API Outgoing Dependencies

...

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  TBDR4 
SON-Handler http://{pcims-host}:{port}/callbackUrl Call back URL for SON-MS (to provide PCI optimization results)M3 R4 
    • Third Party Products Dependencies

...

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.

...