Gitiles
Code Review Sign In
gerrit.nordix.org / oransc / ric-plt / rtmgr / 89c2cdeff5dc079ab1aca01e2e830a961095198f
commit89c2cdeff5dc079ab1aca01e2e830a961095198f[log] [tgz]
authorAbdul Wahid W <abdulwahid.w@nokia.com>Mon Dec 02 05:54:15 2019 +0000
committerGerrit Code Review <gerrit@o-ran-sc.org>Mon Dec 02 05:54:15 2019 +0000
tree2c076503dc7d89a34d14d11fbbe8e6620f57fd7c
parent968403dc8cdb53490f41193416ed354effcb7d01 [diff]
parent761934a3d9f7a1426d1e14e34fb9a4c16599a237 [diff]
Merge "Adding scope of RICPlatform that are under Apache License"
tree: 2c076503dc7d89a34d14d11fbbe8e6620f57fd7c
  1. .releases/
  2. api/
  3. cmd/
  4. docs/
  5. manifests/
  6. pkg/
  7. .gitattributes
  8. .gitignore
  9. .gitreview
  10. .readthedocs.yaml
  11. container-tag.yaml
  12. CONTRIBUTING.md
  13. Dockerfile
  14. glide.lock
  15. glide.yaml
  16. INFO.yaml
  17. LICENSE
  18. README.md
  19. RELNOTES
  20. run_rtmgr.sh
  21. tox.ini
README.md

Routing Manager

Table of contents

Introduction

Routing Manager is a basic platform service of RIC. It is responsible for distributing routing policies among the other platform components and xApps.

The routing manager has two ways to get the xapp details from xapp manager - httpGetter or httpRESTful. In case of httpGetter, the implemented logic periodically queries the xApp Manager component for xApps' list. Where in httpRESTful, starts a http server and creates a webhook subscription in xapp manager to update about changes in xapps and waits changed data to arrive on the REST http server. Either ways, the xapp data received is stored and then processed to create routing policies and distributes them to all xApps.

The architecture consists of the following five well defined functions:

  • NorthBound Interface (NBI): Maintains the communication channels towards RIC manager components
  • Routing Policy Engine (RPE): Provides the logic to calculate routing policies
  • Shared Data Layer (SDL): Provides access to different kind persistent data stores
  • SouthBound Interface (SBI): Maintains the communication channels towards RIC tenants and control components
  • Control Logic (RTMGR): Controls the operation of above functions

Current implementation provides support for the followings:

  • NBI:
    • httpGet: simple HTTP GET interface. Expects an URL where it gets the xApps' list in JSON format
    • httRESTful: provides REST API endpoints towards RIC manager components. Expects REST port and url where the HTTP service will be started to listen on.
  • RPE:
    • rmr: creates routing policies formatted for RIC RMR
  • SDL:
    • file: stores xApp data in container's local filesystem (or in a mountpoint)
    • (backlog) sdl: Shared Data Library to Redis database
  • SBI:
    • nngpub: distributes RPE created policies via NNG Pub channel
    • nngpipe: distributes RPE created policies via NNG Pipeline channel

Release notes

Check the separated RELNOTES file.

Prerequisites

Project folder structure

  • /api: contains Swagger spec files
  • /manifest: contains deployment files (Kubernetes manifests, Helm chart)
  • /cmd: contains go project's main file
  • /pkg: contains go project's internal packages
  • /test: contains CI/CD testing files (scripts, mocks, manifests)
  • Dockerfile: contains main docker file
  • container-tag.yaml: contains CI specific container tag information
  • run_rtmgr.sh: shell script to run rtmgr (requires environment variables to be set)

Installation guide

Compiling code

Docker compile

The Dockerfile located in the project root folder does the following three things:

  • As a first step, it creates a build container, fetches XApp Manager's spec file, generates rest api code from swagger spec and builds rtmgr.
  • As a second step, it executes UTs on rtmgr source code.
  • As a third step, it creates the final container from rtmgr binary (Ubuntu based). For a docker build execute docker build --tag=rtmgr-build:test . in the project root directory (feel free to replace the name:tag with your own)

Compiling without docker

Compiling without Docker involves some manual steps before compiling directly with "go build". The XApp manager's spec file must be fetched, then api generated with swagger. (these steps are included in the Dockerfile). After the code is generated, glide can install the dependencies of rtmgr. Make sure you set your GOPATH variable correctly (example: $HOME/go/src/routing-manager) Code generation and building example (from project root folder):

git clone "https://gerrit.o-ran-sc.org/r/ric-plt/appmgr" && cp appmgr/api/appmgr_rest_api.yaml api/
swagger generate server -f api/routing_manager.yaml -t pkg/ --exclude-main -r LICENSE
swagger generate client -f api/appmgr_rest_api.yaml -t pkg/ -m appmgr_model -c appmgr_client -r LICENSE
glide install --strip-vendor
go build cmd/rtmgr.go

NOTE: before doing a docker build it is advised to remove any generated files and vendor packages:

# assuming that you stand in project root dir
rm -rf appmgr vendor pkg/appmgr_* pkg/models pkg/restapi

Installing Routing Manager

Preparing environment

Tag the rtmgr container according to the project release and push it to a registry accessible from all minions of the Kubernetes cluster. Edit the container image section of rtmgr-dep.yaml file according to the rtmgr image tag.

Deploying Routing Manager

Issue the kubectl create -f {manifest.yaml} command in the following order:

  1. manifests/namespace.yaml: creates the example namespace for routing-manager resources
  2. manifests/rtmgr/rtmgr-cfg.yaml: creates default routes config file for routing-manager
  3. manifests/rtmgr/rtmgr-dep.yaml: instantiates the rtmgr deployment in the example namespace
  4. manifests/rtmgr/rtmgr-svc.yaml: creates the rtmgr service in example namespace

NOTE: The above manifest files will deploy routing manager with NBI as httpRESTful which would not succeed unless there is an xapp manager running at the defined xm-url. The solution is either to deploy a real XAPP manager before deploying routing-manager or start the mock xmgr as mentioned in Testing.

Testing and Troubleshoting

Testing with Kubernetes

Routing Manager's behaviour can be tested using the mocked xApp Manager, traffic generator xApp and receiver xApp.

  1. Checkout and compile both xApp receiver and xApp Tx generator of RIC admission control project: https://gerrit.o-ran-sc.org/r/admin/repos/ric-app/admin
  2. Copy the adm-ctrl-xapp binary to ./test/docker/xapp.build folder furthermore copy all RMR related dinamycally linked library under ./test/docker/xapp.build/usr folder. Issue docker build ./test/docker/xapp.build command. Tag the recently created docker image and push it to the common registry.
  3. Copy the test-tx binary to ./test/docker/xapp-tx.build folder furthermore copy all RMR related dinamycally linked library under ./test/docker/xapp.build/usr folder. Issue docker build ./test/docker/xapp-tx.build command. Tag the recently created docker image and push it to the common registry.
  4. Enter the ./test/docker/xmgr.build folder and issue docker build .. Tag the recently created docker image and push it to the common registry.
  5. Modify the docker image version in each kuberbetes manifest files under ./test/kubernetes/ folder accordingly then issue the kubectl create -f {manifest.yaml} on each file.
  6. Compile and Install routing manager
  7. Once the routing manager is started, it retrievs the initial xapp list from xmgr via HTTPGet additonaly it starts to listen on http://rtmgr:8888/v1/handles/xapp-handle endpoint and ready to receive xapp list updates.
  8. Edit the provided test/data/xapp.json file accordingly and issue the following curl command to update rtmgr's xapp list. curl --header "Content-Type: application/json" --request POST --data '@./test/data/xapps.json' http://10.244.2.104:8888/v1/handles/xapp-handle

Executing unit tests

For running unit tests, execute the following command: go test ./pkg/nbi (or any package - feel free to add your own parameters) If you wish to execute the full UT set with coverage:

  mkdir -p unit-test
  go test ./pkg/sbi ./pkg/rpe ./pkg/nbi ./pkg/sdl -cover -race -coverprofile=$PWD/unit-test/c.out
  go tool cover -html=$PWD/unit-test/c.out -o $PWD/unit-test/coverage.htm

Command line arguments

Routing manager binary can be called with -h flag when it displays the available command line arguments and it's default value.

Example:

Usage of ./rtmgr:
  -configfile string
        Routing manager's configuration file path (default "/etc/rtmgrcfg.json")
  -filename string
        Absolute path of file where the route information to be stored (default "/db/rt.json")
  -loglevel string
        INFO | WARN | ERROR | DEBUG (default "INFO")
  -nbi string
        Northbound interface module to be used. Valid values are: 'httpGetter | httpRESTful' (default "httpGetter")
  -nbi-if string
        Base HTTP URL where routing manager will be listening on (default "http://localhost:8888")
  -rpe string
        Route Policy Engine to be used. Valid values are: 'rmrpush | rmrpub' (default "rmrpush")
  -sbi string
        Southbound interface module to be used. Valid values are: 'nngpush | nngpub' (default "nngpush")
  -sbi-if string
        IPv4 address of interface where Southbound socket to be opened (default "0.0.0.0")
  -sdl string
        Datastore enginge to be used. Valid values are: 'file' (default "file")
  -xm-url string
        HTTP URL where xApp Manager exposes the entire xApp List (default "http://localhost:3000/xapps")

For troubleshooting purpose the default logging level can be increased to DEBUG. (by hand launch it's set to INFO, kubernetes manifest has DEBUG set by default).

Upcoming changes

[] Add unit tests

License

This project is licensed under the Apache License, Version 2.0 - see the LICENSE