...
This page shows three different SDN-R setup examples and the connectivity to other components.
Single (tiny setup)
For development of in case of small volume without any high availableity capability a singel ODL instance is sufficient.
PlantUML Macro |
---|
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ' Script to convert yang modules into other formats ' Author: martin.skorupski@highstreet-technologies.com ' ' Copyright 2019 higshtreet 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 SDN-R tiny setup Connectivity end title box "Network" #eeeeee participant "<b>PNF00</b>\nnetconf-server" as pnf00 participant "<b>PNF01</b>\nnetconf-server" as pnf01 participant "<b>PNF99</b>\nnetconf-server" as pnf99 end box box "ONAP SDN-R" #ffffff participant "<b>ODL</b>\nnetconf-client" as odl01 end box box "ONAP A&AI" participant "<b>AAI</b>\nhttps-server" as aai01 end box box "ONAP DCAE" participant "<b>VES Collector</b>\nhttps-server" as ves01 end box autonumber "<b>[Con000]" group NetConf\nautomated configuration management pnf00 <-> odl01: tcp/ssh/netconf/830 pnf01 <-> odl01: tcp/ssh/netconf/830 pnf99 <-> odl01: tcp/ssh/netconf/830 end group group sdnr-interfacing-with-dcae odl01 <-> ves01: https:8443 end group group sdnr-interfacing-with-aai odl01 <-> aai01: https:8443 end group ' End Diagram ' Format header <b><font color=#8888ff>License</font></b> <b><font color=#8888ff>Apache 2.0</font></b> end header 'caption "\n UML Formatting" right footer SDN-R tiny Thanks to plantUml! 2019-04-06 | onap.org end footer skinparam backgroundColor #fefefe skinparam backgroundColor #fefefe 'skinparam handwritten true skinparam roundcorner 15 skinparam databaseBorderColor #666666 skinparam databaseBackgroundColor #fefefe skinparam databaseFontColor #666666 skinparam sequence { MessageAlign left ArrowColor #2277dd ArrowFontColor #666666 ActorBorderColor #666666 LifeLineBorderColor #666666 LifeLineBackgroundColor #eeeeee BoxBorderColor #666666 GroupBorderColor #666666 GroupBackgroundColor #eeeeee ParticipantBorderColor #666666 ParticipantBackgroundColor #ffffdd 'ParticipantFontName Impact 'ParticipantFontSize 17 ParticipantFontColor #666666 ActorBackgroundColor #ffffdd 'ActorFontColor DeepSkyBlue 'ActorFontSize 17 'ActorFontName Aapex } @enduml |
OpenDaylight cluster (medium setup)
For production deployment are three node OpenDaylight cluster should cover most of the use cases.
PlantUML Macro |
---|
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ' Script to convert yang modules into other formats ' Author: martin.skorupski@highstreet-technologies.com ' ' Copyright 2019 higshtreet 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 SDN-R medium setup Connectivity end title box "Network" #eeeeee participant "<b>PNF00000</b>\nnetconf-server\nhttps-server" as pnf00000 participant "<b>PNF00001</b>\nnetconf-server\nhttps-server" as pnf00001 participant "<b>PNF99999</b>\nnetconf-server\nhttps-server" as pnf99999 end box box "ONAP SDN-R" #ffffff participant "<b>ODL01</b>\nnetconf-client" as odl01 participant "<b>ODL02</b>\nnetconf-client" as odl02 participant "<b>ODL03</b>\nnetconf-client" as odl03 participant "<b>Admin01</b>\nhttps-client" as admin01 participant "db01" as db01 participant "db02" as db02 end box box "ONAP A&AI" participant "<b>AAI-01</b>\nhttps-server" as aai01 participant "AAI-02" as aai02 end box box "ONAP DCAE" participant "<b>VES-01 Collector</b>\nhttps-server" as ves01 participant "DMaaP" as dmaap01 participant "DCAE Servers" as dcae01 end box autonumber "<b>[Con000]" group NetConf\nautomated configuration management pnf00000 <-> odl01 : tcp/ssh/netconf/830 \n<b>currently active pnf00001 <--> odl01: tcp/ssh/netconf/830 \npossible pnf99999 <--> odl01: tcp/ssh/netconf/830 \npossible pnf00000 <--> odl02: tcp/ssh/netconf/830 \npossible pnf00001 <--> odl02: tcp/ssh/netconf/830 \npossible pnf99999 <-> odl02 : tcp/ssh/netconf/830 \n<b>currently active pnf00000 <--> odl03: tcp/ssh/netconf/830 \npossible pnf00001 <-> odl03 : tcp/ssh/netconf/830 \n<b>currently active pnf99999 <--> odl03: tcp/ssh/netconf/830 \npossible end group group sdnr-interfacing-with-dcae odl01 <-> ves01: https:8443 odl02 <-> ves01: https:8443 odl03 <-> ves01: https:8443 end group group sdnr-interfacing-with-aai odl01 <-> aai01: https:8443 odl02 <-> aai01: https:8443 odl03 <-> aai01: https:8443 end group group cluster synchronization odl01 <-> odl02: odl-synch tcp/2550 odl01 <-> odl02: es-synch tcp/9300 odl02 <-> odl03: odl-synch tcp/2550 odl02 <-> odl03: es-synch tcp/9300 odl03 <-> odl01: odl-synch tcp/2550 odl03 <-> odl01: es-synch tcp/9300 db01 <-> db02: synch tcp/3306 aai01 <-> aai02: synch tcp/9300 end group group Notification to http clients by webSocekts note right of odl01 #3399ff <font color=#ffffff><b>Notification towards northbound of ODL are <font color=#ffffff><b>provided via WebSockets. Notification from PNFs <font color=#ffffff><b>are available via port 8443. <font color=#ffffff><b>Notifications from ODL internal databse MDSAL are <font color=#ffffff><b>available via port 8185. end note admin01 <- odl01: ws/8185 (md-sal) admin01 <- odl02: ws/8185 (md-sal) admin01 <- odl03: ws/8185 (md-sal) end group group https gui-cut-through\nmanual configuration management admin01 <-> odl01: https:8443 pnf00000 <-> odl01: https:443 pnf00001 <-> odl01: https:443 pnf99999 <-> odl01: https:443 admin01 <-> odl02: https:8443 pnf00000 <-> odl02: https:443 pnf00001 <-> odl02: https:443 pnf99999 <-> odl02: https:443 admin01 <-> odl03: https:8443 pnf00000 <-> odl03: https:443 pnf00001 <-> odl03: https:443 pnf99999 <-> odl03: https:443 end group ' End Diagram ' Format header <b><font color=#8888ff>License</font></b> <b><font color=#8888ff>Apache 2.0</font></b> endheader 'caption "\n UML Formatting" right footer SDN-R Medium Thanks to plantUml! 2019-04-06 | onap.org end footer skinparam backgroundColor #fefefe skinparam backgroundColor #fefefe 'skinparam handwritten true skinparam roundcorner 15 skinparam databaseBorderColor #666666 skinparam databaseBackgroundColor #fefefe skinparam databaseFontColor #666666 skinparam sequence { MessageAlign left ArrowColor #2277dd ArrowFontColor #666666 ActorBorderColor #666666 LifeLineBorderColor #666666 LifeLineBackgroundColor #eeeeee BoxBorderColor #666666 GroupBorderColor #666666 GroupBackgroundColor #eeeeee ParticipantBorderColor #666666 ParticipantBackgroundColor #ffffdd 'ParticipantFontName Impact 'ParticipantFontSize 17 ParticipantFontColor #666666 ActorBackgroundColor #ffffdd 'ActorFontColor DeepSkyBlue 'ActorFontSize 17 'ActorFontName Aapex } @enduml |
Geo-Redundancy (full setup)
Based on use-cases and high availability requirements a geo-redundant setup with 2x 3 node local OpenDaylight cluster is shown in the figure below.
...