This is a work in progress to define the minimum viable/valuable product for a program to validate the life-cycle of VNF running "in/with" ONAP.
The MVP definition does not prohibit anyone from contributing to other projects or efforts related to VNF testing, but should help set developer priorities.
Requirements & Deliverables
- The goal of the MVP is to develop validation testing within the time-frame of the E-release of ONAP.
- Tests will focus on on-boarding and instantiation of the VNF in/within ONAP.
- Tests will focus on HEAT based VNFs.
- Test will leverage the SDNC and APPC controllers.
- Tests will use the the VIM that is provided with ONAP (a future program update / release may migrate to other VIMs).
- VNFs are validated against the specific release of ONAP (i.e. VNF is validated against ONAP E-release or F-release).
- VNFs must also past the compliance testing (i.e. testing defined in the initial release of VNF testing).
- Testing uses existing interfaces into ONAP for stimulus / response to "drive" the test (i.e. avoid creating new requirements / interfaces for the ONAP at large project).
What is needed / Work to do
- ONAP release must be readily deploy-able, to allow a test framework to run on the deployment to test a VNF.
- Will ensure VNF tests are conducted in a uniform environment.
- Definition of life cycle requirements (i.e. what the test cases validate)
- Does instantiation include configuration?
- Does instantiation include health check?
- Test case description template for VNF validation work
- Definition of the set of ONAP components required for the testing (ONAP profile used for testing).
- Definition of requirements needed for testing (i.e. hardware / pod requirements to run testing).
- Test tooling that drives testing through existing ONAP interfaces.
Open Questions
- Can the test requirements or definitions (procedures) by pulled from, or reuse, the ETSI TST-0007
- What are the integration and testing interfaces that are currently available, i.e. used by the integration team / gating team?
Definition of Done / Success Measures
- Tests can readily be run, with high level of repeatability.
- Level of complexity is manageable by end users (i.e. ease of ONAP deployment + test cases).
Timeline
Date | Deliverable |
---|---|
April 19, 2019 | MVP agreed by the CVC. |
April 23, 2019 | Presentation of MVP to LFN EUAG during teleconference |
Early May | Discussions with ONAP Integration Team to understand what exists for testing today, and what needs to be developed. |
Need to insert ONAP E-release mile-stones here. | |