This demo package show distribution om PM (file based pm and streamed pm) from an O-DU simulator to rApps.
The main purpose of the demo is to show how a data consumer (rApp) can subscribe to data from a data producer via a job in ICS.
The demo requires a running docker and docker-compose.
Demo has been verified on Mac-OS but should work on Linux as well as windows (Git-bash)
Download the nonrtric-prototyping repo
git clone "https://gerrit.nordix.org/local/oransc/nonrtric-prototyping" cd nonrtric-prototyping/pm-data-event-demo
The whole package is started with a single command - ./run-all.sh. To clean all containers, use the cmd - ./down-all.sh
Start the package
./run-all.sh
(in the end of the script - hit enter to start sending fileready events from the O-DU. However, the streamed pm counters are already sending events
./run-all.sh ... ... Hit enter to start sending fileready events ... ...
Make sure that no errors occurs during the script execution. For example, other running container or ports already occupied by other applications may cause errors in the script.
When the script has finished, there should be 22 running containers - see example below.
The O-DU simulator will continuously send events with a random counter value every 10 second. And 900 fileready events will be sent with 30 sec interval where a few counter values has counter values derived from the index of the pm file.
The flow of data can be viewed in several logs.
Events received by the VES collector
docker exec -it ves-collector tail -f /opt/app/VESCollector/logs/input.log
Files fetched from the O-DU and published to the data router - by the datafile collector
docker logs -f datafile-collector
PM Mapper log
docker logs -f pmmapper
PM files and as well as the streamed counters are sent to two simulated rAPPs, rapp1 and rapp2
Logs can be viewed (replace X with 1 or 2)
docker logs -f rappX
In addition, the files are also dumped to directories mounted to the simulated rapp1 and rapp2. Only the latest files is stored.
The file data.json contains the file and the event header
The file event.json contains the streamed counter and the event header
Again, replace X with 1 or 2
cat group6/jsondump/rappX/data.json cat group6/jsondump/rappX/event.json
The set of started containers can be cleaned up at any time by this script
./down-all.sh