...
Sanity Docker executed as part of our Docker run script and will be started automatically on demand as part of other Dockers init process by default.
Executing example:
Code Block |
---|
/data/scripts/docker_run.sh -r 1.1-stagging-lates |
will trigger the sanity docker execution after the components have started.
There is an option to cancel sanity execution by using –s flag to start Docker run script.
Executing example:
Code Block |
---|
/data/scripts/docker_run.sh -s -r 1.1-stagging-lateslatest -t |
-t flag meaning start sanity docker
About onboarding E2E flow:
...
- Onboard of VNF
- Create VF from VSP
- Certify VF
- Create Service
- Add VF to service
Certify Service
- Export TOSCA and validate it structure using external TOSCA parser
**as part of execution we open a connection to Titan and perform resources clean up both before and after tests execution (only resource with “ci” prefix will be deleted from the catalog)
List of VNFs/PNFs that proceed by onboarding flow:
- vCPE_Infra.zip
- vCPE_Vbng.zip
- vCPE_Vbrgemu.zip
- vCPE_Vgmux.zip
- vCPE_Vgw.zip
- base_clearwatersample-signed-pnf-cms-includes-cert-1.0.1-SNAPSHOT.zip
- sample-signed-pnf-1.0.1-SNAPSHOT.zip
- sample-pnf-1.0.1-SNAPSHOT.csar
- sample-pnf-custom-type.csar
- vbng.zip
- vgmux.zip
- vfw.zip
- vvg.zip
- base_vvg.zip
- vLBMS.zip
- vgw.zip
- infra.zip
- vLB.zip
- base_vfw.zip
- base_vlb.zip
- base_vvg.zip
- vbrgemu.zip
- resource-ZteEpcMmeVf-csar_fix.csar
- ZteEpcMmeVf.csa
- Huawei_vHSS.csar
- vSBC_update_v03.csar
- Huawei_vMME.csar
- vsp-vgw.csar
- database-substitution-mappings.csar
Execution time:
Current tests execution time is ~2min ~7min – this includes onboarding of 5 VNFs 22 VNF/PNF running in 2 threads1 thread
Report location:
Code Block |
---|
/data/logs/sdc-sanity-api-tests/ExtentReport/ /data/logs/sdc-ui-tests/ExtentReport/ |
Report example:
CSIT:
SDC plans to leverage our internal sanity docker as part of the CSframeworkork. we will be executing the docker from the CSIT and storing the results
...