Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

References

CPS-2425 - Getting issue details... STATUS

CPS Data Notifications Overview

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

All schemas should have urn:cps column be a prefix Csaba Kocsis Kolawole Adebisi-Adeolokun

4

Lcm ( Lifecycle Management Events)

NCMP Produces LCM Events

Leave as is, Topology changes to cloud event won’t come in till 2026.

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 ?
[ Replied for #3 and #5 as comment]

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

urn: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
DataSchema : org.onap.ncmp:cmhandle-lcm-event
Version : 1.0

org.onap.cps.ncmp.events.lcm.v1.LcmEventHeader

Non Cloud Event
DataSchema : org.onap.ncmp:cmhandle-lcm-event
Version : 1.0

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

  • No labels