Skip to end of metadata
Go to start of metadata

 | 9am PDT |  noon EDT | 16:00 UTC | 18:00 CEST | 21:30 IST 


ZOOMhttps://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
Meeting ID: 890 6970 8424

Attendees

Informed

Discussion items

TimeItemWhoNotes
00:00Admin

Next meetings: 

2021-06-30: John Keeney 

2021-07-07: Martin Skorupski

2021-07-14: John Keeney

2021-06-21: Martin Skorupski

00:06Requirement

Requirement discussion from June 20

https://lists.onap.org/g/onap-requirements-sub/message/1985

00:05O-RAN-SCO-RAN-SC PTLs

Status reports:

  • Non-RT-RIC: John Keeney
    • releasing the D-Release - final regression tests
    • deployment in O-RAN-SC Lab
      • link monitor app to be updated
      • feedback by Kamel Idirworks (smile)
        • Non-RT-RIC, OAM, SIM (O-RU, O-DU) 4 CPUs + 16GB → better use 8CPU and 32GB
    • TOC call today
      • next week a vote for release
  • SIM: Alex Stancu
    • as discussed already (smile)
  • OAM: Martin Skorupski
    • Ready to create branch for D-Release
  • O-DU: HariomGupta(HCL)
    • integration into O-DU (high) working fine
    • IPv6 into fully enabled 
    • expectation IPv4 as NetConf end-point working - but is not - HariomGupta(HCL)sending to Martin Skorupski
00:20SMO deployment options

SMO deployment options

  • no tested helm for OAM in O-RAN-SC D-Release - idea update the one from C-release
  • for Non-RT-RIC a new helm is available - still some updates to be done
  • Please see presentation within  REQ-887 - Getting issue details... STATUS

Meeting? on Friday 6/25

https://lists.onap.org/g/onap-meetings/viewevent?repeatid=37969&eventid=1192141&calstart=2021-06-25


Activity

  • kubernetes updates
  • issues with certs addressed
  • reuse of O-RAN-SC helm 
  • Winriver lab


<Martin Skorupski needed to leave. John Keeney continues minutes. See also: 2021-06-23 Meeting notes - Joint OAM / NONRTRIC / SIM SCRUM meeting >

00:48

<End>



END






00:00Use Case

@all

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

<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



Action items