2021-03-31 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting) - Agenda

Martin Skorupski

Next meetings: 

2021-03-24: John Keeney (Ericsson EST)

2021-03-31: Martin Skorupski

2021-04-06: John Keeney (Ericsson EST)

2021-04-13: Martin Skorupski   - 

Status reports:

• Non-RT-RIC: John Keeney (Ericsson EST) 
  • prototyping for rApps deployment ongoing.... 
  • ONAP H-release - log settings
• SIM: Alex Stancu  
  • CII badging - 
• OAM: Martin Skorupski
  • yet another slack  #ccsdk-sdnc-features
  • Update docker-compose
    • to onap-sdnc:2.1.3 (version from Mar26)
    • to org.onap.dcaegen2.collectors.ves.vescollector:1.9.0
    • to 
  • next steps
    • integration of an identity server
    • update ccsdk to ODL silicon - needed for NETCONF-Call-Home/TLS
    • creation of a use case specific docker-compose with simulated O-RU-Fronthaul and O-DU-hello-world.yang + ves:pnfRegistration (maybe ves:heartbeat, ves:fault) - header VES:7.2.1

Swaminathan Seetharaman

SMO functionality and alignment between ONAP and O-RAN SC

• Swami, John and Martin: slide set was presented 
• There was a meeting between ONAP TSC and ONAP ToC
• 

Q/A

damian.nowak

@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 (Ericsson EST) 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 (Ericsson EST) Seems this use case is not real-world useful, especially since recovery will happen automatically anyway, & mix of standards ...
• Martin Skorupski John Keeney (Ericsson EST) 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 (Ericsson EST) Will use a simple file/hardcoded for initial versions of this use case.
  • Paweł Pawlak Andy Mayer Topology in A&AI, CPS ? John Keeney (Ericsson EST) 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 (Ericsson EST) 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 (Ericsson EST) 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