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.
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 | 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 |
...