OOM New Delhi Release

Owned by Andreas Geißler
Last updated: Apr 17, 2024
1 min read

ONAP component list for discussion.

As discussed in TSC 2024-03-28 and OOM Meeting (OOM Meeting Notes - 2024-03-27), we should review the list of component to be deployed in the New Delhi release.

Background for this decision is:

The removed components could be listed in the release notes of New Delhi.

Candidates list of components/subcomponents, which need to be "disabled" from default OOM deployment.

Component

Subcomponent

Reasons

Component

Subcomponent

Reasons

CLI



  • No updates to support Istio since 3 releases

  • Not maintained

  • Agreed with Dan Xu

DCAEGEN2

dcae-pmsh

  • needs MR

  • not updated

DCAEGEN2

dcae-tcagen2

  • needs MR

  • not updated

DCAEGEN2

dcae-son-handler

  • needs MR

  • not updated

DCAEGEN2

dcae-slice-analysis-ms

  • needs MR

  • not updated

DCAEGEN2

dcae-heartbeat

  • needs MR

  • not updated

DCAEGEN2

dcae-kpi-ms

  • needs MR

  • not updated

DCAEGEN2

pm-mapper

  • needs MR and data-router

  • not updated

DCAEGEN2

dcae-datafile-collector

  • needs MR and data-router

  • not updated

DCAEGEN2

dcae-snmptrap-collector

  • needs MR

  • not updated

DMAAP

message-router

data-router

  • DR only used by pm-mapper and data-file-collector

  • if the DCAE components are not deployed, the whole DMaaP component can be disabled

HOLMES



  • needs MR

  • not updated

MODELLING



  • No changes in etsi-catalog chart since 04/2022

  • Agreed with Deng Hui

MSB



  • already decided to be removed as Ingress replaces it

NBI



  • needs MR

  • is archived

  • DT uses fork and checks, whether Kafka patch can be supported, if component is required

OOF



  • no changes since 2023

  • needed by usecase ?

SDNC

dmaap-listener

  • needs MR

  • listen on events for usecases

  • seems not to be used

VFC



  • no updates since 2022

  • Agreed with Keguang He

VNFSDK



  • no changes since 2021

  • Agreed with Dan Xu