2022-01-04 DCAE Meeting Notes

S.NO

 Time (est)

 Topics

 Requester/Assignee

 Notes/Links

START RECORDING

PARTICIPANT LIST

Network Slicing Use Case - DCAE impacts in Jakarta release

+ IBN/CCVPN Closedloop Support

@Ahila P @Henry Yu @Dong Wang 

Discuss Slicing impact https://jira.onap.org/browse/DCAEGEN2-3021  & open items from 2021-11-30 DCAE Meeting Notes

E2E_Network_Slicing_DCAE impacts.pdf

Followup needed on below items (to be continued on next meeting or schedule separate call)

•  

  •  

    • Example on current training and configuration derived

    • Dependency/Interation with other ONAP components (e.g Policy, AAI) and Jakarta impact to be clarified

    • Training algorithm employed

    • Demo on how the ML MS is used on Slicing usecase flow will be useful

  Need to assess how/what source will be maintained in ONAP and can be supported in generic before it can be standardized as MS under DCAE project

CII badging

@Tony Hansen 

CII rebranded to OpenSSF Best Practice 

https://bestpractices.coreinfrastructure.org/en

Istanbul Maintenance release

@Vijay Kumar 

DCAEGEN2-3022 - Log4j vulnerability (2.0-beta9 to 2.14.1)

• https://www.helpnetsecurity.com/2021/12/13/log4shell-update-cve-2021-44228/

• https://www.kaspersky.com/blog/log4shell-critical-vulnerability-in-apache-log4j/43124/

• https://logging.apache.org/log4j/2.x/security.html

Recommendation from SECCOM was 2.16.0 in December; new CVE has been identified and  2.17.1 is the new target recommended version for now*

01/04/22 - Upgrade impacted DCAE components to 2.17.1 once SECCOM/TSC confirms 

12/17/21 - VESCollector, RESTConf, VES-Mapper impacted; new containers released using 2.16.0

Jakarata Release 

@Vijay Kumar 

• Release Planning: Jakarta

• R10 M1 -DCAEGEN2-2979 -  Rescheduled to 12/09/2021 - DONE

• ARC - ONAPARC-724 (Scheduled for 01/11/2022)

• R10 M2 - DCAEGEN2-3009(01/27/2022) 

• DCAE R10 Jakarta M2 Release Planning   

  • 01/04/2022 - To be reviewed by Sponsoring companies and REQ owners for clarification on DCAE impact and/or resource commitmment

• Jakarta Impact View per Component

@Vijay Kumar 

**Deferred to next meeting**

Review GR and BP approved for Jakarta & DCAE impact

1. Global Requirement

   1.  REQ-441/REQ-1070 - Log to std out/err  - No new impact (healthcheck and SNMPtrap collector addressed for J release).  SNMPTRap container pending to be released. 

2. Best-Practice

   1. REQ-1073 - Integration base image   - Impact for VESCollector/RestConf/SliceAnalysis

   2. REQ-1072 - Standardized log fields  - Jakarta Best Practice Proposal for Standardized Logging Fields - v2 

      1. Need to be assessed for any DCAE MS impact (for future release compliance)

3. Vulnerabilities identified by SECCOM needing version upgrades : DCAEGEN2-3006

Jakarata - Helm migration 

@Vijay Kumar 

**Deferred to next meeting**

Discuss DCAE transformation planned items for J release - DCAEGEN2-2773

Priorities

• Switch components to latest SDK version

• OOM charts updates to disable Cloudify/handlers (CBS may be exception depending on above item)

  • Iteration 1 (once OOM branching is done)- Disable all cloudify/handlers under dcaegen2 

  • Iteration 2 (M3/Jakarta)- Move VESOpenAPI and CBS? to dcaegen2-services 

• Integration testsuite migration

• Helm flow support through MOD 

• DMaap Provisioning optimization

  • Pub/sub credential handling alignment - OKAY to proceed 

  • Topic/Feed cleanup on undeploy -

    • Topic cleanup to be split into separate Jira and assessed later ; Feed cleanup OKAY to proceed. (Impacted by AAF removal, Strimzi Operator introduction)

• Review - DCAEGEN2-2774   DCAE MS SVC template enhancement - Deferred to K release

  • Any new usecase/MS demanding these features for J release (otherwise Jira will be moved to backlog)

• CBS removal for DFC has dependency on DCAEGEN2-2935

Closed:

• Disable DCAE platform in deployment - https://gerrit.onap.org/r/c/oom/+/125731 

• DCAE Mod helm flow support - https://gerrit.onap.org/r/c/oom/+/123932

To Do 

• dcaegen2/deployment - updated to remove CM container build  - DONE

• BBS-Eventprocessor (dcaegen2/services) - Builds and sub-component repo will be removed post ARC meeting/review (M2). 

  • Once approved by ARC - need buld jobs and corresponding helm-charts removed/disabled.

• Integration testsuite migration 

  • Cloudify based testsuite has been disabled in gating/daily runs

  • Krzysztof K working on Bulk-PM helm test - WIP 

• Documentation update for DCAE deployment and MOD setup

DIscuss PM-Mapper switch to use unauthenticated topic for below items.

• Multiple subscriber issue (DCAEGEN2-2937)

• Dmaap/Strimzi migration

• Servicemesh compliancy

@Vijay Kumar 

• @Fiachra Corcoran  indicated DMAAP team looking to build a standardized library for Strimzi/Kakfa migration across ONAP components-  to be confirmed in few weeks. Will hold on DCAE SDK standardization efforts across DCAE MS for time-being.

• PM-Mapper migration for switching to unauthenticated topic to be targetted for J release (SDK DMAAP integration is optional, but preferred). To bo be discussed with @Former user (Deleted) / @Former user (Deleted)  to finalize plan.

• SliceAnalysis/KPI-MS will remain on Cambri lib and will subscribe to PM_Mapper unauthenticated topic

Followup with @Fiachra Corcoran /DMAAP team on below

• Any solution to provision unauthenticated  topic/client in DMAAP MR currently part of ONAP deployment?

Currently most of unauthenticated topics (used by DCAE MS) are created on the fly (i.e during first event published). However this causes an issue for MS Client/consumer as they miss the first event (as client gets registered in kafka only after topic is created). This may be required for BulkPM Testsuite/SliceAnalysis/KPI-MS when PM_Mapper is switched to unauthenticated topic.

• Assess if DMAAP SDK client lib can be adapted to support Strimzi/Kafka and used as common target library

• HV_VES currently uses direct kafka interfaces; suggestion on how this should be handled part of Strimizi/Kafka migration - if any recommendation on the library to be used or change HV_VES kafka api's directly?

Other ONAP features/changes with DCAE impacts for Jakarta

@Vijay Kumar 

**Deferred to next meeting**

General discussion

• Servicemesh support - DCAE component impact on below 

1.  

   1. Allow http support (early J release) - DCAE components that rely only on HTTPS will be impacted

      1. Partial analysis completed; impact limited to 1-2 MS currently - will share the report into WIKi/next meeting - @Vijay Kumar 

   2. Components dependent on AAF cert 

      1. DR depenency on AAF is primarily on cert (auth is done local)

      2. Share the current findings and create wiki to capture the dependencies for DCAE components - @Vijay Kumar 

   3. Secure topic/feed dependency - DFC, PM-Mapper, PNF-Reg, SliceAnalysis, BBS-Ep

• Impact from DMAAP-MR → Strimzi/Kafka

  • Pub/sub API change - may need to integrate with new SDK provided by DMAAP team; all DCAE MS will have impact to align with new SDK.

    • SDK client lib need to have backward compatibility with MR (controlled via ENV/deployment property)

  • Mapping service - Alternate solution proposed by @Fiachra Corcoran /DMAAP team could be candidate solution; avoid technology dependency and can be handled generic across all MS without much impact

  • Provisioning API will change - DCAE helm template job MR provisioning template/scripts to be revisited under Strimzi/Operator

Black integration update

@Tony Hansen 

**Deferred to next meeting**

Topics/Demos' for future meetings

<Topics can be added below by presenters as they are ready>

TBD - Demo for DCAE MOD Helm flow support - @Vijay Kumar 

@Vijay Kumar

NA

@Tony Hansen

NA

@Jack Lucas

NA

@Former user (Deleted)

NA

@Former user (Deleted)

NA

@Former user (Deleted)

NA

@Niranjana Y 

NA