2021-08-16 Meeting notes

8/9: SON use case weekly calls moved to Mondays as discussed:

https://lists.onap.org/g/onap-meetings/viewevent?repeatid=32219&eventid=1236181&calstart=2021-08-09
Will keep it short to 25 minutes on days when we have Use Case call at 9am EDT (alternate weeks)

7/30
Proposal for SDNR work to have flexibility in using old and new apis for ConfigDB/CPS DB.
Consensus that this approach makes sense.

https://jira.onap.org/browse/CCSDK-3401
 
https://gerrit.onap.org/r/c/ccsdk/distribution/+/122981

7/30
PM message format options. Slicing use case uses the file-based approach. Intent is to
leverage commonality among use cases. Will follow up with Ahila.

8/16

Please see email chain about CM format. SON use case can change formats since it is generated

from RAN-Sim. Need to ensure that DCAE VES collector can support the O1-aligned CM message.

8/9

Would like to have coordination of actions over A-1 and O-1.

Question. How can ONAP components can invoke and use A-1 Adapter.

DMaaP message on A1-P topic did not work with work done for Slicing use case.

Follow up with Dan Timoney about how components in ONAP can talk to A-1 adapter.

8/16

Shankar presented factors involved in determining role of A1 in ONAP-SON use case. Good discussion.

ONAP-SON use case has done a lot of work with O1 interface. We are discussing what is the right way

to add A1 interface. Important to identify the SON function which is suitable for A1 (assuming some abstraction

of A1-xApp-E2 flow). Current thoughts around handoff and neighbor relations as it relates to our work in PCI and ANR.

8/16

Ongoing: Functional testing going on for RAN-Sim. Switching to VES 7.2

Ongoing: Migration from ConfigDB to CPS for SON-Handler. Need to finalize xPath templates.