...
What is needed / Work to do Matrix
Test Life Cycle
| # | Step (Common) | HEAT Specific | TOSCA Specific |
|---|---|---|---|
| 1 | Initialize Vendor and Category Information | via SDC | N/A- already in SOL001 VNF Descriptor |
| 2 | Create the VSP in SDC | via SDC | via SDC |
| 3 | Upload Archive |
| Heat Archive | ETSI SOL004 CSAR |
| File | |||
| 4 | (Optional) Assign any Unassigned Files to Artifacts | via SDC | Error or warning since package should match manifest |
| 5 | Validate the VSP and ensure |
no Errors exist (warnings are OK) | via SDC | via VNFSDK | |
| 6 | Assign the Vendor License Model to the VSP (assumes a single VLM for testing purposes) | via SDC | via SDC |
| 7 | Create Virtual Function - Import the VSP (find using Name or ID from prior steps) | via SDC | N/A- already in SOL001 VNF Descriptor |
| 8 | Create Virtual Function - Set name of VF (auto-assign or make input into test script), contact and other required fields | via SDC | N/A- already in SOL001 VNF Descriptor |
| 9 | Create Service - Set Name (auto-assign based on VSP or make input into test script) | via SDC | via SDC |
| 10 | Create Service - Assign required or optional fields based on test script input | via SDC | via SDC |
| 11 | Create Service - Assign VF/VNF to the Service Model | via SDC | via SDC |
| 12 | Distribute the Service Model and validate successful Distribution | via SDC → DMaaP | via SDC → DMaaP |
| 13 | Submit Preloads | via SDNC | via |
| SDNC | |||
| 14 | Trigger Instantiation of Base Module from VID (NOTE: Need to see how we handle multi-module VNFs - presumably we can query this information and instantiate each individually) | via VID | via VID to SO & SOL003 adapter or VFC & SOL003 adapter |
| 15 | Verify successful instantiation |
Health-check TBD - needs further discussion
Items to do
Verify Heat Stack Create Successful Ping Ports on OAM network | Verify VNF created successfully Ping ports on OAM network |
Items to do
Based on a review with the ONAP Integration team the test suite Robot scripts provide the majority of the building blocks to perform the automation required for Heat-based VNFs this effort. There is still work to adapt the existing scripts to handle a generic VNF vs. the predefined demo VNFs currently used. The amount of effort on a per function basis as laid out in the table is not known at this time, but the overall effort does look to be achievable in the El Alto time frame.
| # | item | HEAT specifics |
|---|
| exist? | resources needed | TOSCA specifics | exist? | resources needed | |||
|---|---|---|---|---|---|---|---|
| 1 | Update VNFREQTS for LCM definition | Requirements for VNF "life-cycle" will be the same for HEAT / TOSCA. | 70% | VNFREQTS Team | Requirements for VNF "life-cycle" will be the same for HEAT / TOSCA. | 50% | VNFREQTS Team |
| 2 | Automation Script(s) to on-board VSP | Integration TestSuite | Yes | Contributions to Integration project by VVP team. | Victor: Investigating to reuse the existing scripts. | ~80% | VNFSDK Team |
| 3 | Automation Script(s) to Create VF | Integration TestSuite | Yes | Contributions to Integration project by VVP team. | Victor: Investigating to reuse the existing scripts. | ~80% | VNFSDK Team |
| 4 | Automation Script(s) to Create Service | Integration TestSuite | Yes | Contributions to Integration project by VVP team. | Victor: Investigating to reuse the existing scripts. | ~80% | VNFSDK Team |
| 5 | Automation Script(s) to Submit Preloads | Integration TestSuite | Yes | Contributions to Integration project by VVP team. | SDN-C Specific Operation: TOSCA could be ignored | N/A | |
| 7 | Automation Script(s) to Instantiate VNF | Integration TestSuite | Yes | Contributions to Integration project by VVP team. | Need to develop new scripts | No | VNFSDK Team |
| 8 | Automation Script(s) to Healthcheck VNF | N/A - not planned for this phase | N/A | Nice to have | N/A | ||
| 9 | Clean up after test(s) | Implemented directly in TestSuite | TestSuite Team | Implemented directly in TestSuite | TestSuite Team |
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?
...
| 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 |
External Resources
https://wiki.onap.org/display/DW/OVP+LCM+Support