References
CPS-2425 - Getting issue details... STATUS
CPS Data Notifications Overview
Issues & Decisions
Issue | Notes | Decisions | |
|---|---|---|---|
| 1 | We will just change the data schema field in the event header when we publish the event and we would still maintain the internal java type as is. | Csaba Kocsis or kieran mccarthy to provide more insights. | |
| 2 | When we start populating a different data schema , will that seamlessly integrate with the code at your end ? Or we still have to coordinate this change ? | Csaba Kocsis or kieran mccarthy to provide more insights. |
Issues & Decisions on event schemas
Issue | Notes | Decisions | |
|---|---|---|---|
| 1 | Async Event DataOperation Event | NCMP Produces DataOperationEvent | All schemas should have urn:cps column be a prefix Csaba Kocsis Kolawole Adebisi-Adeolokun |
| 2 | Cm Notification Subscriptions | NCMP Produces and Consumes the events | All schemas should have urn:cps column be a prefix Csaba Kocsis Kolawole Adebisi-Adeolokun |
| 3 | Dmi Data Avc Event | Events we receive from DMI | Since NCMP is consuming it , so we dont have any changes to be done. Only the application publishing it will have to do it. |
| 4 | Lcm ( Lifecycle Management Events) | NCMP Produces LCM Events | Leave as is, Topology changes to cloud event won’t come in till 2026. Priyank Maheshwari and Kolawole Adebisi-Adeolokun |
| 5 | NCMP Data Avc Event | NCMP Produces AvcEvent | All schemas should have urn:cps column be a prefix Csaba Kocsis Kolawole Adebisi-Adeolokun Priyank Maheshwari to check why NCMP Data Avc Event have a different schema to Dmi Data Avc Event Should this schemas not be the same ? |
| 6 | TrustLevel Events | NCMP Consumes Device Heartbeat | All schemas should have urn:cps column be a prefix Csaba Kocsis Kolawole Adebisi-Adeolokun |
Data Schema and Type Mapping
Below table shows the current mapping of the dataschema and type been send/received as part of the notifications.
Use Case | Current Data Schema | Internal Java Type | Expected Data Schema | |
|---|---|---|---|---|
| 1 | AsyncEvent - DataOperationEvent | urn:cps: org.onap.cps.ncmp.events.async1_0_0.DataOperationEvent:1.0.0 | org.onap.cps.ncmp.events.async1_0_0.DataOperationEvent | urn:cps: org.onap.cps.ncmp.events.async.DataOperationEvent:1.0.0 |
| 2 | Cm Notification Subscription ( Produce and Consume) | org.onap.ncmp.cm.subscription:1.0.0 ( Incoming to NCMP ) org.onap.ncmp.cm.subscription:1.0.0 ( Outgoing from NCMP ) org.onap.ncmp.dmi.cm.subscription:1.0.0 ( Incoming to DMI Plugin from NCMP ) org.onap.ncmp.dmi.cm.subscription:1.0.0 ( Outgoing from DMI towards NCMP ) | org.onap.cps.ncmp.impl.cmnotificationsubscription_1_0_0.client_to_ncmp.NcmpInEvent org.onap.cps.ncmp.impl.cmnotificationsubscription_1_0_0.ncmp_to_client.NcmpOutEvent org.onap.cps.ncmp.impl.cmnotificationsubscription_1_0_0.ncmp_to_dmi.DmiInEvent org.onap.cps.ncmp.impl.cmnotificationsubscription_1_0_0.dmi_to_ncmp.DmiOutEvent | ur:cps:org.onap.ncmp.cm.subscription:1.0.0 |
| 3 | DMI Data Avc (Consuming) | Since we are just consuming , hence the team publishing will decide the schema. | ||
| 4 | Lcm ( Lifecycle Management Events ) | Non Cloud Event | org.onap.cps.ncmp.events.lcm.v1.LcmEventHeader | Non Cloud Event |
| 5 | NCMP Data Avc ( Used for publishing trustlevel changes) | urn:cps:org.onap.cps.ncmp.events.avc.ncmp_to_client.AvcEvent:1.0.0 | org.onap.cps.ncmp.events.avc.ncmp_to_client.AvcEvent | ?? |
| 6 | Trust Level Events (Consuming) heartbeat messages coming from DMIs |