...
Here is the RMR communication diagram among the xApps:
Demo Video
| Multimedia | ||||||
|---|---|---|---|---|---|---|
|
Delivery Status
| Warning | ||
|---|---|---|
| ||
Only the Integration PTL should edit the delivery status table to track the release validation progress |
...
xApps can be cloned from nexus repository using the following command:
TS xApp:
git clone "https://gerrit.o-ran-sc.org/r/ric-app/ts"
AD xApp:
git clone "https://gerrit.o-ran-sc.org/r/ric-app/ad"
Currently, we are building the images locally after cloning it.
Once the Staging and Release images are available, we can use the below commands.
Build and push the docker image for both AD xApp and TS xApp using the following:
...
Each of these xApps have a descriptor in their gerrit repo under the xapp-descriptor/ directory.
None of them have xapp specific controls and therefore no individual json schema.
Here are the URLs for each which can be included in HTTP POST call to onboard tool.
TS xApp:
https://gerrit.o-ran-sc.org/r/gitweb?p=ric-app/ts.git;a=blob_plain;f=xapp-descriptor/config.json;hb=HEAD
AD xApp:
https://gerrit.o-ran-sc.org/r/gitweb?p=ric-app/ad.git;a=blob_plain;f=xapp-descriptor/config.json;h=ae48a24a1ad8b510bace596c76f7c480c6884f21;hb=297dbd6245ec69571c8ad7091a18cbe9c7ba2488HEAD
It is required to deploy TS xApp followed by AD xApp.
...
Onboarding xApps:
Invoke the API calls into the xApp On-boarder, providing it the locations of the xApp descripters.
curl --location --request POST "http://$(hostname):32080/onboard/api/v1/onboard/download" --header 'Content-Type: application/json' --data-binary "@./onboard.ts.url"
curl --location --request POST "http://$(hostname):32080/onboard/api/v1/onboard/download" --header 'Content-Type: application/json' --data-binary "@./onboard.ad.url"
Checking the on-boarded charts:
curl --location --request GET "http://$(hostname):32080/onboard/api/v1/charts"
...