Versions Compared

Old Version 10

changes.mady.by.user Vijay Venkatesh Kumar

Saved on

compared with

New Version Current

changes.mady.by.user Vijay Venkatesh Kumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: ves 6.0->ves7.1

...

  1. High-Volume VES collector microservice (under 5G/performance analysis and optimization)
  2. File collector microservice   (under 5G/performance analysis and optimization) **Dependency Has dependency on DMaaP project for BusController delivery DataRouter delivery 
  3. PM Mapper microservice  (under 5G/performance analysis and optimization) **Dependency Has dependency on DMaaP project for DataRouter delivery (Stretch Goal, not currently committed for Casablanca))
  4. Standalone TCA microservice

...

In addition, DCAE team will work on following enhancement as Stretch Goal (not currently committed for Casablanca due to resource constraint / external dependencies /unclear requirement )

  • (S3P:security) Buscontroller integration for dynamic topic provisioning and AAF based role setting.  **Dependency Has dependency on DMaaP project for BusController delivery
  • (S3P:Performance) Performance optimization
    • VESCollector
    • TCA (new TCA service independent of CDAP will be contributed for R3).
  • VES 6.0 upgrade support (Updated  07/31/18 - VES 7.0.1 will be supported in R3 and will replace 6.0 originally planned) 
    • Primarily VES Collector updates for new domains and transformation
      (Security requirement for mutual TLS needs further clarification)
  • DCAE onboarding tool (dcae_cli) enhancement and environment support
  • (S3P: Maintainability) Logging format compliance
  • (S3P: Resiliency) MultiMutli-site support   **Dependency Has dependency on OOM Team
  • (S3P: Security) Securing api/interface and authorization via AAF (Need further clarification/support from Security/AAF team -  1) CADI library not available for Python 2) Consistent solution for AAF integration not identified (security proposal has many items WIP) 3) Process of AAF certificate distribution in K8S for components not defined and esp for components interfacing with external to ONAP)
  • Following R2 items (descoped due to time/resource constraint) will be continued to enhanced for platform integration/S3P needs

...

DCAE will support the following functional requirements listed on the Casablanca Release Requirements page: 

    • 5G/PNF
           Partial Commit - Support for new collector and services for processing highvolume RAN measurement and bulk data file processing
    • Scaling
      Scaling - Test only (No additional development expected from DCAE to support this requirement)

...

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

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your projectResouce and Repositories in the centralized page.

...

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


Deliverable
repoDescriptionDataFileCollector
Repository Maven Group ID

Components Description

data-file-collectordcaegen2/collectors/datafileorg.onap.dcaegen2.collectors.datafileData File
collector
collector 
HV
hv-ves-
VESCollector
collectordcaegen2/collectors/hv-vesorg.onap.dcaegen2.collectors.hv-vesHigh Volume VES Collector
PM
pm-
Mapper
mapperdcaegen2/services/pm-mapperorg.onap.dcaegen2.services.pm-mapperMapper to
processing
process files from DR and transform to VES
TCA
tca-
SA
gen2dcaegen2/analytics/tca-
sa    
gen2  

org.onap.dcaegen2.analytics.tca-gen2

Standalone(SA) TCA




Architecture

High level architecture diagram

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance12(stretch)
    • 0 -- none
    • 1 – baseline performance criteria identified and measured
    • 2 & 3 – performance improvement plans created & implemented
Stability22
    • 0 – none
    • 1 – 72 hours component level soak w/random transactions
    • 2 – 72 hours platform level soak w/random transactions
    • 3 – 6 months track record 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

Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear and cannot be committed to.


Securing api/interface and authorization via AAF (Stretch Goal, not currently committed for Casablanca due to following 1) CADI library not available for Python 2) Consistent solution for AAF integration not identified (security proposal has many items WIP) 3) Process of AAF certificate distribution in K8S for components not defined and esp for components interfacing with external to ONAP)


Buscontroller integration for dynamic topic provisioning and AAF based role setting.  **Dependency on DMaaP project for BusController delivery (Stretch Goal, not currently committed for Casablanca)



    • 0 – none
    • 1 – CII Passing badge + 50% Test Coverage
    • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
    • 3 – CII Gold
Scalability1

1

Mutli-site support   **Dependency on OOM Team (Stretch Goal, not currently committed for Casablanca)


    • 0 – no ability to scale
    • 1 – single site horizontal scaling
    • 2 – geographic scaling
    • 3 – scaling across multiple ONAP instances
Manageability1

1

Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear (independent upgrade) and cannot be committed to.



    • 1 – single logging system across components; instantiation in < 1 hour
    • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability1

1

Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear (related to tutorial documentation) and cannot be committed to.


    • 1 – user guide; deployment documentation; API documentation
    • 2 – UI consistency; usability testing; tutorial documentation

...

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.

...