...
- 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. (focus exclusively?)
- 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).
...
- 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 |
| 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 |