| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
- How long the project has been an active: Since 05/30/2017
- Release Participation: Beijing, Casablanca, Dublin, El Alto, Frankfurt
- Engagement levels for past releases (up to 3):
- Commits per Release:
- Contributors per Release:
- Companies per release:
- Use Cases:
| Release name and timeframe | Commits | Authors |
|---|---|---|
| Beijing | 118 | 11 |
| Casablanca | 66 | 5 |
| Dublin | 81 | 5 |
| El Alto | 48 | 6 |
| Frankfurt | 64 | 6 |
Architecture Alignment:
- None
Artifact Information:
- The VVP code and test-cases are primarily in the following 2 repos:
https://gerrit.onap.org/r/admin/repos/vvp/validation-scripts
https://gerrit.onap.org/r/admin/repos/vvp/test-engine
Documentation is available here:
https://docs.onap.org/projects/onap-vvp-documentation/en/latest/index.html#master-index
- VVP is not part of integration testing because it is not integrated with the rest of the platform.
- VVP is used internally at AT&T to validate VNFs are compliant with the ONAP VNF Heat Template Requirements. It has also been used by many others as a tool when writing VNF Heat Templates for ONAP, including the templates that are part of the integration/robot demos.
Other Information:
- VVP is also the home for the OVP VNF Life-Cycle Validation Badging, which has been used to badge several vendor Heat-based VNFs.