| Table of Contents |
|---|
...
CPS Data Notifications Overview
Issues & Decisions
...
Issue | Notes | Decisions | |
|---|---|---|---|
| 1 |
Async Event DataOperation Event
Schema prefix | All schemas should have urn:cps column be a prefix Csaba Kocsis Kolawole Adebisi-Adeolokun | ||
| 2 | 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. Although we discussed during the meeting that it has no affect at your end but just to record the decision I am putting it here. | Csaba Kocsis or kieran mccarthy to provide more insights. | No issue |
| 3 | 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. | SDK Impacts at Ericsson. Csaba Kocsis Coordination Needed |
Agreed Event Schema Names
Issue | Notes | Decisions | |
|---|---|---|---|
| 1 | Async Event DataOperation Event | NCMP Produces DataOperationEvent | |
| 2 | Cm Notification Subscriptions | NCMP Produces and Consumes the events |
| ||
| 3 | Dmi Data Avc Event | Events |
NCMP receives from DMI |
| ||
| 4 | Lcm ( Lifecycle Management Events) | NCMP Produces LCM Events |
| ||
| 5 | NCMP Data Avc Event (northbound) | NCMP Produces AvcEvent |
All schemas should have urn 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 ?
Note : Agreed to leave as it is in alignment with 3GPP. ( based on comment from kieran mccarthy ) | ||
| 6 | TrustLevel Events | NCMP Consumes Device Heartbeat |
|
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 Name | Internal Java Type |
|---|
Proposed New Data Schema Name | ||||
|---|---|---|---|---|
| 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. |
batch-response:1.0.0 ( Need to document in the RTD - same event , just the event schema name has changed ) | ||||
| 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. |
events.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) trust level messages coming from DMIs |
|
|