Global Requirements for DMaaP MR Removal in New Delhi

• Strimzi Apache Kafka provides an alaternative kafka cluster deployment method. This is a replacement for the legacy kafka offered by DMaaP Message Router.
• In New Delhi, DMaaP Message Router and its dependencies should be removed.

DMaaP team issued an epic for DMaaP MR deprecation, https://jira.onap.org/browse/REQ-1376 (see the dependency relationships with other projects)

Also, OOM analyzed its dependency analysis:

• DCAE:
  • dcae-ves-collector →  https://gerrit.onap.org/r/c/oom/+/137002?usp=search  code: https://git.onap.org/dcaegen2/collectors/ves/commit/?id=47195e4ac559963cd33dc155f219bd2b127ef025
  • dcae-prh → Gating planned, https://gerrit.onap.org/r/c/oom/+/137153
  • dcae-pmsh
  • dcae-tcagen2
  • dcae-son-handler
  • dcae-slice-analysis-ms
  • dcae-heartbeat
  • dcae-kpi-ms
  • dcae-datafile-collector
  • dcae-snmptrap-collector
  • (UPDATE info by DT) So there is a DCAE SDK for interaction with DMaaP.
    We have changed the implementation of that SDK  to talk to Kafka directly.
    This new SDK is now used in VES collector and PRH services.
    If other services are using the SDK to talk to DMaaP, they can use this new version now.
    We have updated documentation of this SDK as well.https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/sdk/apis.html
• NBI → planned by DT
• AAI-resources → planned by DT
• SO-bpmn-infra → planned by DT
• SDC-BE → to be checked why still connecting to MR

• • Michael Morris :
    From SDC point of view yes, but for any components subscribing to the messages (using sdc-distribution-client or their own implementation)
    then they will need to be updated to new kafka based version of sdc-distribution-client (2.0.1) or update their own impl if not using the sdc-distribution-client
    sdc-BE and sdc-distibution-client were both updated to support using either DMaaP or kafka.
• Policy
  • apex-pdp
  • xacml-pdp
  • apew-pdp
• SDNC
  • dmaap-listener
• Holmes