Under construction!
This page describes how to run current implementation for the O-DU Slice Assurance usecase.
...
| Code Block |
|---|
git clone "https://gerrit.o-ran-sc.org/r/nonrtric/rapp/ransliceassurance" |
Run using simulators
Run Dmaap MR / SDNR stub
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
Example:
└─ $ ▶ CONSUMER_HOST=http://localhost CONSUMER_PORT=3905 ./icsversion |
Use case using SMO deployment
For this case, the following components will be needed:
- DU simulator, that will send VES message.
- OAM controller, that will create stream to communicate with VES collector and trigger PM Job event in DU.
- VES Collector, representing the VES (REST) provider at SMO for all kind of events
- ONAP Dmaap, representing SMO DMaaP component, includes message-router
- Dmaap Adapter, that takes information from DMaaP and present it as a coordinated Information Producer
- ICS Information Coordinator Service, that coordinate/Register Information Types, Producers, Consumers, and Jobs.
For starting the OAM Controller and VES Collector, a minimal SMO deployment is needed. This can be started using the instructions from here and ignoring the ONAP-Policy steps. NonRT-RIC should be replaced for docker-compose file located in
| Code Block | ||||
|---|---|---|---|---|
| ||||
ransliceassurance/docker-compose/icsversion |