Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents

...

Project NameEnter the name of the project
Target Release NameLondon
Project Lifecycle StateMature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company AT&T, Nokia, Wipro, Huawei, DT, Capgemini

...

REQ#DCAE Commit StatusDCAE Impact AssessmentDCAE JIRA #
REQ-1378 - E2E Network Slicing use case enhancements for London release

YES

AI/ML MS for IBN based closed Loop in E2E Network Slicing

•    Mainstreaming the ml-prediction-ms(New mS introduction)
•    Support for multiple slices (sNSSAIs) in training and prediction modules
•    Use CPS instead of Config DB
•    Remove RAN Simulator dependency

Commitment from Kevin Tang sendil kumar Jaya kumar Ahila P /WIPRO  

DCAEGEN2-3067

London Features with DCAE Impact

REQ#DCAE <Pending resource/commitment>
REQ#DCAE Commit StatusDCAE Impact AssessmentDCAE JIRA #
REQ-1351 - External secure communication only via IngressNONo resource/support available from DCAE project; changes likely in OOM charts.


REQ-1349 - Removal of AAFStretch-goal

OOM-3068  (DCAE Svc template updates) - Jack Lucas 

DCAEGEN2-3095 /DCAEGEN2-3336 (RESTConf cert dependency removal) - Kedar Ambekar 

DCAEGEN2-3335 - VESOpenAPI - (question)

DCAEGEN2-3037 (EPIC) - Story DCAEGEN2-3095 /DCAEGEN2-3336 (RESTConf)

London Spec with DCAE Impact


DCAEGEN2-3335 - VESOpenAPI



REQ-1376 - DMaaP Enhancements for L releaseNO

DMAAP BC removal support 

BC used mainly for BulkPM flow for Feed provisioning - need assessment on switching DFC/PM-Mapper to use non-secure endpoints.


London Spec with DCAE Impact

REQ#DCAE Commit StatusDCAE Impact AssessmentDCAE JIRA #
REQ-1379 - Improve DCAE PRH to handle Early PNF RegistrationsYES
  • Configurable option to enable/disable reprocessing of AAI failed lookup
  • Log and auto-commit (to remove failed entry) if older than x timeframe
    • Enable persistence for PRH reprocessesing
    • DCAE SDK dmaap-client enhancement to support native kafka interface
    will be recommended. Depending on env/config/deployment properties, dmaap-client lib can serve a wrapper to switch between native kafka or MR REST api.

    Commitment from Sangeeta Bellara / DT

    DCAEGEN2-3312
    DCAE MOD retirementYES

    Retire MOD from ONAP/DCAE

    • OOM charts updates
    • Documentation

    Commitment from Vijay Kumar / AT&T

    DCAEGEN2-3278

    PM-Mapper Improvement/Bug-fixesYES

    Fix issues of duplicate events handling & DR retry

    Commitment from Viresh Navalli / Vamshi Namilikonda Capgemini

    DCAEGEN2-3315

    DCAEGEN2-3313

    NAYES

    Sonarcoverage improvements for DCAE components

    • Heartbeat MS, VESCollector

    Commitment

    from

    Sub-Jira under EPIC DCAEGEN2-3256

    NANOPending Assessment

    DMAAP SDK standardization for DCAE Microservices (following components are using cambria client)

    • KPI-
    mS
    mSRESTConf
    • mS (deferred from Kohn; need to be confirmed by Ahila P / Niranjana Y )
    • RESTConf  (No resouce/support available from DCAE project)

    DCAEGEN2-3030









    London POC (DCAE impact)

    REQ#DCAE Commit StatusDCAE Impact AssessmentDCAE JIRA #

    REQ-1072 - Standardized logging fields 

    REQ-1345 - Standardized logging fields - Python London release 

    NONo resources for POCNA

    Best Practices/GLOBAL Requirements

    REQ#DCAE Commit StatusDCAE Impact AssesmentDCAE JIRA #

    REQ-443 - CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL

    Global-REQ 

    YES

    DCAE passed silver badging; Gold badging improvements dependent on LF wide policy/infra updates.

    (No new impact for DCAE)

    NA

    REQ-439/REQ-1211- CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES

    Global-REQ

    Stretch-goal

    London DCAE 

    Commitment: Kedar Ambekar / DT Team  (TCAGEN2/RESTConf/PM-Mapper, DataFileCollector, VESMapper, SDK, VES-OpenAPI manager)

    Following are OPEN  (pending resource/commitment)

    DCAEGEN2-3318

    REQ-437 - COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8)

    Global-REQ

    YES

    Existing DCAE python components are already compliant; New mS (ml-prediction-mS) will also meet this requirement when delivered.

    Commitment from Wipro 

    Covered under REQ-1378 (Commitment from Kevin Tang Ahila P /WIPRO  )

    NA

    REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11)

    Global-REQ

    YES

    Complaint with DCAEMOD deprecation.

    Java17 upgrade pilot targetted for PM-Mapper in London (supported by Kedar Ambekar/DT Team)

    NA
    REQ-432/REQ-760
     - IPv4/IPv6 dual stack support in ONAP
    YES

    Enhance ONAP common-service template - add IPv4/IPv6 support

    (No new impact for DCAE)

    OOM-2749 

    REQ-441/REQ-1070 - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA - London RELEASE

    Global-REQ

    YES

    New mS (ml-prediction-mS) will be complaint to the requirement. All other DCAE mS area already complaint STDOUT logging


    Covered under REQ-1378 (Commitment from

    Wipro 

    Kevin Tang Ahila P /WIPRO  )

    Tracked under DCAEGEN2-3067

    REQ-1073 - Using basic image from Integration  

    YES

    (No new impact for DCAE in London release)

    NA

    REQ-1072 - Standardized logging fields REQ-1341 - Standardized logging fields - Java London release 

    Stretch-goalNO

    Will need updates to several DCAE java component - no resource

    (only vescollector updates committed by AT&T)

    REQ-1342 - Retirement of unmaintained repos YES

    DCAE MOD will be retired in London release

    Commitment from Vijay Kumar / AT&T

    DCAEGEN2-3278





    Best Practices

    ...


     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+             

    ...

    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

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

    1+



      • 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

    ...

    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 NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
    VES CollectorAPI for VNFs to send VES data Currently Available
    No change for this release
    HealthcheckAPI for querying DCAE component healthcheck Currently AvailableR4No change for this release
    Data Extraction Service (DES)API for data retrieval and simple computation from DL-Handler maintained storages (For R8, this will be used by DCAE components such Slice-Analyis MS) and UUICurrently AvailableR8No change for this release
    PMSH API support for Subscription/Filters/Measurement group management Currently AvailableR10

    No change for this release

    https://git.onap.org/dcaegen2/tree/docs/sections/apis/pmsh_swagger.json


    SliceAnalysis MsAPI support for data aggregation based on NSI/NSSI; this will be consumed by OOFCurrently AvailableR10

    No change for this release

    https://git.onap.org/dcaegen2/tree/docs/sections/apis/swagger_slice_analysis.json

    https://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/11774039616493831/slice-analysis-swagger.yaml?version=1&modificationDate=1640159785000&api=v2






    • Third Party Products Dependencies

    ...

    Risk identifiedMitigation PlanContingency Plan
    Documented under London Risks

    • Resources

    Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:dcae

    ...