Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

O-RAN Alliance OpenFronthaul specifications define for O-RU and O-DU management plane traffic the usage of NetConf Notifications.

The message flow in ONAP defines for notifications the VES messages format send to DMaaP VES collector to be forwarded to DMaaP Message Router.

SDN-R should close the gap for NetConf notifications and should make NetConf notification content available in a generic way for all ONAP µServices. Such function was already discussed based on 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-887
. The VES domain "notification" could be used for Configuration Change Notification. However, once 3GPP has agreed on VES 'cmNofity' the now domain should be used.

Related components: Devicemanager cluster bundles

On SDN-R level the NetConf CM Notification Handling mechanism should be combinded with all kind for notfication from SDN-R to other ONAP components. Therefore all the functionality of the VES collector should be used instead of sending directly messaged to DMaaP.

The name of the component is "VES Provider".

Such notifications are:

Related Jiras

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-1187

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-1188


PlantUML Macro
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 
' PlantUML for ONAP/O-RAN Configuration management (NetConf)
'
' Copyright 2020 highstreet technologies GmbH
' Licensed under the Apache License, Version 2.0 (the "License"); 
' you may not use this file except in compliance with the License. 
' You may obtain a copy of the License at 
' 
' http://www.apache.org/licenses/LICENSE-2.0 
' 
' Unless required by applicable law or agreed to in writing, software 
' distributed under the License is distributed on an "AS IS" BASIS, 
' WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
' See the License for the specific language governing permissions and 
' limitations under the License. 
'

@startuml

' Diagram 
title 
  ONAP/O-RAN Configuration management
end title
                          
box “Network” #lightpink
  participant "xNF" as xnf
end box


box "SMO-O1-Controller \n(e.g. ONAP CCSDK/SDNC/SDN-R)" #gold
  participant "NetConf Client" as ncc
  participant "O1-xNF-Adapter \n(e.g. DeviceManager)" as deviceManager
  database "Log or CSP" as log
  participant "VES Provider" as vesProvider
  participant "RestConf Server" as rcs
end box

box "SMO O1-EventCollector \n(e.g. ONAP VES Collector)" #gold
  participant "VES Collector" as vesConsumer
end box

box "SMO MessageBus \n(e.g. ONAP DMaaP)" #gold
  participant "Message Router" as dmaap
end box

box "User space" #lightblue
  actor "SMO µService, rApp \n or OLDUX in browser" as user
end box

autonumber 1 1 "<b>[00]"

== Start the engines ==

xnf <-> ncc: NETCONF\nestablish session\n<hello>
ncc -> deviceManager: Connected! (including yang-capabilities
deviceManager -> deviceManager: IF device supports\n'create-subscription'
ncc <- deviceManager: NETCONF\n<create-subscription>

xnf <- ncc: NETCONF\n<create-subscription>


== Trigger a valid configuration ==

user -> rcs: REST PUT or POST request for xNF
rcs -> ncc: ODL-MDSAL
ncc -> xnf: <edit-config>
xnf -> ncc: <rpc-reply>
ncc -> rcs: ODL-MDSAL
rcs -> user: HTTP RESPONSE

== Related notification flow ==

xnf -> ncc:CM-notification\nNetConf/YANG
ncc -> deviceManager: ODL-MDSAL
deviceManager -> vesProvider: ODL-MDSAL
deviceManager -> log: store event
vesProvider -> vesProvider: convertion/model-translation \n(xml->ves)
vesProvider -> vesConsumer: REST: send VES Message
vesConsumer -> dmaap: REST: Publish event \nunauthenticated.VES_NOTIFICATION_OUTPUT

' End Diagram
' Format
header
  <b><font color=#8888ff>License</font></b>
  <b><font color=#8888ff>Apache 2.0</font></b>
end header

right footer 
  Thanks to plantUml! 
  2020-06-17 | onap.org | o-ran-sc.org
end footer

skinparam backgroundColor #fefefe

skinparam backgroundColor #fefefe
'skinparam handwritten true
skinparam roundcorner 15

skinparam databaseBorderColor #444444
skinparam databaseBackgroundColor #fefefe
skinparam databaseFontColor #444444

skinparam sequence {
  MessageAlign left
  ArrowColor #2277dd
  ArrowFontColor #444444
  ArrowThickness 2
  ActorBorderColor #444444
  LifeLineBorderColor #444444
  LifeLineBackgroundColor #eeeeee
  LifeLineBackgroundColor #eeeeee
 
  BoxBorderColor #444444
    
  GroupBorderColor #444444
  GroupBackgroundColor #eeeeee
  
  ParticipantBorderColor #444444
  ParticipantBackgroundColor #ffffdd
  ParticipantFontColor #444444
    
  ActorBackgroundColor #ffffdd
  'ActorFontColor DeepSkyBlue
  'ActorFontSize 17
  'ActorFontName Aapex
}

@enduml