Welcome to O-RAN SC SMO O1 Documentation
SMO O1 Overview
This repository is for the implementation, installation, and use of the O1 interface of SMO. It uses the Software Defined Netowrk (SDN) Controller for Radio (SDNR) to implement the O1 interface. The software comes in the form of Docker containers that are setup using docker-compose.
Developer-Guide
Processes
Actions
Release-Notes
This document provides the release notes for releases related to SMO O1.
Version history
Date |
Ver. |
Author |
Comment |
2022-12-15 |
G |
G-release |
|
2021-12-15 |
E |
E-release |
|
2021-06-15 |
D |
Dawn release |
|
2020-12-15 |
C |
Cherry release |
Summary
G-release: The G-release mainly targeted to update with the latest SDNR image.
E-release:
The E-release was targeted towards network slicing. The O1 interface did not need any updates to support the use case. Most of the support for the use case has to come in the Network Function (NF), and in the rApp that supports the use case. The only percievable change is the change in the logo to the GUI interface.
The D(awn) release was targeted towards implementation of the O1 interface itself and getting an initial implementation in place.
Release Data
Project |
SMO O1 |
Repo/commit-ID |
Repo: smo/o1 Commit id: |
Release designation |
G-Release |
Release date |
2022-12-15 |
Purpose of the delivery |
Latest SDNR image |
Feature Additions
JIRA BACK-LOG:
JIRA REFERENCE |
SLOGAN |
Bug Corrections
JIRA TICKETS:
JIRA REFERENCE |
SLOGAN |
SMO-11 |
Change banner in O1 GUI interface |
Deliverables
Software Deliverables
<STATE WHAT SOFTWARE DELIVERABLES THAT ARE RELATED TO THIS VERSION, AND WHERE THOSE CAN BE RETRIEVED>
Documentation Deliverables
<STATE WHAT DOCUMENTATION DELIVERABLES THAT ARE RELATED TO THIS VERSION, AND WHERE THOSE CAN BE RETRIEVED>
Known Limitations, Issues and Workarounds
System Limitations
<STATE ALL RELEVANT SYSTEM LIMITATIONS, IF THERE IS ANY>
Known Issues
<STATE ALL KNOWN ISSUES WITH JIRA REFERENCE>
<EXAMPLE>:
JIRA TICKETS:
JIRA REFERENCE |
SLOGAN |
Workarounds
<STATE ALL KNOWN WORKAROUNDS TO THE ISSUES STATED ABOVE, IF THERE IS ANY>
References
<STATE RELEVANT REFERENCES FOR THIS RELEASE/VERSION>
Installation Guide
Abstract
This document describes how to install the software for SMO O1, it’s dependencies and required system resources.
Version history
Date |
Ver. |
Author |
Comment |
2021-12-13 |
0.0.1 |
Initial Version |
|
0.0.2 |
|||
1.0 |
Introduction
O1:
This document describes the supported software and hardware configurations for the reference component as well as providing guidelines on how to install and configure such reference system.
The audience of this document is assumed to have good knowledge in RAN network, Docker and Linux system.
Preface
Prerequisites:
Before starting the installation of O1, make sure the following hardware and software requirements are met.
Hardware Requirements
System:
Following minimum hardware requirements must be met for installation of SMO O1. While the system can be installed on a smaller system, it will be slow, and difficult to use:
HW Aspect |
Requirement |
# of servers |
1 |
CPU |
4 |
RAM |
16G |
Disk |
100G |
NICs |
1 |
Software Installation and Deployment
Docker and docker-compose:
This section describes the installation of the software to enable the SMO O1 interface on the referenced hardware.
The software installation has been tested on a Ubuntu 20.04 based system. Assuming such an installation, make sure that Docker and docker-compose are installed on the system.
To deploy the solution, type the following on the command line:
$ docker-compose up -d
Once the deployment is successful, verify the deployment using the following command:
$ docker-compose ps
Expect an output that is similar to this:
Name Command State Ports
------------------------------------------------------------------------------------------------------------------------------------
sdnr /bin/sh -c /opt/onap/sdnc/ ... Up 0.0.0.0:8101->8101/tcp,:::8101->8101/tcp, 0.0.0.0:8181->8181/tcp,:::8181->8181/tcp
sdnrdb /tini -- /usr/local/bin/do ... Up 9200/tcp, 9300/tcp
Thereafter, the GUI interface for O1 can be accessed at:
http://<host_ip>:8181/odlux/index.html
The username/password is:
admin/Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U
and can be updated by updating the .env file in the repository.
References
User Guide
This is the user guide of OSC SMO O1 Interface
Description
This project is intended for operators that want to configure the RAN Network Functions (NF), i.e., O-DU, O-CU, O-RU, and the Near RT-RIC over the O1 (NETCONF/RESTCONF) interface.
Each of the NFs advertise their own capabilities over a NETCONF session that is established between the SMO and each of the NFs. Thereafter the NETCONF session is used to configure and manage each of the NFs.
This user guide assumes that Installation Guide has been followed to install the necessary hardware and software.
Feature Introduction
The GUI interface for O1 interface can be accessed at:
http://<host_ip>:8181/odlux/index.html
The username/password is:
admin/Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U
and can be updated by updating the .env file in the repository.
API-Docs
This is the API-docs of <COMPONENT>