Page Comparison

DEC plugfest: https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=7274618 https://lf-onap.atlassian.net/wiki/display/DW/Week+2019+Dec+2nd

Report from O-RAN SC meeting last week 

• ONAP 5G use case implementation and O-RAN SC O1 interface implementations depend on O-RAN Alliance data models (YANG, VES).
• O-RAN Alliance data models bases on 3GPP specs and data models.
• A more efficient communication channel between all parties will be defined.
• There is the idea (not mine!) to discuss, specify, and publish VES in O-RAN-SC - to align 3GPP, O-RAN Alliance, O-RAN-SC, ONAP and others.
• My personal(!) expectations: This will take time and officially released 3GPP and O-RAN alliance may not make it before API feeze of Guilin. Of cause I hope of surprises. There are delegates in O-RAN Alliance working against my personal expiation - ONAP SDN-R and O-RAN-SC OAM are supporting such efforts as much as they can.

I got the following Action Item from RunTime Config DB Meeting notes Feb 21, 2019
Further infos: RunTime Config DB (Data Persistency Service(?))Project Proposal (Oct 25 2019)Configuration Persistence Service Project

Convert yang model in SDN-R to be used into CCSDK. RTCfgDB will be used for OOF/SON/PCI first. Yang model as used by OOF/SON/PCI to convert. Yang model from SDN-R > CCSDK. SDN-C gets yang model from SDC. Yang to SQL. Need to have 1 Yang model.

In order to convert yang files, we need to know more about the target format of the conversion. We would prefer a document explaining the mapping details from YANG to SQL and from SQL to YANG. An easy way of the conversion is to translate YANG to its xml representation YIN and then group them in a single xml file with a xml-warpper tag. An example attached.

One yang as requested does not scale, due to the dynamics when new devices are connected to SDN-R exposing new yang models.