VVP - VNF Test Platform integration

Owned by Vincent Scharf
Nov 30, 2018
2 min read

Status

 Draft

Submitter

@Vincent Scharf

Contributors

@Vincent Scharf

Proposed Release

Dublin

JIRA Ticket(s)

VVP-120: Introduction of a web based vvp validation platformClosed

Abstract

Currently, there are three types of VNF "certification/validation" - VVP, as the initial ONAP VNF check based on HEAT, VNFSDK, being a more generic approach to VVP, and OPNFV. With dovetail, OPNFV introduced a framework that acts as a technical baseline for other compliance verification projects within the scope of the Linux Foundation Networking (LFN) umbrella project. In order to provide a platform that provides certification of VNFs against ONAP requirements the VNFSDK team already started to develop the VNF Test Platform (VTP). After discussing the scope of the VVP-Web proposal we discovered, that what we want to achieve is having the vvp-validation-scripts integrated into the such a VNF Test Platform, so vendors would not only validate against VNFSDK, but also against the vvp-validation-scripts covering even more checks.

The overall goal here is to provide a central VNF certification portal that holds the certification status of any VNF for any official requirements.

Rationale/Goals

  • Integrate the vvp-validation-scripts with the VNF Test Platform (VTP) suggested by the VNFSDK team.

    • integrate the vvp-validation-scripts test cases as a set of basic test cases that are applied to any VNF that gets validated by the VTP.

    • automate vvp-validation-script test runs if changes in the HEAT templates are detected.

    • execution of the vvp-validation-scripts could be done on the python test runner suggested by the VTP.

  • Provide a central VNF validation and certification portal for ONAP under the head of the OPNFV Verified Program.

Use Cases

ID

VVP-VTP-1

Title

VNF LFN certification

Description

VTP with integrated VVP validation

Primary Actor

LFN member

Preconditions

A VNF provider developed a VNF with unknown ONAP compliance.

Main Success Scenarios

  1. The VNF provider pushes his VNF to the VTP repository

  2. The test runs are automatically triggered

  3. The VNF is fully compliant regarding the checks done by the vvp-validation-scripts

  4. The VNF gets certified

Exception Scenarios

  1. The VNF provider pushes his VNF to the VTP repository

  2. The test runs are automatically triggered

  3. The VNF is not fully compliant regarding the checks done by the vvp-validation-scripts

  4. The VNF does not get certified

  5. The VNF provider has now the possibility to develop his VNF further using the VTP and gets feedback for every change done to the templates regarding the compliance to the VNF requirements.

Post Conditions

The VNF provider has an ONAP certified VNF.



Features

FeaureID

Description

Status

FeaureID

Description

Status

F-1

Implement the vvp-validation-scripts test cases into the VTPs "Test repository"

Dublin

F-2

Enable the VTP "python runner" to run the vvp-validation-scripts

Dublin



Extend the VTPs "VNF package repository" to enable the storage of VNF HEAT templates

Dublin

F-3

Extend the VTPs "Test center" to find VNF HEAT templates that should get tested with the vvp-validation-scripts inside the "VNF package and run them with the python runner

Dublin

F-4

Extend the VTPs "Test center" to enable the writeback of test results generated by the vvp-validation-scripts into the "test repository"

Dublin

F-5

Consider the VVP tests in the certification process on the OVP web portal when test results generated by VTP are uploaded

Dublin