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 

1. 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.
2. Tests will focus on on-boarding and instantiation of the VNF in/within ONAP.
3. Tests will focus on HEAT based VNFs.
4. Test will leverage the SDNC and APPC controllers.
5. 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).
6. VNFs are validated against the specific release of ONAP (i.e. VNF is validated against ONAP E-release or F-release).
7. VNFs must also past the current VNF criteria defined by ONAP for the initial release of VNF compliance testing.
8. 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

1. ONAP release must be readily deploy-able, to allow a test framework to run on the deployment and test a VNF.  
2. ONAP deployment must be reproducible to ensure VNF tests are conducted in a uniform environment.
3. Definition of life cycle requirements (i.e. what the test cases validate)
   1. Does instantiation include configuration?
   2. Does instantiation include health check?
4. Test case description template for specifying VNF validation test purpose, implementation steps and pass/fail criteria.
5. Definition of the set of ONAP components and their configuration required for the testing (ONAP profile used for testing).
6. Definition of test infrastructure requirements needed for testing (i.e. hardware with compute / network / storage and pod requirements to run testing).
7. Test tooling that drives testing through existing ONAP interfaces.

Open Questions

1. Can the test requirements or definitions (procedures) by pulled from, or reuse, the ETSI TST-0007
2. 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

1. Tests can readily be run, with high level of repeatability.
2. 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.

1. Feedback from CMCC: The VNFD we are using in our company are all TOSCA-based. Also, we are using VFC for VNF LCM. We suggest to update the 3rd item and the 4th item in "Requirements & Deliverables" to  "Tests will focus on HEAT based VNFs and TOSCA based VNFs" and "Test will leverage the SDNC, APPC and VFC controllers".
2. Verizon feedback: As mentioned in the comment below we we are using TOSCA based VNF-D as well. We would like to extend the requirements to include SOL004/SOL001 VNFs using the SDC→SO→SOL003 Adapter → External VNFM→VNF path or the SDC → SO → SOL005 Adapter → VF-C → VNF path.
3. China Telecom Feedback：We have both HEAT based and TOSCA based VNFDs in the DEMO running on our testbed. It will be great if TOSCA based VNFs could be added in the Requirement, providing the resources are available.
4. ChinaUnicom Feedback： Our company also has the strong demands for TOSCA based VNF and we hope that it could be included into the scope.

Timeline