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 5 Next »

References

CPS-1431 - Getting issue details... STATUS

Assumptions

#AssumptionNotes
1NCMP receives subscription through topic cm-avc-subscription
2

Message body is consumed as 

{
  "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 

{
  "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
1Event will be forwarded under topic ncmp-dmi-cm-avc-subscription

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?

I think it might be seen as bad if a Nokia DMI was provided with all the Ericsson cmHandles.

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.



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.



4In the forwarded message, cm-handle properties are added by NCMP. Is this just public properties or public and private properties

  • No labels