OAM Integration Solution

Table of Contents

Scope

This page gives references to the docker-compose solution of the OAM deployment.

Network

The following network diagram represents a structured view of various network segments within a system, emphasizing boundaries and key nodes for access and communication.

At the perimeter, there is the Internet, symbolized by a cloud, which connects into a DMZ (Demilitarized Zone) network. The DMZ is marked by blue coloring and is designated to handle traffic addressed to a domain matching *.smo.o-ran-sc.org. Inside this zone, there's a gateway component labeled "traefik" with a 10G-1 interface, depicted with cog icons to suggest control or routing functionality. This gateway serves as the bridge between the public internet and the internal networks.

The SMO (Service Management and Orchestration) domain is rendered in a golden-yellow tone and is divided into two blocks—likely reflecting logical or physical separation within the same broader system. One part includes user-facing components like a controller UI (odlux), Kafka UI, and InfluxDB UI, suggesting this side focuses on system interaction and monitoring interfaces. There's also an element called rAppPM, likely related to performance management applications, and a hexagonal "extend" node, which might indicate expandable or modular design.

The other SMO block focuses on backend infrastructure. It includes a second gateway ("10G-2") and an identity provider (Keycloak on "10G-1"), suggesting authentication and authorization services. Other elements like Kafka (messages), a controller, a VES collector, and a Data File Collector (DFC) represent the core processing, message brokering, monitoring, and data handling functions of the orchestration system. Another "extend" node appears, hinting at further integration or modules.

Moving deeper into the architecture, the DCN (Data Center Network) is shown with a semi-transparent red color. It mirrors some SMO components (controller, VES collector, Data File Collector), likely indicating redundancy or mirrored functionality. Additionally, it introduces specific hardware like O-DU 01-01-01 and O-RU 01-01-01-01, with a deeper red tone for emphasis, pointing to physical radio access network elements.

Finally, a separate O-DU (O-RAN Distributed Unit) network is colored similarly but slightly darker, indicating possibly more isolated or hardware-intensive functions. It includes components for DHCP service and reiterates the O-DU and O-RU nodes, but this time, it differentiates between hybrid and hierarchical types of O-RUs, highlighting architectural or deployment distinctions.

Altogether, the diagram illustrates how traffic is isolated and directed between external access points, management UIs, backend services, and network infrastructure components, reflecting both security zoning and functional layering.

Open

References

repo: https://gerrit.o-ran-sc.org/r/gitweb?p=oam.git;a=summary

docker container architecture: https://wiki.onap.org/display/DW/Running+O-RAN-SC+oam+solution