This workflow examines the SMO SMO CSAR package validation tool that identifies CSAR package issues.
...
validating tool that provides the testers and DevOps engineers to validate the TOSCA version, CSAR version and verify if the yaml file exists in the directory and the entry definition contents of yaml file.
Demo Video
| Multimedia |
|---|
| name | SMO-CSAR.mov |
|---|
| width | 1280 |
|---|
| height | 720 |
|---|
|
Delivery Status
| Warning |
|---|
|
Only the Integration PTL should edit the delivery status table to track the release validation progress |
|
| OTF | OAM | NONRTRIC | RICP | RICAPP | O-DU | O-CU | Test Result | Notes |
|---|
| Deployment Artifacts | Docker Container |
Containers are locally built
|
|
|
|
|
|
|
| SMO only provides source codes for this tool |
| Helm Charts |
Docker compose
|
|
|
|
|
|
|
| SMO only provides source codes for this tool |
| Deployment scripts |
| N/A |
|
|
|
|
|
| SMO only provides source codes for this tool |
| E2E Flows |
Mount FH simulator | O-RAN-FH Simulator through ODL | The
Usage from sources
...
Navigate into the validator folder
| Code Block |
|---|
|
cd solution/dev/smo/yang-validator |
...
Start the services of of the validator
| Code Block |
|---|
|
docker-compose up |
This starts two services currently:
- a O-RAN-FH Simulator exposing the O1 interface YANG models (NETCONF username/password is "netconf/netconf" and port is 18300)
- a vanilla OpenDaylight Aluminium SR0 version, acting as the SMO (ODL username/password is "admin/admin" and port is 8181)
...
| Code Block |
|---|
|
curl -X PUT "http://<VM_IP>:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=ntsim-ng-o-ran-fh" -u admin:admin -H "accept: */*" -H "Content-Type: application/xml" -d "<node xmlns=\"urn:TBD:params:xml:ns:yang:network-topology\"><node-id>ntsim-ng-o-ran-fh</node-id><host xmlns=\"urn:opendaylight:netconf-node-topology\"><VM_IP></host><port xmlns=\"urn:opendaylight:netconf-node-topology\">18300</port><username xmlns=\"urn:opendaylight:netconf-node-topology\">netconf</username><password xmlns=\"urn:opendaylight:netconf-node-topology\">netconf</password></node>" |
| Note |
|---|
|
You need to change two places in the above API call. Use your VM's IP in the following API call. |
That's it! Now the mount-point named ntsim-ng-o-ran-fh can be used in the ODL Aluminium SR0 to test XML/JSON. configuration data against the YANG definition.
Usage from OSC Lab
The framework is deployed in a VM inside OSC Lab: 192.168.130.90
One which has access to OSC Lab could use directly the SMO (OpenDaylight Aluminium) to address the O-RAN-FH Simulator (having the mount-point name ntsim-ng-o-ran-fh). E.g. of a GET request:
...
...
| Tosca-csar-ver-vnf-vsn.csar |
|
|
|
|
|
|
|
|
|
| Tosca-ver-vnf-vsn.csar |
|
|
|
|
|
|
|
|
|
| ns-vsn.csar |
|
|
|
|
|
|
|
|
|
| vnf-vsn.csar |
|
|
|
|
|
|
|
|
|
| yaml-error-vnf-vsn.csar |
|
|
|
|
|
|
|
|
|
| yaml-file-error-vnf-vsn.csar |
|
|
|
|
|
|
|
|
|
| 3rd-party csar package |
|
|
|
|
|
|
|
|
|
| Info |
|---|
| title | Limited SMO deliverables |
|---|
|
* As a new project, the SMO project delivers multiple tools that have not been integrated into a unified platform in the Cherry release. Therefore, helm charts and deployment scripts are not provided yet. |
Usage from sources
Git clone https://gerrit.o-ran-sc.org/r/smo/app.git
Script path: ./tools/oran-pkg-validation
Tool file contents:
main.py
csar.py
Toscameta.py
utlis.py
Usage:
python3 main.py <validate function> -d <destination> [--no-verify-cert] <source>
<source> : source directory where the csar package zip file exists.
<destination> : destination directory to unzip the csar contents.
[--no-verify-cert] : Optional parameter.
example:
python3 main.py csar-validate -d /tmp/ [--no-verify-cert] CSAR-dest/vnf-vsn.csar
The ORAN CSAR package validation code leverages from vnfsdk CSAR pkg code with modification.
...
