This document captures the high-level design implemented for the OOFPCI POC use case and SDNR DMaaP Listener/Consumer and RPC/DG execution (based on the contents of the DMAAP message received).

To support closed-loop-automation use cases, such as SON, SDNR:

  • Receives DMAAP message from pertinent ONAP components (such as, Policy/OOF) and micro-services (such as, SON MS)
  • Invokes corresponding RPC's/DG's that implement the logic to accomplish the requested action (such as, add neighbors to a cell, configure PCI value of a cell...)
  • Sends confirmation back to Policy and other components, about success or failure of the requested action

The below diagram depicts high-level design/architecture:

All technical details associated with creating DMAAP listener docker for SDNR are included here.

All technical details associated with Directed Graphs for YANG/RPC execution are included here.

Key Prerequisites and requirements:

  • YANG models that capture configuration tree and RPC's are defined
  • DMAAP message payloads are aligned with YANG models



  • No labels

3 Comments

  1. Herbert Eiselt

    In oofpcipoc-consumer the onNbrlistChangeNotification() processes the "RAN Neighbor List change notification" and forwards to "http://sdnc.onap:8282/restconf/operations".  Which service is behind "sdnc.onap:8282"?

  2. Herbert Eiselt

    features-aggregator

    • contains: provider
    • does not consider consumer

    installer: contains: consumer, provider and dependencies

    model: Specifies rpc api

    consumer 

    • depends on provider, model
    • not part of the feature-aggragator 
    • depends on provider, model

    provider 

    • depends on model, ccsdk.sli
    • Main class1: oofpciClient
      • Wraps SvcLogicService: Processing/executing "graphs" → returning Properties
    • Main class2: oofpciProvider
      • owns as attribute "oofpciClient" service
      • Registers oofpcipocApiService (RestconfAPI)
      • Processes RPC commands, using "oofpciClient" 
    • Instance for both classes started as bean. oofpciProvider gets oofpciClient instance
    • Part of feature

  3. Sandeep Shah

    Hi Herbert - just an fyi...You are referring to the consumer/provider code associated with Netconf Notification associated with nbr list change notification...we have merged the code; however, it is not yet part of oofpcipoc karaf feature....Thanks!