- Created by Alex Stancu, last modified on Apr 27, 2021
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 6 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:
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" 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" NTS_NF_MOUNT_POINT_ADDRESSING_METHOD: ${NTS_NF_MOUNT_POINT_ADDRESSING_METHOD} 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" 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" NTS_NF_MOUNT_POINT_ADDRESSING_METHOD: ${NTS_NF_MOUNT_POINT_ADDRESSING_METHOD} 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
The variables which are used in the compose file can be defined separately in a .env file:
DOCKER_REPO=nexus3.o-ran-sc.org:10004/o-ran-sc/ NTS_MANAGER_PORT=8300 NTS_BUILD_VERSION=1.2.3 IPv6_ENABLED=false SSH_CONNECTIONS=1 TLS_CONNECTIONS=0 NTS_NF_MOUNT_POINT_ADDRESSING_METHOD=host-mapping SDN_CONTROLLER_PROTOCOL=http SDN_CONTROLLER_IP=172.40.0.21 SDN_CONTROLLER_PORT=8181 SDN_CONTROLLER_CALLHOME_PORT=6666 SDN_CONTROLLER_USERNAME=admin SDN_CONTROLLER_PASSWORD=admin VES_COMMON_HEADER_VERSION=7.1 VES_ENDPOINT_PROTOCOL=https VES_ENDPOINT_IP=172.40.0.90 VES_ENDPOINT_PORT=8443 VES_ENDPOINT_AUTH_METHOD=no-auth VES_ENDPOINT_USERNAME=sample1 VES_ENDPOINT_PASSWORD=sample1
- No labels