2021-04-28 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting) - Agenda

Martin Skorupski

Next meetings: 

2021-05-05: John Keeney

2021-05-12: Martin Skorupski

2021-05-19: John Keeney

2021-05-26: Martin Skorupski

Status reports:

• Non-RT-RIC: John Keeney 
• SIM: Alex Stancu 
  • docker images in nexus
    • O-DU (ves:pnfRegistration and ves:fault and hello-world-use-case.yang)
    • O-RU (Callhome (TLS/SSH), OFH yang, NETCONF notification) 
    • NOTE: the capabilities above must be configured as expected by O-RAN Alliance Spec - both SIM are based on the same framework.
    • https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=33292606
      
• OAM: Martin Skorupski
  • new repo created for "nf-oam-adopter"
  • info from CCSDK: ODL version Aluminum SR3 in H-Maintenance

Q/A

@all

OSC Proposed e2e integration use case: O-RU FH connection recovery

• REF/Background:
  • (OAM) Closed loop use case
  • (RSAC) Meeting 14 Jan:
    • Slides: https://wiki.o-ran-sc.org/download/attachments/1179971/RU_failure_recovery_use_case.pptx?version=1&modificationDate=1610637325824&api=v2
    • Recording: https://zoom.us/rec/share/mKYOGkB3mgpvIo2Hx1eY5Oifyw9qV9NQd7NiEj-FxQKP0kUpWOc7yvMO_LLPhA_M.lmx2LCh7-QwDHAFi
• Martin Skorupski provided intro
  • Alarm when fronthaul connection dies (O-DU - O-RU) (VES to SMO)
• John Keeney If there is a failure both O-DU & O-RU will try reconnect anyway - without this loop? Martin Skorupski Yes.
• @? How does SMO connect to O-RU?
  • Martin Skorupski This is a mix of different deployment options (hierarchical vs hybrid, O1 vs M-Plane). Main issue is agreeing models & terminology.
• John Keeney Seems this use case is not real-world useful, especially since recovery will happen automatically anyway, & mix of standards ...
• Martin Skorupski John Keeney Using this use case as longer term motivator for SMO/NONRTRIC/rApp development - independent of usecase
• Topology ??:
  • May need a topology service for this use case - John Keeney Will use a simple file/hardcoded for initial versions of this use case.
  • Paweł Pawlak Andy Mayer Topology in A&AI, CPS ? John Keeney No - not initially. Plan to  keep it simple for this release.

<bridge dropped recording stopped at this point. Most participants reconnected once bridge started again>

• Topology ??: (contd)
  • John Keeney Lots of options for how this should be done properly in ONAP.
  • Swaminathan Seetharaman ONAP usecases already have some plans for this e.g. slicing, oof,  etc
  • Andy Mayer A model should be agreed in ONAP. Lots of previous discussions in ONAP - e.g. what goes in A&AI and CPS ... but that was a while ago.
  • Martin Skorupski SDNR has some topology model too - not standards based.
  • @Sven John Keeney Martin Skorupski Lots of issues with different topology models ... and most existing hierarchical models break down in a 5G/CloudRan environment
  • Lots of work ... Andy Mayer Martin Skorupski Can create a JIRA in ONAP MODCOM ...
  • ... but will keep it simple here for this use case.
• @? Will other O1 usecases be effected? Martin Skorupski i No. O1 functions continue as before.
• Martin Skorupski Please add feedback if any