Page History

...

Interfaces:

1. Mount Request to SDN-R

<node xmlns="urn:TBD:params:xml:ns:yang:network-topology"> 
<node-id>new-netconf-device id</node-id> 
<host xmlns="urn:opendaylight:netconf-node-topology">127.0.0.1</host> 
<port xmlns="urn:opendaylight:netconf-node-topology">17830</port> 
<username xmlns="urn:opendaylight:netconf-node-topology">admin</username> 
<password xmlns="urn:opendaylight:netconf-node-topology">admin</password> 
<tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only> 
</node> 

...

      curl -k --header "Content-Type: application/json" --request GET https://<ip>:30226/events/CM_HANDLE

    4 & 5. Fetch the module sets and yang model and intial config data from SDN-R using RESTConf API (CPS-DMI Plugin takes care of it)

       Yang model: https://<ip>:<port>/restconf/operations/network-topology:network-topology/topology/topology-netconf/node/{node-id}/yang-ext:mount/ietf-netconf-monitoring:get-schema

    6.    Initial-config data: This is not currently supported (as on 01-10-2021). Use the CPS Data APIs to store the initial config data to CPS.

       DMI Plugin should be able to fetch the initial RAN Configuration data as well (not shown in the sequence diagram).

      https://<ip>:<port>/restconf/config/network-topology:network-topology/topology/topology-netconf/node/{node-id}/yang-ext:mount/ran-network:ran-network

Discussion with CPS Team on 28-09-2021: