Versions Compared

Old Version 6

changes.mady.by.user kieran mccarthy

Saved on

compared with

New Version 7

changes.mady.by.user kieran mccarthy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

#IssueNotesDecision
1List scenariosNeed to clarify scenariosRefer to Internal study
2Topicswhat topics are used in what scenario (topic for each Datastore ?)Refer to Internal study
3Handle unknown event schemasWrap event?












Event Flow Sketch

Image Modified


CM Event Specification Outline

{

  "eventId"                           : "9999",                                                                        # some generic event uuid generated by DMI Plugin
  “eventCorrelationId”      : “cmhandleId-001”,                                                   # cmhandleId used for event correlation
  "eventTime"                     : "2021-11-16T16:42:25-04:00",
  "eventSource"                  : "org.onap.ncmp",                                                  
  "eventType"                      : "org.onap.ncmp.cm-notification-event",           # event type for async request response events 
  ”eventSchema”                 : “org.onap.ncmp:cm-notification-event",           # event schema for async request response events 
  ”eventSchemaVersion”    : “v1",                                                                        # event schema version

  "event":  {
              <RFC 8641-yang-datastore-notification-payload>                               # See next slide for example
   }

}

RFC 8641 : yang-datastore notification definition

notifications:

          +---n push-update

          |  +--ro id?                   sn:subscription-id

          |  +--ro datastore-contents?   <anydata>

          |  +--ro incomplete-update?    empty

          +---n push-change-update {on-change}?

             +--ro id?                   sn:subscription-id

             +--ro datastore-changes

             |  +--ro yang-patch

             |     +--ro patch-id    string

             |     +--ro comment?    string

             |     +--ro edit* [edit-id]

             |        +--ro edit-id      string

             |        +--ro operation    enumeration

             |        +--ro target       target-resource-offset

             |        +--ro point?       target-resource-offset

             |        +--ro where?       enumeration

             |        +--ro value?       <anydata>

             +--ro incomplete-update?    empty


'operation' type definition

...