Brief Project Overview (brief as it should be known)
In ONAP, as part of Container Network Function (CNF) support, its mandatory to add enable the following testing/validation to make sure the given CNF is as per the need.
Design Time validation: When Operator on-board CNF as VSP in SDC, Operator wants to check the given CNF is confromance to their Operator Specific compliance such as security policies
Run time validation: Once CNF is provisioned in ONAP, it needs to be validated for sanity check and required functioanlity check.
Support LFN OVP 2.0 to support CNF conformance and CNF on-boarding vadlidations. (pre-on-boarding time)
More Details: OVP 2.0 CNF support in ONAP
New component capabilities for Guilin, i.e. the functional enhancements, if applicable
- Add cnf conformance check support inline with CNF support functioanilty enabled in this release
New or modified interfaces
cnf-compliance-check - supports to check the CF conformance
If they are modified, are they backwards compatible?
Interface naming (point to an example)
Consumed API from other projects
Project | API Dependency | Notes |
|---|---|---|
Published API
Project | API | Notes |
|---|---|---|
Reference to the interfaces.
(Reference to the the swagger.json file(s) whenever possible)
What are the system limits?
.
Involved use cases, architectural capabilities or functional requirements.
OVP 2.0 and Test Automation
Listing of new or impacted models used by the project (for information only).
(list all the relevant Jira tickets)