2023-10-17 Meeting notes

Owned by N.K. Shankaranarayanan
Last updated: Oct 17, 2023
2 min read

Date

Oct 17, 2023

Attendees

  • @N.K. Shankaranarayanan

  • @Priyank Maheshwari

  • @murali parthasarathy k 

  • @kieran mccarthy 

  • @Kolawole Adebisi-Adeolokun 

Recording:

Agenda

  • Status update

  • Discussion of CM Flow 



Notes:

Update: Priyank, Vishal, Murali are meeting regularly. Vishal team to deploy the latest CPS codebase to have full CM update implementation.

CM Flow: Shankar created sequence flow diagram for CM Update. Great discussion from team to update and improve accuracy of flow.

See Config Management (CM) Sequence Flow - Developer Wiki - Confluence (onap.org)



-- notes from previous mtgs --

VES message example: See CPS-1434: VES Message to update CPS DB 

API call example:
/rests/data/network-topology:network-topology/topology=topology-netconf/node=nearrtric-22_cucpserver2/yang-ext:mount/ietf-netconf-monitoring:netconf-state/schemas

payload: {"ietf-netconf-monitoring:input":{"identifier":"ran-network"}}



Files for yang model and initial config (same as RAN-Sim) used within CPS for testing: 

cps-ran-schema-model@2021-05-19.yang

cps-ran-schema-model-data-v4.json

--

 Flow from Priyank  

1. DMI Plugin /v1/inventory/cmHandles - call the internal API to register the cmhandles    

2. /ncmpInventory/v1/ch - NCMP API is invoked and cmHandle persisted in ADVISED state    

3. ModuleSyncWatchdog kicks in and syncs the schemaset and anchor    

4. Call the /dmi/v1/modules to get the list of Module references --> this internally call SDNC    

5. Return all the list of modules to NCMP    

6. Find if there are any new modules by looking at the Cps Database.    

7. If there are any new , again call the DMI Plugin to get the moduleResources. /dmi/v1/moduleResources    

8. Persist the newly received moduleResources

--



Control Flow:

Initial state before step 1: SDN-R has mounted netconf devices (NFs) and has yang models. CPS DB does not have this info.

Steps 1-8:

SDN-R calls DMI Plug-in, registers list of cmHandleIds (typically same as netconf server name or nodeId)

DMI Plug-in does internal updates, then calls SDN-R to get schema information

APIs are used by SDN-R to load initial instance of CU and DU NFs and properties

Final state after step 8: 

CPS DB is initialized with all info in RAN-Sim. 
DMI Plug-in is ready to process a VES msg for CM update, with assumption that VES msg has a sourceId which is same as cmHandleId.



See CPS documentation .. https://docs.onap.org/projects/onap-cps/en/latest/overview.html