Versions Compared

Old Version 1

changes.mady.by.user Luke Gleeson

Saved on

compared with

New Version Current

changes.mady.by.user Luke Gleeson

Saved on

Key

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

Table of Contents

References

<insert Jira Ref, Using confluence menu options +, Jira Issue/Filter>
<optional other relevant references, Jiras, Confluence pages, external links>

Assumptions<optional>

...

Jira
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1431

Assumptions

#AssumptionNotes
1

Issues & Decisions

NCMP receives subscription through topic cm-avc-subscription
2

Message body is consumed as 

Code Block
collapsetrue
{
  "version": "1.0",
  "eventType": "subscriptionCreated",
  "event": {
    "subscription": {
      "clientID": "SCO-9989752",
      "name": "cm-subscription-001"
    },
    "dataType": {
      "dataspace": "ALL",
      "dataCategory": "CM",
      "dataProvider": "CM-SERVICE"
      "schemaName": "org.onap.ncmp:cm-network-avc-event.rfc8641"
      "schemaVersion": "1.0"
    },
    "predicates": {
                   “targets” :  [“sdsd”, “slada”, “ccde3”]     #  cmhandle targets
        "datastore": “passthrough-operational",
        "datastore-xpath-filter": "//_3gpp-nr-nrm-gnbdufunction:GNBDUFunction/ 
             _3gpp-nr-nrm-nrcelldu:NRCellDU/ | //_3gpp-nr-nrm-gnbcuupfunction:GNBCUUPFunction// |
            //_3gpp-nr-nrm-gnbcucpfunction:GNBCUCPFunction/_3gpp-nr-nrm-nrcelldu:NRCellCU// |
            //_3gpp-nr-nrm-nrsectorcarrier:NRSectorCarrier//”  
 
    }
}



3

Message body is forwarded as 

Code Block
collapsetrue
{
  "version": "1.0",
  "eventType": "subscriptionCreated",
  "event": {
    "subscription": {
      "clientID": "SCO-9989752",
      "name": "cm-subscription-001"
    },
    "dataType": {
      "dataspace": "ALL",
      "dataCategory": "CM",
      "dataProvider": "CM-SERVICE"
      "schemaName": "org.onap.dmi:cm-network-avc-event.rfc8641"
      "schemaVersion": "1.0"
    },
    "predicates": {
                   “targets” :  [  { cmhandle : “sdsd”,
                                              cmhandle-properties” : {
                                                  “prop1” : “prop-value”
                                               }
                                           },
                                           {  cmhandle : “slada”,
                                              cmhandle-properties” : {
                                                  “prop-x” : “prop-valuex”
                                               }
                                           }, 
                                           {  cmhandle : “ccde3”,
                                              cmhandle-properties” : {
                                                  “prop-y” : “prop-valuey”
                                               }
                                           }
                                        ]     #  cmhandle targets
        "datastore": “passthrough-operational",
        "datastore-xpath-filter": "//_3gpp-nr-nrm-gnbdufunction:GNBDUFunction/ 
             _3gpp-nr-nrm-nrcelldu:NRCellDU/ | //_3gpp-nr-nrm-gnbcuupfunction:GNBCUUPFunction// |
            //_3gpp-nr-nrm-gnbcucpfunction:GNBCUCPFunction/_3gpp-nr-nrm-nrcelldu:NRCellCU// |
            //_3gpp-nr-nrm-nrsectorcarrier:NRSectorCarrier//”  
 
    }
}



Open Issues

#

IssueNotes Decision
1
Do we need a analysis template?is convention for (new) developers to guide them2This is an open issue3This is a very important (blocking issue)

<Note. use green for closed issues, yellow for important ones if needed>

Any Other Header

< we do not want to dictate the remainder of an analysis it will depend on the type of user story at hand>

Any Other Header

...

What topic do we forward event toDMI-DATA what names are allowed and do they conflict with allowed topic namesEvent will be forwarded under topic ncmp-dmi-cm-avc-subscription-{DMI-DATA-SERVICE-NAME}
2

Question: Assumption is all DMIs read message and determine whether it is applicable to them based on the cmhandles included in the targets. DMIs cannot be targeted specifically as it is an async kafka message

Answer: Sounds like a security related bug that is being worked around. Can this be fixed so that each DMI provides the topic it uses for subscriptions?

Follow up Question: Target cmhandles are optional? In this case NCMP cannot determine which DMIs to send to and all DMIs will have to read it.

DMI Specific Topic (registration update)

Convention approach dmi-data or dmi service name

"For dmi to be able to forward subscriptions to you setup on this topic and give dmi rw access"

DMIs are responsible for setting up the topic

Convention is set by topic above - Document : "DMI gives itself read access and gives NCMP write access"

3

Is the datastore going to be a mandatory field in the predicate body for datastore validation purposes (ONLY Passthrough supported)

Answer: On the device, we need to be prepared for NMDA. I.e. the subscription will be targeted to either operational or running, or both.

As long as the schema introduced now (for passthrough only) supports extensibility without backward incompatibility, I’m good.


Datastore will be validated
4In the forwarded message, cm-handle properties are added by NCMP. Is this just public properties or public and private properties
Only private properties are appended