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

Compare with Current View Page History

« Previous Version 3 Next »

References

Assumptions

Issues & Decisions

#IssueNotesDecisions
1What dataspace and anchor to use?
Dataspace: NCMP-Admin  Anchor: AVC-Subscriptions
2How do we load the data ( not using cps-core / not using Liquibase )?

Options

  1. Liquibase steps in CPS-Core (not preferred, adds to Technical Debt)
  2. Add Liquibase to NCMP (possible but would make NMCP install aware/dependent on Postgres)
  3. Startup Hooks that trigger CPS-Admin (rest or Java) interface calls
    1. Helm 
    2. Springboot

Need to discuss with stakeholders re. Priority and Cost

3

Predicate details are unclear at the moment. Which component(s) processes the predicates?! Device, DMI-Plugin and or NCMP


Predicate Example 
"datastore": “passthrough-operational",  (O)
                "datastore-xpath-filter" : "//_3gpp-nr-nrm-nbdufunction: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//”

Contact kieran mccarthy to clarify this (Tony assumed predicates were NOT for NCMP)

Background

NCMP wil need to store which subscriptions are current for each cm-handle

  • Dataspace: NCMP-Admin (existing)
  • Anchor: AVC-Subscriptions (new)
  • Top level list Container?! (if need wrap in a top-level container)
    • CONTAINER: subscription-registry
      • LIST: subscription[@clientId=AppB and @name=mySubscription]
        • LEAF: clientId (leaf)
        • LEAF: name
        • LEAF: topic
        • LEAF: isTagged

YANG model

The following yang model will be used to store the payload information of subscription data

  • No labels