Date

Attendees

Goals

  • Setup OSC SMO in the lab

Discussion items

Mahesh Jethanandani bhanu chandra  Kiran Ambardekar Santanu De Shrinivas Joshi
TimeItemWhoNotes
5 minAgenda bashingAll


30 min 

D-release 
  • Gerrit commits
  • O1 interface
  • VES interface
  • OSC lab
    • Access to the lab
      • Each of committers should verify access to the lab.
    • Username based on public key shared with Felix.
    • Access to the VM 192.168.130.90
      • Each committer should verify access to the VM
    • Installation of O1 software
    • O-DU access details
      • netconf/netconf! is the username/password
      • ODU VM IP in OSC 192.168.50.190
    • Installation of VES interface 
      • O-RU pnfRegistration event
25 minE-release MVP readout and planning

user-59b16 

user-59b16 opened discussion on E-release. A closed loop automation use-case was discussed for network slicing. Initial thoughts were around configuring a single network slice with parameters and then cause a threshold crossing event. That event is then captured by the VES, and non-RT RIC then issues a correction to the network slicing parameters.

More discussion to follow.

Action items

  • bhanu chandra, Kiran Ambardekar, Santanu and Shrinivas Joshi to send their ssh public keys to Zhe Huang for him to add to all the VMs in the OSC lab.
  • bhanu chandra , Kiran, Santanu and Shrinivas to verify they can still access the OSC lab and VMs in the OSC lab after their ssh keys have been added.
  • Kiran, Santanu and Shrinivas to install the VES software on the SMO VM in OSC lab. 
  • Kiran, Santanu and Shrinivas to verify they can receive pnfRegistration events from O-RU in the lab.
  • Kiran, Santanu and Shrinivas to install O-DU/O-RU simulator and verify all events.
  • bhanu chandra to install O1 software on the SMO VM in the lab.
  • bhanu chandra to verify connectivity to O-DU using the information above. Validate the setup with NETCONF operations to the O-DU.