...
- 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)
- Both HEAT & TOSCA
What does a mean (formally for a test case requirement) to "instantiate" (or startup) a VNF?
Info from Victor, Definition of VNF onboarding
- Verify the VNF package by using VNFSDK compliance check test cases.
- upload a VNF package to ONAP system
- verify the VNF Package already exist on the ONAP system.
- Verify the VNF package by using VNFSDK compliance check test cases.
Info from Victor, Definition of VNF instantiation.
Trigger an "instantiate VNF" operation to Controller
verify that the requested grant for the "instantiate VNF" operation has been approved by the controller
VNF related software images have been successfully added to the image repository managed by the VIM or already exist on the VIM system.(Currently, ONAP is manually doing this.)
Verify that the requested virtualised resources have been allocated by the VIM according to the VNFD
Verify that virtualised resource allocation constraints have been met by querying the VIM
Verify that any existing virtualised resources have not been affected by the allocation of the new virtualised resources by querying the VIM
Verify that the VNF instance resources are visible on the controller
- Does instantiation include configuration?
- both heat and Tosca template could include the inject-file/user-data(cloud-init) as the day0 configuration file of a VNF.
- Does instantiation include health check?
- Yes, we could use the query interface (query the VNF detail info) to implement the health-check func.
- HEAT
- Trevor Lovett & Ryan Hallahan will help with this.
- TOSCA
- Weitao Gao will help with this.
Info from Victor, Definition of VNF instantiation.
Trigger an "instantiate VNF" operation to Controller
verify that the requested grant for the "instantiate VNF" operation has been approved by the controller
VNF related software images have been successfully added to the image repository managed by the VIM or already exist on the VIM system.(Currently, ONAP is manually doing this.)
Verify that the requested virtualised resources have been allocated by the VIM according to the VNFD
Verify that virtualised resource allocation constraints have been met by querying the VIM
Verify that any existing virtualised resources have not been affected by the allocation of the new virtualised resources by querying the VIM
Verify that the VNF instance resources are visible on the controller
- 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.
- HEAT
- TOSCA
- Both HEAT & TOSCA
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.
- 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".
- 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.
- 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.
- 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
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 |
...