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 availability capability a single ODL instance is sufficient. SDN-R tiny setupConnectivity Network ONAP SDN-R ONAP A&AI ONAP DCAE PNF00netconf-server PNF00netconf-server PNF01netconf-server PNF01netconf-server PNF99netconf-server PNF99netconf-server ODLnetconf-client ODLnetconf-client AAIhttps-server AAIhttps-server VES Collectorhttps-server VES Collectorhttps-server NetConfautomated configuration management [Con001]tcp/ssh/netconf/830 [Con002]tcp/ssh/netconf/830 [Con003]tcp/ssh/netconf/830 sdnr-interfacing-with-dcae [Con004]https:8443 sdnr-interfacing-with-aai [Con005]https:8443LicenseApache 2.0SDN-R tinyThanks to plantUml!2019-04-06 | onap.org


OpenDaylight cluster (medium setup)

For production deployment are three node OpenDaylight cluster should cover most of the use cases. SDN-R medium setupConnectivity Network ONAP SDN-R ONAP A&AI ONAP DCAE PNF00000netconf-serverhttps-server PNF00000netconf-serverhttps-server PNF00001netconf-serverhttps-server PNF00001netconf-serverhttps-server PNF99999netconf-serverhttps-server PNF99999netconf-serverhttps-server ODL01netconf-client ODL01netconf-client ODL02netconf-client ODL02netconf-client ODL03netconf-client ODL03netconf-client Admin01https-client Admin01https-client db01 db01 db02 db02 AAI-01https-server AAI-01https-server AAI-02 AAI-02 VES-01 Collectorhttps-server VES-01 Collectorhttps-server DMaaP DMaaP DCAE Servers DCAE Servers NetConfautomated configuration management [Con001]tcp/ssh/netconf/830currently active [Con002]tcp/ssh/netconf/830possible [Con003]tcp/ssh/netconf/830possible [Con004]tcp/ssh/netconf/830possible [Con005]tcp/ssh/netconf/830possible [Con006]tcp/ssh/netconf/830currently active [Con007]tcp/ssh/netconf/830possible [Con008]tcp/ssh/netconf/830currently active [Con009]tcp/ssh/netconf/830possible sdnr-interfacing-with-dcae [Con010]https:8443 [Con011]https:8443 [Con012]https:8443 sdnr-interfacing-with-aai [Con013]https:8443 [Con014]https:8443 [Con015]https:8443 cluster synchronization [Con016]odl-synch tcp/2550 [Con017]es-synch tcp/9300 [Con018]odl-synch tcp/2550 [Con019]es-synch tcp/9300 [Con020]odl-synch tcp/2550 [Con021]es-synch tcp/9300 [Con022]synch tcp/3306 [Con023]synch tcp/9300 Notification to http clients by webSocekts Notification towards northbound of ODL areprovided via WebSockets. Notification from PNFsare available via port 8443.Notifications from ODL internal databse MDSAL areavailable via port 8185. [Con024]ws/8185 (md-sal) [Con025]ws/8185 (md-sal) [Con026]ws/8185 (md-sal) https gui-cut-throughmanual configuration management [Con027]https:8443 [Con028]https:443 [Con029]https:443 [Con030]https:443 [Con031]https:8443 [Con032]https:443 [Con033]https:443 [Con034]https:443 [Con035]https:8443 [Con036]https:443 [Con037]https:443 [Con038]https:443LicenseApache 2.0SDN-R MediumThanks to plantUml!2019-04-06 | onap.org

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.

The example propose a separate log server for each local instance of SDN-R. SDN-R full setupConnectivity Network ONAP SDN-R Geo01 ONAP A&AI Geo01 ONAP DCAE Geo01 ONAP SDN-R Geo02 ONAP A&AI Geo02 ONAP DCAE Geo02 PNF00000netconf-serverhttps-server PNF00000netconf-serverhttps-server PNF00001netconf-serverhttps-server PNF00001netconf-serverhttps-server PNF99999netconf-serverhttps-server PNF99999netconf-serverhttps-server ODL11netconf-client ODL11netconf-client ODL12netconf-client ODL12netconf-client ODL13netconf-client ODL13netconf-client Admin11https-client Admin11https-client Admin12https-client Admin12https-client db11 db11 db12 db12 log11 log11 AAI-11https-server AAI-11https-server AAI-12 AAI-12 VES-11 Collectorhttps-server VES-11 Collectorhttps-server DMaaP DMaaP DCAE Servers DCAE Servers ODL21netconf-client ODL21netconf-client ODL22netconf-client ODL22netconf-client ODL23netconf-client ODL23netconf-client Admin21https-client Admin21https-client Admin22https-client Admin22https-client db21 db21 db22 db22 log21 log21 AAI-21https-server AAI-21https-server AAI-22 AAI-22 VES-21 Collectorhttps-server VES-21 Collectorhttps-server DMaaP DMaaP DCAE Servers DCAE Servers NetConfautomated configuration management [Con001]tcp/ssh/netconf/830currently active [Con002]tcp/ssh/netconf/830possible [Con003]tcp/ssh/netconf/830possible [Con004]tcp/ssh/netconf/830possible [Con005]tcp/ssh/netconf/830possible [Con006]tcp/ssh/netconf/830currently active [Con007]tcp/ssh/netconf/830possible [Con008]tcp/ssh/netconf/830currently active [Con009]tcp/ssh/netconf/830possible [Con010]tcp/ssh/netconf/830possible [Con011]tcp/ssh/netconf/830possible [Con012]tcp/ssh/netconf/830possible [Con013]tcp/ssh/netconf/830possible [Con014]tcp/ssh/netconf/830possible [Con015]tcp/ssh/netconf/830possible [Con016]tcp/ssh/netconf/830possible [Con017]tcp/ssh/netconf/830possible [Con018]tcp/ssh/netconf/830possible sdnr-interfacing-with-dcae [Con019]https:8443 [Con020]https:8443 [Con021]https:8443 [Con022]https:8443 [Con023]https:8443 [Con024]https:8443 sdnr-interfacing-with-aai [Con025]https:8443 [Con026]https:8443 [Con027]https:8443 [Con028]https:8443 [Con029]https:8443 [Con030]https:8443 cluster synchronization [Con031]odl-synch tcp/2550 [Con032]es-synch tcp/9300 [Con033]odl-synch tcp/2550 [Con034]es-synch tcp/9300 [Con035]odl-synch tcp/2550 [Con036]es-synch tcp/9300 [Con037]odl-synch tcp/2550 [Con038]es-synch tcp/9300 [Con039]odl-synch tcp/2550 [Con040]es-synch tcp/9300 [Con041]odl-synch tcp/2550 [Con042]es-synch tcp/9300 [Con043]odl-synch tcp/2550 [Con044]es-synch tcp/9300 [Con045]odl-synch tcp/2550 [Con046]es-synch tcp/9300 [Con047]odl-synch tcp/2550 [Con048]es-synch tcp/9300 [Con049]odl-synch tcp/2550 [Con050]es-synch tcp/9300 [Con051]odl-synch tcp/2550 [Con052]es-synch tcp/9300 [Con053]odl-synch tcp/2550 [Con054]es-synch tcp/9300 [Con055]odl-synch tcp/2550 [Con056]es-synch tcp/9300 [Con057]odl-synch tcp/2550 [Con058]es-synch tcp/9300 [Con059]odl-synch tcp/2550 [Con060]es-synch tcp/9300 [Con061]synch-port tcp/3306 [Con062]synch-port tcp/3306 [Con063]synch-port tcp/3306 [Con064]synch-port tcp/3306 [Con065]synch-port tcp/3306 [Con066]synch-port tcp/3306 [Con067]synch tcp/9300 [Con068]synch tcp/9300 [Con069]synch tcp/9300 [Con070]synch tcp/9300 [Con071]synch tcp/9300 [Con072]synch tcp/9300 Notification to http clients by webSocekts Notification towards northbound of ODL areprovided via WebSockets. Notification from PNFsare available via port 8443.Notifications from ODL internal databse MD-SAL areavailable via port 8185. [Con073]ws/8185 (md-sal) [Con074]ws/8443 (ux-frame) [Con075]ws/8185 (md-sal) [Con076]ws/8443 (ux-frame) [Con077]ws/8185 (md-sal) [Con078]ws/8443 (ux-frame) [Con079]ws/8185 (md-sal) [Con080]ws/8443 (ux-frame) [Con081]ws/8185 (md-sal) [Con082]ws/8443 (ux-frame) [Con083]ws/8185 (md-sal) [Con084]ws/8443 (ux-frame) https gui-cut-throughmanual configuration management [Con085]https:8443 [Con086]https:8443 [Con087]https:443 [Con088]https:443 [Con089]https:443 [Con090]https:8443 [Con091]https:8443 [Con092]https:443 [Con093]https:443 [Con094]https:443 [Con095]https:8443 [Con096]https:8443 [Con097]https:443 [Con098]https:443 [Con099]https:443LicenseApache 2.0SDN-R fullThanks to plantUml!2019-04-06 | onap.org

Abbreviations

  • PNF Physical network function
  • VNF Virtual network function
  • XNF Physical or virtual network function
  • No labels