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.

Even when you use these options the errors reported can be difficult to decipher as there is no clean mapping between the validation failure and the specific requirement(s) violated.

Both of these options present their own unique barriers to entry. We'd like to eliminate these barriers and make it easy for anyone to download a simple tool, point it at your HEAT templates, and get an informative report to the specific errors that were encountered.

This approach will not eliminate the ability for users to execute validations from the command-line or be implemented in such a way that containerized versions ofthe validation scripts can be delivered.

This will simply be a convenience to ensure validations can be executed with a minimum amount of effort.