The docker compose file helps the user to deploy all or partial components of the Slice assurance use case with one command.
Minimal SMO deployment is needed. This can be started using the instructions from https://gerrit.o-ran-sc.org/r/gitweb?p=oam.git;a=blob;f=solution/integration/README.md;h=73100a4d31a84fb0de9beeb52b639df249ab0fcf;hb=HEAD
This docker compose start the following components:
Coordinate/Register Information Types, Producers, Consumers, and Jobs.
The Non-RT RIC Control Panel is a graphical user interface that enables the user to view and manage the A1 policies in the RAN and also view producers and jobs for the Information coordinator service.
To view the policy or information jobs and types in control panel gui along with Policy Management Service & Information Coordinator Service you should also have nonrtric gateway because all the request from the gui are passed through this API gateway.
Two alternatives mediators that take information from DMaaP (& Kafka) and present it as a coordinated Information Producer. These configurable adapters/mediators act as producers of Information Coordinator Service (ICS) jobs by polling topics in DMaaP Message Router (MR) or Kafka and pushing the messages to a consumer.
The DMaaP Adaptor Service needs two configurations files, one for the application specific parameters and one for the types the application supports. More information can be found on wiki page: Java version.
The DMaaP Mediator Producer needs one configuration file for the types the application supports and different environment variables that can be configured in the docker compose file. More information can be found on wiki page: Go version.
O-DU Closed Loop use case Slice Assurance rApp integrated with ICS.
docker-compose up -d
docker logs -f ics docker logs -f dmaap-adaptor-service docker logs -f dmaap-mediator-service docker logs -f odu-app