Page History

Date

08 Jul 2020 16:00 UTC / noon EDT / 18:00 CEST
Zoom: https://zoom.us/j/619914482

Discussion items

Time

Item

Who

Notes

00:00

Admin

Martin Skorupski

Next meeting: 2020-07-15

O-RAN-SC

New Use case: App Life Cycle Management (LCM)

https://wiki.o-ran-sc.org/display/RSAC/1.+Application+LCM+Use+Case

Questions

Could it be related to Kubernetes/Helm?
Could it be related to CSAR (SDC)?
- https://www.opentosca.org/documents/howto-build-csars.pdf
- Csar Structure

PoC

Tracy Van Brakle

PoC end of Sep - more enhanced first week of Dec

5G/LTE-xHaul
OTIC Europe, NA, Asia, India, Israel
Use cases
- multi operator, multi operator - slicing related
- multi-vendor Software Management
- multi-vendor 3GPP aligned services
- CAS, FHGW - see O-RAN Transport WG7 WG4 WG9
- Spectrum Management (DEC)
- Scale/Latency measurement on environments
- O-CU, O-DU
  - TEF, DT

NETCONF-638

Jeff Hartley

-- quick follow up

Info:

NETCONF-638 is confirmed and assigned
Reason for a non-permanent NetConf session:

Self Termination of NetConf Sessions

PlantUML Macro

@startuml
Title Read MOI
autonumber "[0]"
participant "Provisioning MnS Consumer” as NMS
participant "Provisioning MnS Provider" as ME
NMS <-> ME : Establish NETCONF Session
NMS -> ME : NETCONF <rpc> <get><filter>, or NETCONF <rpc> <get-config><source><targetDS><filter>
Note over ME : Retrieve config
ME --> NMS: NETCONF <rpc-reply> <data>
NMS <-> ME : Terminate NETCONF Session
@enduml

Source: O-RAN Specification - O-RAN.WG1.O1-Interface.0-v03.00

O-RAN-SC wiki: https://wiki.o-ran-sc.org/display/OAM/Termination+of+NetConf+Sessions

O-RAN-SC wiki: https://wiki.o-ran-sc.org/display/OAM/Architecture+discussion+for+Non-Permanent+NetConf+Sessions

O-RAN-SC Jira: https://jira.o-ran-sc.org/browse/OAM-1

OpenDaylight Jira: https://jira.opendaylight.org/browse/NETCONF-638

NetConf Session

Thanks Jeff

Process to establish a NetConf session