2019-08-21 Meeting notes (SDN-R)

Owned by Martin Skorupski
Last updated: Aug 21, 2019
1 min read

Date

Aug 21, 2019

Attendees

  • @Dongho Kim

  • @Jeff Hartley

  • @Martin Skorupski

  • @Sandeep Shah

  • @John Keeney

  • @shashikanth.vh

    Please add yourself. Thanks!

Informed

  • @alexander.dehn

  • @George Clapp

  • @Herbert Eiselt

  • @Latha Ramamurthy

  • @Tracy Van Brakle

Goals

  • Share information

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

15min

CDS

@Martin Skorupski

CDS - Controller Design Studio useful links by Dongho (thanks)

AI: Invite PTL of CDS for the next meeting ...

10min

Info

@Martin Skorupski

ONAP/O-RAN-SC Plugfest

  • first week from December in Seoul

  • it will be an O-RAN-SC event 

Use cases

1. PNF PnP

  • VES message: pnfRegsitration

  • ONAP most of the ONAP components.  


2. PM Bulk (file)

  • VES message for "File Ready"

  • PM upload via SFTP

3. Basic fault

  • existing VES domain "fault" to be used.

4. Basic config Config via NetConf, updated to the controller via VES. 
-- WG4 O-RU, FH (M-Plane) - NetConf Notification -> ONAP model-driven DMaaP Agent (notification)
-- WG5 O-DU, VES message from the beginning - O1 -Architecture.

5. OOF-SON -> Sandeep Shah was pushed to Release B

- VES Notifications

Objective


The objective is showing O1 interface between ONAP and real equipment.

In OWL is equipment available from NEC, AltioStar, Huawei and software-defined radios, which could be used. 

Under discussion the support of real equipment integrated via DT-Could in Prag (e.g. ZTE) and OSNL. (see June demo)

15min

ConfigDB

@Sandeep Shah

ConfigDB

  • The first implementation was done for OOF PCI PoC

  • SDN-R was updating ConfigDB to support other ONAP components

  • There is a discussion started about the modeling of the data stored in ConfigDB

  • Another discussion may end in creating a new ONAP project of ConfigDB.


Action items