Today a VNF provider that wants to validate their HEAT templates has two options:

• Clone the vvp/validation-scripts repos and run the validations via the command line.
• Setup a broader, multi-container ecosystem to execute validations via a web portal.

The VVP-web should replace the broad, multi-container ecosystem with a simple one-click deployment that provides an easy to use web interface to upload and validate HEAT templates. It should not only validate one set of HEAT templates but further provide a version-controlled progress tracker that enables the team to directly map the changes done to the templates with the tests succeeded and failed. The progress tracker can also be useful when presenting progress to managers. Or for managers to follow the progress of the development of a VNF closely without having to deep dive into the technical aspects.