| | 43 | - We referred to the GitHub repositories: |
| | 44 | - [https://github.com/o-ran-sc/it-tifg] |
| | 45 | - [https://github.com/o-ran-sc/oam/tree/master/solution] [[BR]] |
| | 46 | These were mentioned by Alex. |
| | 47 | - After studying the README files of the repositories, we understood that we need to set up two frameworks: |
| | 48 | - '''Service Management and Orchestration (SMO) for Operations and Maintenance (OAM)''' and '''O-RU framework''' to test the '''Hybrid M-plane'''. |
| | 49 | - '''Prerequisites:''' [[BR]] |
| | 50 | The solution was tested on a virtual machine (VM) with the following configuration: |
| | 51 | - 4 CPU cores |
| | 52 | - 16 GB RAM |
| | 53 | - 50 GB storage |
| | 54 | - Python 3.12 (default in Ubuntu 24.04) |
| | 55 | - Docker installed |
| | 56 | - Firstly, we started by setting up the '''SMO for OAM''' framework and performed a step-by-step environment setup: |
| | 57 | - Created .env files |
| | 58 | - Configured domain settings |
| | 59 | - Built docker compose infrastructure |
| | 60 | - Simulated various network services (e.g., controller, VES collector) |
| | 61 | - Debugged and resolved common setup issues such as: |
| | 62 | - health checks |
| | 63 | - certificate installation (OpenDaylight) |
| | 64 | - DNS/host issues |
| | 65 | - The '''OpenDaylight controller''' requires a certificate to be installed before it can be launched. It is installed via [https://docs.opendaylight.org/en/latest/downloads.html] |
| | 66 | - '''OpenDaylight:''' [[BR]] |
| | 67 | OpenDaylight (ODL) is an open-source, modular, and extensible Software-Defined Networking (SDN) platform designed to enable centralized network control and programmability. In the context of the O-RU and SMO frameworks for testing the Hybrid Management Plane (Hybrid M-plane) in O-RAN architecture, OpenDaylight acts as the SDN controller responsible for managing and orchestrating network services, configurations, and state synchronization between components. |
| | 68 | |
| | 69 | Within the SMO (Service Management and Orchestration) framework, OpenDaylight plays a critical role in: |
| | 70 | - Controlling and automating the configuration of the O-RU (O-RAN Radio Unit) over standardized interfaces (e.g., NetConf/YANG). |
| | 71 | - Simulating or managing the communication across the O-RAN M-plane, which blends traditional and virtualized infrastructure. |
| | 72 | - Ensuring secure and policy-driven operations, such as certificate handling, device onboarding, and performance monitoring. |
| | 73 | Its extensibility and compatibility with O-RAN-defined models make OpenDaylight a foundational component for building a reference implementation that reflects the goals of a disaggregated, interoperable RAN. |
| | 74 | |
