This is a work in progress to define the minimum viable/valuable product (MVP) for a program to validate the life-cycle of a VNF running "in/with" ONAP.
The MVP definition should not discourage anyone from contributing to other projects or efforts related to VNF testing, but should help guide developer priorities for test frameworks.
Requirements & Deliverables
- The goal of the MVP is to specify a suite of VNF validation tests and associated test infrastructure that can be developed 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 i.e. a generic version of OpenStack. (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 current VNF criteria defined by ONAP for the initial release of VNF compliance testing.
- Testing uses existing interfaces into ONAP for stimulus / response to "drive" the tests (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 and test a VNF.
- ONAP deployment must be reproducible to 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 specifying VNF validation test purpose, implementation steps and pass/fail criteria.
- Definition of the set of ONAP components and their configuration required for the testing (ONAP profile used for testing).
- Definition of test infrastructure requirements needed for testing (i.e. hardware with compute / network / storage and 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).
EUAG Feedback
Please place your feedback here, as needed.
- abc
Timeline
Date | Deliverable |
---|---|
April 19, 2019 | MVP agreed by the CVC. |
April 23, 2019 | Presentation of MVP to LFN EUAG during teleconference |
End April | MVP agreed / finalized (feature freeze) |
Late April / Early May | Meetings with development/technical teams to determine what currently exists and what needs to be proposed as new work. |
Late May | Development plans finalized with technical teams. |
June 13, 2019 | ONAP E-release M1 |
June - July | VNF requirements created for life-cycle |
July 18, 2019 | ONAP E-release M2/M3 |
July | Test case development, per requirements set |
August | Test tooling development |
August 29, 2019 | ONAP E-release |
September | Beta testing from E-release, requirements frozen / completed, test case and tooling bug fixes only |
October | Beta conclusions, first VNFs publicly listed as passing the validation testing |