Hey Vijay,

Yes, the api's will prob remain for as long as necessary.

I noticed today that CTC are coding towards the dcae sdk which maybe isn't the 
best strategy.
https://gerrit.onap.org/r/c/dcaegen2/services/+/130050

Although if all dcae clients utilise the sdk then I guess the transition would 
be smoother in future.
At present we (DMaaP team of 2) 🙂 are focused on the mess that is 
SDC/sdc-distro-clients.

I know yourself and Seshu have shown interest in the migration, which is much 
appreciated but I think it may take a few (if not more) releases to resolve.

[cid:58786a2d-7ee2-450c-a672-ab266e16e825]

Fiachra Corcoran

GFTL EST Ireland

[email protected]

Ericsson Software Technology

Ericsson Software Campus

Athlone

Ireland

N37 PV44

________________________________
From: VENKATESH KUMAR, VIJAY <[email protected]>
Sent: 28 July 2022 14:55
To: Fiachra Corcoran <[email protected]>; [email protected] 
<[email protected]>
Cc: Chaker Al-Hakim <[email protected]>
Subject: RE: [onap-discuss] Message Router api deprecation #dmaap


Hi Fiachra,

Could you confirm if DMAAP MR API’s will still be available under OOM 
deployment for Kohn?



As you are aware, migration to Strimzi/Kafka impact almost all DCAE 
microservices and changes involved are beyond just helm charts updates. For 
Kohn, we have EPIC (DCAEGEN2-3030<https://jira.onap.org/browse/DCAEGEN2-3030>) 
to standardize dmaap-client 
library<https://github.com/onap/dcaegen2-services-sdk/tree/master/rest-services/dmaap-client>
 (under repo:dcaegen2/services/sdk) which will continue to leverage MR api’s. 
The plan eventually is to update this SDK lib to support Strimzi/kafka api’s 
based on deployment configuration (retaining backward compatibility to MR). 
However as we do not have resources, this SDK update cannot be committed for 
Kohn.



It would be helpful if someone from the community/DMAAP team can help to 
enhance the SDK api’s which will enable smoother transition for the DCAE 
services.



P.S - If there are other solution design identified to make this migration 
seamless for applications, would certainly be interested in them.



Thanks,

Vijay



From: [email protected] <[email protected]> On Behalf Of 
Fiachra Corcoran via lists.onap.org
Sent: Thursday, July 28, 2022 5:26 AM
To: [email protected]
Subject: [onap-discuss] Message Router api deprecation #dmaap



Dear ONAP community,

As part of the Kohn release the DMaaP project is deprecating the Message Router 
apis.
With this, it is STRONGLY recommended that new and existing projects avoid 
developing towards these apis.

The evolution of messaging within ONAP is moving to use strimzi kafka. (Kafka 
native or REST over strimzi kafka bridge)
If more details are required please feel free to contact the dmaap team on our 
onap slack channel.




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#24121): https://lists.onap.org/g/onap-discuss/message/24121
Mute This Topic: https://lists.onap.org/mt/92666891/21656
Mute #dmaap:https://lists.onap.org/g/onap-discuss/mutehashtag/dmaap
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to