You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

O1 Simulators for O-DU and O-RU

Scope

The purpose of the O1 Simulators is to provide a NETCONF Server framework exposing the OpenFronthaul November 2020 train models, in the case of O-RU, and the use case specific model for the O-DU. In addition, the Simulators provide the already existing capabilities like NETCONF Call Home (via SSH), sending VES messages (pnfRegistration, fault, file-ready etc.).

Artifacts

Each of the simulators is released as a docker image which can be used independent from any other image.

  • O-RU Simulator: nexus3.o-ran-sc.org:10004/o-ran-sc/nts-ng-o-ran-ru-fh:1.2.1
  • O-DU Simulator: nexus3.o-ran-sc.org:10004/o-ran-sc/nts-ng-o-ran-du:1.2.1

Starting

The Simulators can be started easily via docker-compose. Example of such a file:

O-RU and O-DU Simulators docker-compose
version: '3.7'
services:
  ntsim-ng-o-ru:
    image: "${DOCKER_REPO}nts-ng-o-ran-ru-fh:${NTS_BUILD_VERSION}"
    cap_add:
      - SYS_ADMIN
    stop_grace_period: 5m
    hostname: "O-RAN-O-RU-1"
    ports:
     - "::18300:830"
     - "::18301:831"
    environment:
        IPv6_ENABLED: ${IPv6_ENABLED}
        SSH_CONNECTIONS: ${SSH_CONNECTIONS}
        TLS_CONNECTIONS: ${TLS_CONNECTIONS}
        
        NTS_NF_STANDALONE_START_FEATURES: "datastore-populate ves-heartbeat ves-file-ready web-cut-through manual-notification-generation"
        
        SDN_CONTROLLER_PROTOCOL: ${SDN_CONTROLLER_PROTOCOL}
        SDN_CONTROLLER_IP: ${SDN_CONTROLLER_IP}
        SDN_CONTROLLER_PORT: ${SDN_CONTROLLER_PORT}
        SDN_CONTROLLER_CALLHOME_PORT: ${SDN_CONTROLLER_CALLHOME_PORT}
        SDN_CONTROLLER_USERNAME: ${SDN_CONTROLLER_USERNAME}
        SDN_CONTROLLER_PASSWORD: ${SDN_CONTROLLER_PASSWORD}
  
        VES_COMMON_HEADER_VERSION: ${VES_COMMON_HEADER_VERSION}
        VES_ENDPOINT_PROTOCOL: ${VES_ENDPOINT_PROTOCOL}
        VES_ENDPOINT_IP: ${VES_ENDPOINT_IP}
        VES_ENDPOINT_PORT: ${VES_ENDPOINT_PORT}
        VES_ENDPOINT_AUTH_METHOD: ${VES_ENDPOINT_AUTH_METHOD}
        VES_ENDPOINT_USERNAME: ${VES_ENDPOINT_USERNAME}
        VES_ENDPOINT_PASSWORD: ${VES_ENDPOINT_PASSWORD}

  ntsim-ng-o-du:
    image: "${DOCKER_REPO}nts-ng-o-ran-du:${NTS_BUILD_VERSION}"
    cap_add:
      - SYS_ADMIN
    stop_grace_period: 5m
    hostname: "O-RAN-O-DU-1"
    ports:
     - "::18310:830"
     - "::18311:831"
    environment:
      IPv6_ENABLED: ${IPv6_ENABLED}
      SSH_CONNECTIONS: ${SSH_CONNECTIONS}
      TLS_CONNECTIONS: ${TLS_CONNECTIONS}
      
      NTS_NF_STANDALONE_START_FEATURES: "datastore-populate ves-heartbeat ves-file-ready manual-notification-generation web-cut-through"
      
      SDN_CONTROLLER_PROTOCOL: ${SDN_CONTROLLER_PROTOCOL}
      SDN_CONTROLLER_IP: ${SDN_CONTROLLER_IP}
      SDN_CONTROLLER_PORT: ${SDN_CONTROLLER_PORT}
      SDN_CONTROLLER_CALLHOME_PORT: ${SDN_CONTROLLER_CALLHOME_PORT}
      SDN_CONTROLLER_USERNAME: ${SDN_CONTROLLER_USERNAME}
      SDN_CONTROLLER_PASSWORD: ${SDN_CONTROLLER_PASSWORD}

      VES_COMMON_HEADER_VERSION: ${VES_COMMON_HEADER_VERSION}
      VES_ENDPOINT_PROTOCOL: ${VES_ENDPOINT_PROTOCOL}
      VES_ENDPOINT_IP: ${VES_ENDPOINT_IP}
      VES_ENDPOINT_PORT: ${VES_ENDPOINT_PORT}
      VES_ENDPOINT_AUTH_METHOD: ${VES_ENDPOINT_AUTH_METHOD}
      VES_ENDPOINT_USERNAME: ${VES_ENDPOINT_USERNAME}
      VES_ENDPOINT_PASSWORD: ${VES_ENDPOINT_PASSWORD}

# We can attach to any other docker network, like in the example below        
# networks:
#   default:
#     external:
#       name: smo_integration





  • No labels