Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Page Status: Copied from Guilin-R7 - Aug-24-2020
Component Status: Pending PTL updates and ArchCom Review

Last Reviewed on:


Certified by:

1. High Level Component Definition and Architectural Relationships (template)











































VVP provides the functionality to validate that a VNF Heat package is compliant with the ONAP VNF Heat Template Requirements from the ONAP VNFRQTS project. The ONAP VNF Heat Template Requirements are a set of restrictions and guidelines that a heat-based VNF must adhere to for ONAP compliance. ONAP compliance ensures a VNF can be properly modeled, instantiated, and inventoried by the ONAP platform.

The VVP validation-scripts is a set of python-based tests and are invoked by using pytest. Each test is marked with a specific requirement(s) from the VNFRQTS project. After executing the validation scripts, a validation report is constructed and provided to the user with details about each violation (if any). These details include the template the violation was found in, the test and module name, and the requirement number and text from the ONAP VNF Heat Template Requirements.

2. Template Component API definitions

Template Component provides the following interfaces:

Interface NameInterface Definition Interface CapabilitiesVersionStatusConsumed Models
vvpe-1Command line interface to execute the vvp validation scripts. 

Validates a VNF Heat Template package. Generates a violation report. Generates preload JSON files for modules if no violations are found.



None

Note:   xxxI interface is a internal interface.  xxxxE interface is a external interface

Template Component consumes the following Interfaces:

Interface NamePurpose Reason For UseVersion(s)


3. Component Description:

A more detailed figure and description of the component.

VVP Installation and User Guide

4. known system limitations

Architectural Technical Debt

Runtime: None.

5. System Deployment Architecture

None, VVP is run locally.

6. New Release Capabilities

None.

7. References

  1.  VVP Installation and User Guide



  • No labels