Versions Compared

Key

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

Table of Contents
7

This page is related to Jira

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyONAPMODEL-35


Motivaton

Based on discussion between ONAP and O-RAN-SC there is a need to provide a common model to µServices with respect to (network) topologies.

In previous proof-of concept and demonstrations several different topologies of different types were presented. Such use-case driven topologies have several "things" in common.  For multi topology networks based on virtual and physical network functions a view across technologies is required to optimize the network in terms of utilization and/or latency and other criteria's. 


Use case driven topology representations

Geographical Topology

Physical Topology

Ethernet Topology

PTP-Topology


Idea

The idea could be to define an ONAP topology model across all ONAP components and technologies and describe a kind of mapping to technology and/or use case specific topology models, such as:

  • PCEP
  • LLDP
  • IEEE 802.3
  • TAPI
  • OpenROADM
  • 3GPP-EP
  • IETF-Interfaces
  • ONF:LogicalTerminationPoints
  • OpenConfig
  • ...


Initial draft proposal

PlantUML Macro
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 
' Copyright 2021 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 
  Abstract Topology Model
end title


package To-interfaces {
  interface Top {
    UUID Identifier
    String Name
    String Label
    ENUM LifeCycleState
	ENUM OperationalState
	ENUM AdminstrativeSTate
  }
  interface Topology implements Top
  interface Node implements Top
  interface Edge implements Top
  interface Path implements Top
}


Topology *--> "*" Node: hasNodes
Topology *--> "*" Edge: hasEdges
Topology *--> "*" Path: hasPaths
Node *--> "*" Node: hasChildren
Node *--> "*" Node: hasNeighborsOfSameType
Edge *--> "*" Edge: hasChildren
Edge "1" o-left-> "2" Node: refrencesNodesOfSameType
Path "1" o-right-> "*" Edge: referencesLinks


' 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! 
  2021-01-29 | onap.org
end footer

skinparam backgroundColor #fefefe

skinparam backgroundColor #fefefe
'skinparam handwritten true
skinparam roundcorner 15

skinparam class {
  BorderColor #444444
  BackgroundColor #ffffdd
  FontColor #444444
}

skinparam database {
  BorderColor #444444
  BackgroundColor #ffffdd
  FontColor #444444
}

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