Versions Compared

Old Version 18

changes.mady.by.user Krzysztof Kuzmicki

Saved on

compared with

New Version 19

changes.mady.by.user Krzysztof Kuzmicki

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

These test cases cover the commonality between the test data for 5G - PNF Pre-Onboarding & Onboarding and aims to achieve an end to end verification for Pre-Onboarding and Onboarding.

...

Test Case ID
PNF-POB-OB-1 
Anchor
PNF-POB-OB-1 test
PNF-POB-OB-1 test
Test Case NameTest Pre-Onboarding of Vendor Supplied Package in VNF-SDK
DescriptionTaking a pre-formed sample csar package mimicking a vendor supplied PNF csar which will contain relevant artefacts verify this package against the VNF-SDK CLI tool (R&D approach)
ReleaseDublin
Preconditions

Sample csar package mimicking vendor csar agreed and available

Sample secured zip file consisting of the csar package, a signature file and a certificate file mimicking vendor csar agreed and available

Testing Steps


StepExpected Result

Install VNF Testing platform (VTP) on Linux machine with Ubuntu 18.04 according to instruction. VTP+Installation.doc

VTP is up and running

Copy csar package at linux machine with VTP. valid_all.csarCsar file is present on linux machine.

Validate csar package using VTP tool by running command:

oclip --product onap-vtp csar-validate --pnf --csar valid_all.csar

Validation doesn't find violations in valid_all.csar package

Copy secured zip file at linux machine with VTP.  valid_all.zip

Zip file s present on linux machine.

Validate secured zip file  with csar package using VTP tool by running command:

oclip --product onap-vtp csar-validate --pnf --csar valid_all.zip

Validation doesn't find violations in valid_all.zip package


Conclusion (Pass/Fail)
Testing LabONAP Lab/standalone linux machine

...

Test Case ID
PNF-POB-OB-3 
Test Case NameTest Pre-Onboarding of Vendor Supplied Package in (offline) VNF Test Platform installed according to  https://docs.onap.org/en/latest/submodules/vnfsdk/model.git/docs/files/vnf-test-platform.html
DescriptionTaking a pre-formed sample csar package mimicking a vendor supplied PNF csar which will contain relevant artefacts verify this package against the VNF-SDK API
ReleaseDublin
Preconditions

Sample csar package mimicking vendor csar agreed and available

Testing Steps


StepExpected Result

Install VNF Testing platform (VTP) on Linux machine with Ubuntu 18.04 according to instruction. https://docs.onap.org/en/latest/submodules/vnfsdk/model.git/docs/files/vnf-test-platform.html

export NEXUS_DOCKER_REPO=nexus3.onap.org:10001

docker login $NEXUS_DOCKER_REPO -u docker -p docker

export REFREPO_TAG=1.3.0

export POSTGRES_TAG=latest

export MTU=1450

wget https://raw.githubusercontent.com/onap/vnfsdk-refrepo/master/vnfmarket-be/deployment/install/docker-compose.yml

docker-compose up -d

run docker ps and following entries would be reported:

root@oclip-2:~# docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

246141724b02 nexus3.onap.org:10001/onap/vnfsdk/refrepo:1.3.0 "/service/docker-e..." 2 days ago Up 2 days 0.0.0.0:8000->8000/tcp, 0.0.0.0:8702-8703->8702-8703/tcp, 0.0.0.0:50051->50051/tcp refrepo

20bfa4ba1734 nexus3.onap.org:10001/onap/vnfsdk/refrepo/postgres:latest "docker-entrypoint..." 2 days ago Up 2 days 0.0.0.0:5432->5432/tcp postgres root@oclip-2:~#

REST Endpoint for VTP validation (from local docker compose)
http://<local_docker_host>:8702/onapapi/vnfsdk-marketplace/v1/vtp/executions?requestId=<some_request_id>
REST Endpoint for VTP validation (from ONAP instance)
http://<one_of_ONAP_k8s_hosts>:30297/onapapi/vnfsdk-marketplace/v1/vtp/executions?requestId=<some_request_id>

VTP is up and running.

Endpoint for validation API is available

Open postman application and load VTP_postman_collection.json for VTP validationPostman is available and collection is loaded

Fill parameters in postman:

  • in "file" choose csar/zip file to be validated
  • in "execution" in parameters  put name of file that will be validated "csar": "file://noETSI-Entry-Manifest or ETSI-Entry-Change-Log.csar",
  • in Headers put following value: Content-Type application/x-www-form-urlencoded


Validation doesn't find violations in valid_all.csar package
Pres send button in order to validate csar/zip file

csar/ZIP file  is validated and output is available

Example of output for noETSI-Entry-Manifest or ETSI-Entry-Change-Log.csar is output.json


Conclusion (Pass/Fail)
Testing LabONAP Lab/standalone linux machine

...