Test Manual
Deploy E2Simulator
There are several steps below that need to be taken to run this successfully. Sorry it is not yet as smooth as it should be. Some of these need to be automated properly, and some have to do with platform issues. If someone could take some of these on it would be helpful.
1. Deploy RIC platform
2. kubectl rollout restart deployment --namespace ricplt deployment-ricplt-e2mgr deployment-ricplt-e2term-alpha (The e2mgr and e2term need to be restarted; this is due to some issues with health check; I don’t know whether it has been resolved by that team)
3. In the root directory of e2sim:
4. Follow directions in README to produce the deb files
5. Since the deb files are not yet pushed to package cloud, we need to copy them
6. cp e2sim*deb ../e2sm_examples/kpm_e2sm
7. cd ../e2sm_examples/kpm_e2sm
8. Edit the Dockerfile at the bottom to have IP address of service-ricplt-e2term-sctp-alpha service
9. docker build .
10. docker tag <tag just built> e2simul:0.0.2
11. helm install –namespace ricplt helm
Once deployed, kubectl logs will show:
- An E2 Setup Request from E2 Simulator to E2 Term
- An E2 Setup Response from E2 Term to E2 Simulator
Onboarding and Deployment of xApps
...
- Traffic Steering (TS) xApp (AT&T)
- QoE Prediction Driver (QPDriver) xApp (AT&T)
- QoE Prediction (QP) xApp (AT&T)
- KPIMON xApp (Samsung)
The first step is to deploy KPIMON xApp
Since KPIMON xApp does not yet have a CI job to create an image in Nexus and also does not have an xApp descriptor,
currently KPIMON deployment must be done in the following way:
- clone scp/ric-app/kpimon
- docker build .
- docker tag <image tag just created>
Now deploy the other three xApps
Each of these three xApps Each of them except for KPIMON have a descriptor in their gerrit repo under the xapp-descriptor/ directory.
...