Re: DMAAP-message-router-mirrormaker pods is not running #dmaap
While you are all discussing this, just want to point out a related Jira we created a long time ago: https://jira.onap.org/browse/OOM-1579
At that time, DMaaP design anticipated there might be a central “hub” and one or more edge deployments because the AT&T ECOMP architecture has long had central/edge deployments. (e.g. use case: edge data collector/central analysis function)
The blocking issue in ONAP has been some consensus on the technique and naming conventions for inter-K8S services, and as this Jira mentions, some deployment indicator for where you are deploying (and what the central deployment is named).
The vision, as it relates to this thread might look like:
Note: the direction of the message replication is important – you can’t have bidirectional replication on the same topic – but either direction is supported.
As Mandar, Sunil and I are getting pulled from ONAP soon, wish we had the Pruss CDS use case 6 months ago!
While we still have some limited cycles to consult, might somebody want to transition into DMaaP to complete the work using the newer MM?
From: onap-discuss@... <onap-discuss@...> On Behalf Of Michael Pruss
Sent: Tuesday, November 17, 2020 3:15 PM
To: SAWANT, MANDAR <ms5838@...>; onap-discuss@...
Subject: Re: [onap-discuss] DMAAP-message-router-mirrormaker pods is not running #dmaap