...
The picture below shows the setup used for function tests. Non-RT RIC components in orange, simulators in light blue and the test environment in dark blue. The purple arrow is outside the scope of the test but is used for demo test scripts.
Note: The Control Panel GUI consist of two parts, control panel and the gateway for accessing the nonrtric components.
Note: When running in kubernetes, the test engine uses a proxy (not shown) for accessing the nonrtric components.
Test scripts/Test cases
The below table is a list of test cases. All scripts beginning with the letters "FTC" (Function Test Case) are considered test scripts to test functionality. The remaining test scripts are primarily used for demo purposes.
...
- Bash shell
- docker (latest)
- docker-compose (latest)
- python3 (latest)
- minikube (latest) or a local kubernetes cluster - only needed when running in kubernetes mode
...
| Component | image (release repo) | tag for d-release profile | tag for cherry profile (release) | |
|---|---|---|---|---|
| Policy Management Service | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-policy-agent | 2.2.0 | 2.1.1 | cherry |
| A1-controller | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-a1-controller | - | 2.0.1cherry | |
| SDNC A1 Controller | nexus3.onap.org:10002/onap/sdnc-image | 2.1.2 | - | |
| Enrichment Coordinator Service | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-enrichment-coordinator-service | 1.1.0 | 1.0.1 | cherry |
| Control Panel | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-controlpanel | 2.2.0 | 2.1.0 | |
| Gateway | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-gateway | 1.1.0 | cherry- | |
| A1-Simulator | nexus3.o-ran-sc.org:10002/o-ran-sc/a1-simulator | 2.1.0 | 2.1.0 | cherry |
| R-APP Catalogue | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-r-app-catalogue | 1.1.0 | 1.0.1cherry |
"profile" refers to the name of the environment variable profile used when executed a test case. The profiles has the pattern 'test_env-oran<profileoran-<profile-name>.sh in the test/common dir.