Versions Compared

Old Version 24

changes.mady.by.user Priyank Maheshwari

Saved on

compared with

New Version Current

changes.mady.by.user Priyank Maheshwari

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

References

...

Issues & Decisions

Issue

Notes

Decisions

1

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

23

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.

3

Renaming of the existing schemas.

  1. DMI Data Avc Event can be called as DMI Cm Avc Event ( Issue#3 in the below table)

  2. NCMP Data Avc Event to also be renamed. ( TBD )

...

SDK Impacts at Ericsson. Csaba Kocsis
NCMP Documentation to say listen on both the event schemas ( as the schema doesn't change ) Priyank Maheshwari

Coordination Needed

Agreed Event Schema Names

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


urn:cps:org.onap.cps.ncmp.events.batch-response:1.0.0
NCMP to document changes related to old and new schema as content of the schema doesn't change.

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


urn:cps:org.onap.ncmp.events.subscription:1.0.0

3

Dmi Data Avc Event

Events

we receive from DMISince NCMP is consuming it , so we dont have any changes to be done. Only the application publishing it will have to do it.
Priyank Maheshwari and Kolawole Adebisi-Adeolokun

NCMP receives from DMI


urn:cps:org.onap.cps.ncmp.events.moi-changes:1.0.0

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


urn:cps:org.onap.cps.ncmp.events:cm-handle-lcm:1.0.0
Note : to be done only when this is compliant with Cloud Events.

5

NCMP Data Avc Event (northbound)

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]


urn:cps:org.onap.cps.ncmp.events.cm-handle-changes:1.0.0
To be confirmed. Awaiting response from kieran mccarthy or Csaba Kocsis

Note : Agreed to leave as it is in alignment with 3GPP. ( based on comment from kieran mccarthy )

6

TrustLevel Events

NCMP Consumes Device Heartbeat

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


urn:cps:org.onap.cps.ncmp.dmi.events:cm-handle-trust-level:1.0.0

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

Expected

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.

async.DataOperationEvent

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.

cm

events.subscription:1.0.0

urn:cps:org.onap.ncmp.cm.subscription:1.0.0

3

DMI Data Avc (Consuming)
( CM Data Notifications coming to NCMP from DMI )

Since we are just consuming , hence the team publishing will decide the schema.

urn:cps:org.onap.cps.ncmp.events.moi-changes:1.0.0

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

urn:cps:org.onap.cps.ncmp.events:cm-handle-lcm:1.0.0 No change to be done now. Just name agreed.

5

NCMP Data Avc ( Used for publishing trustlevel changes)
Northbound

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

??
urn:cps:org.onap.cps.ncmp.events.cm-handle-changes:1.0.0 ( do we use ncmp notify events ?? kieran mccarthy )

6

Trust Level Events (Consuming)

heartbeat

trust level messages coming from DMIs

urn:cps:org.onap.cps.ncmp.events:device-trust-level-event-schema:1.0.0

urn:cps:org.onap.cps.ncmp.dmi.events:cm-handle-trust-level:1.0.0