SMO CSAR Package Validation Verification
This workflow examines the SMO CSAR package 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
Delivery Status
DO NOT EDIT
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 |
|
|
|
|
|
|
|
| SMO only provides source codes for this tool |
Helm Charts |
|
|
|
|
|
|
|
| SMO only provides source codes for this tool | |
Deployment scripts |
| N/A |
|
|
|
|
|
| SMO only provides source codes for this tool | |
E2E Flows | 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 |
|
|
|
|
|
|
|
|
|
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.gitScript 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.