Page Status: Copied from R6 - Mar, 22, 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 Name | Interface Definition | Interface Capabilities | Version | Status | Consumed Models |
|---|---|---|---|---|---|
| xxxE-1 | External Interface Definition. | capabilities | x.y.z (according to strategy) | ||
| xxxI-2 | Internal interfaces if we want to raise them | Display and update: xxxxx |
Note: xxxI interface is a internal interface. xxxxE interface is a external interface
Template Component consumes the following Interfaces:
| Interface Name | Purpose Reason For Use | Version(s) |
|---|---|---|
| SDCE-6 | To Recieve the Control Loop Blueprint from SDCTo recieve | |
| PolicyE-2 | To create and configure the closed Loop Operational Policies | |
| DCAEE-x | Retrieve DCAE appplication status | |
| DCAEE-y | Deploy/remove DCAE application. |
3. Component Description:
A more detailed figure and description of the component.
<< link to project-specific description elsewhere >>
4. known system limitations
Architectural Technical Debt
Runtime: None
Clamp data redundancy is dependant on kubernetes and the persisten volume.
Clamp appliation redundancy HA reliease on kubernetes
5. System Deployment Architecture
FFS
6. New Release Capabilities
<< list the new capabilities that were introduced in this release, or a hot-link to the key features. New sub-chapter per release, as per a release notes document >>
7. References
- CLAMP Overview & User Guide: https://onap.readthedocs.io/en/latest/submodules/clamp.git/docs/index.html
- CLAMP internal interfaces: https://onap.readthedocs.io/en/latest/_downloads/d3c9f924c6586fe411d40a05ad9b1bb7/swagger.pdf