Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Date

Attendees

Notes

This was our first meeting using the ONAP bridge

1. ONAP Wiki for OOF-PCI use case documentation.
Main wiki page continues to be the same:
https://wiki.onap.org/display/DW/5G+-+OOF+%28ONAP+Optimization+Framework%29+and+PCI+%28Physical+Cell+ID%29+Optimization
There are child pages for different parts of the work.

There is link to this page from the main "Casablance 5G Use Case" page which is also the file repository.
https://wiki.onap.org/display/DW/5G+Use+case+Items

2. ConfigDB schema and API Spec exposed by SDN-R to OOF and PCI Handler MS (PCIHMS).
Devendra is working on API Spec translating previous MySQL based spec to MariaDB based spec. API spec will be uploaded to Wiki. We need to finalize this by 9/5 so that SDN-C PTL can process a CR

Decisions:
objects in configDB: cell, pnf
cell object: add pnf-name
pnf object: add cells (list of cellIds)
pnf:cellId is 1:N relationship

configdB API:
modify get nbrlist to incude pci value in response
add get pnf-name to api (in response to cellid)

See: https://wiki.onap.org/display/DW/SDN-R%3A+Impacts+and+Interface+aspects

3. Yang model

Sandeep is going to study and come back with Yang model for the use case. This will build on SDN-R yang model.
Note that cellID needs to be globally unique. Suggestion to use eCGI.
Need to be aligned to 3GPP and ORAN.
See: https://wiki.onap.org/download/attachments/28382769/onap-sdnr-modelling.zip?api=v2

4. Policy Module code changes for OOF-PCI:
Plan for code changes was presented in 8/29 Policy call.
See: https://wiki.onap.org/display/DW/Policy%3A+Impacts+and+interface+aspects

Plan: Swami/Saravanan will be submitting code changes by 9/7

5. PCI MS: Microservice design doc will be uploaded to Wiki.

6. RAN Simulator:
Decision has been made to use the Honeycomb netconf server.
Note that since one pnf has one netconf server and one pnf can support multiple cells, the number of netconf servers is reduced for the target of 2000 cells.

7. Dublin release:
5G Use Case team already has wiki page for Dublin plans.
We could consider following (need feedback):
- extension of PCI use case: include data from DCAE (PM/FM KPIs?) and triggers from SO/AAI (new cell addition) and FM alarms.
- onboard PCIHMS to DCAE
- build out interface and sync between AAI and configDB
- add other SON function such as ANR (joint optimization?) or others which can be used to test the CLC function in Policy for SON coordination.

This was our first meeting using the ONAP bridge
Attendees:N. K. ShankarSwaminathanSaravananSandeepTracy Van BrakleDilip KrishnaswamyKrishna moorthySeshuVikas VarmaSlawek StawiarskiGeorge ClappFerri TafreshiCarlos de AndradeMehmet Toy
(others please add .. I do not have a complete list)
1. ONAP Wiki for OOF-PCI use case documentation.Main wiki page continues to be the same:https://wiki.onap.org/display/DW/5G+-+OOF+%28ONAP+Optimization+Framework%29+and+PCI+%28Physical+Cell+ID%29+Optimization There are child pages for different parts of the work.
There is link to this page from the main "Casablance 5G Use Case" page which is also the file repository.https://wiki.onap.org/display/DW/5G+Use+case+Items
2. ConfigDB schema and API Spec exposed by SDN-R to OOF and PCI Handler MS (PCIHMS). Devendra is working on API Spec translating previous MySQL based spec to MariaDB based spec. API spec will be uploaded to Wiki. We need to finalize this by 9/5 so that SDN-C PTL can process a CR
Decisions:objects in configDB: cell, pnfcell object: add pnf-namepnf object: add cells (list of cellIds)pnf:cellId is 1:N relationship
configdB API:modify get nbrlist to incude pci value in responseadd get pnf-name to api (in response to cellid)
See: https://wiki.onap.org/display/DW/SDN-R%3A+Impacts+and+Interface+aspects
3. Yang model
Sandeep is going to study and come back with Yang model for the use case. This will build on SDN-R yang model. Note that cellID needs to be globally unique. Suggestion to use eCGI.Need to be aligned to 3GPP and ORAN.See: https://wiki.onap.org/download/attachments/28382769/onap-sdnr-modelling.zip?api=v2 
4. Policy Module code changes for OOF-PCI:Plan for code changes was presented in 8/29 Policy call.See: https://wiki.onap.org/display/DW/Policy%3A+Impacts+and+interface+aspects
Plan: Swami/Saravanan will be submitting code changes by 9/7
5. PCI MS: Microservice design doc will be uploaded to Wiki.
6. RAN Simulator:Decision has been made to use the Honeycomb netconf server.Note that since one pnf has one netconf server and one pnf can support multiple cells, the number of netconf servers is reduced for the target of 2000 cells.
7. Dublin release:5G Use Case team already has wiki page for Dublin plans.We could consider following (need feedback):- extension of PCI use case: include data from DCAE (PM/FM KPIs?) and triggers from SO/AAI (new cell addition) and FM alarms.- onboard PCIHMS to DCAE- build out interface and sync between AAI and configDB- add other SON function such as ANR (joint optimization?) or others which can be used to test the CLC function in Policy for SON coordination.

  • No labels