comTable of Contents

Scope

For security and organizational reasons it might be necessary to define several virtual networks, when deploying an ONAP/SMO solution.

The following with network setup is just an example and is used of demonstration purposes.

Please note that this setup is different form the OOM Kubernetes setup, by intention. it is just simpler but has its limitations. For production purposes, please follow the latest setup of the OOM project.  

Networks

DMZ

A logical subnetwork that contains and exposes external services to an untrusted network, such as the internet. 

SMO

A logical subnetwork that contains internal services. This network is considered as trusted.

OAM

A logical subnetwork that contains and exposes external services to network functions. 

Diagram

LicenseApache 2.0Use case NetworksDMZ172.30.0.0/16SMO172.40.0.0/162001:db8:1:1::/64OAM172.50.0.0/162001:db8:1:1::/64 gateway10G-1 gateway10G-2 identity10G-1 topology10G-1 dmaap10G-1 sdnrdb10G-1 sdnr10G-1 sdnr100G-2 ves-collector10G-1 ves-collector100G-2 InternetOther ServciesDNS; DHCP; NTP; Acumosetc        ManagementSwitches    Gateway   Identity     Topology   DMaaP     SDN-R-DB   SDN-R        VES-Collector       OAM Switch Network FunctionscNF; vNF; pNF; etcThanks to plantUml!2021-04-06 | onap.org

Example Telecommunication Network 

The following network is used for the following purposes:

  • Deployment 
  • Day0 Configuration
  • Day1 Configuration
  • End-2-End Integration tests

SVG

JSON


  • No labels