Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

VTP already provides required compliance test cases for TOSCA and HEAT based VNF. And this page provides the details on the LCM test cases required to on-board and instantiate VNF (TOSCA & HEAT) in ONAP. 

Problem Statement

https://wiki.lfnetworking.org/display/LN/VNF+Validation+Minimum+Viable+Product

Solution

ONAP VNF Test Platform (VTP) provides the required platform for deploying and excuting the required ONAP test cases,  which could be of nature compliance, Life-cycle and performance & functional as well. In dublin,  We have VVP and VNFSDK as apporved projects under ONAP, which handles the VNF related test cases for HEAT and TOSCA respectively and in dublin, we have unified the usage of these cases over VNF Test platform (VTP). This helps to run these test cases from where ever required, such as OVP,  ONAP SDC. During the ONS 2019 events, these integrations are demonstrated.  (in SDC for VSP compliance check before on-boarding the VNF and dovetail for running the test cases in ONAP for OVP). so VTP would be better option to run the LCM MVP test cases over ONAP. 

Complete Life-cycle actions of VNF

The Life-cycle of VNF invovles following actions

A. Desgin-Time Life cycle operations

  1. on-boarding of the VNF packages
  2. modeling

B. Run-Time Life cycle operations

  1. instantiation of the VNF
  2. Configuration of VNF
  3. upgrade of VNF
  4. Termination of VNF

C. Closed-Loop Life cycle operations

  1. Auto / Manual Healing
  2. Auto / Manual Scaling

Planned Life-cycle actions of VNF for LCM MVP

As part of requirement defined by CVC for LCM MVP,  A.1, A.2 and B.1 actions are required for both HEAT and TOSCA VNF.

Test case availability for LCM MVP actions

In dublin release, ONAP community enabled all required commands for doing end-end service provisioning as given below:

These commands are super set of required actions in LCM MVP.  And VTP has capability to directly consumes these commands as test cases, MVP could be achieved easily by levarging these commands in VTP.

ONAP does not provide option for end-user to instantiate VNF directly, but thru' Network Service (NS) via SO and E2E Service via VFC.  so VTP will perform instantiation of VNF using SO and VFC. 

How Heat based VNF is instatiated

The required commands for running the LCM MVP test cases are mentioned as part of the workflow given below for HEAT based ONAP ECOMP appr   oach.

 


Sample available here: https://github.com/onap/integration/blob/master/test/hpa_automation/heat/hpa_automation.py

As VTP could levarage each of these commands as test cases , all these test cases for LCM is available as it is 

How TOSCA based VNF is instatiated


Here, TBD commands to be implemented while others are already exists

Sample available here: https://github.com/onap/integration/blob/master/test/hpa_automation/tosca/hpa_automation.py 

As VTP could levarage each of these commands as test cases , all these test cases for LCM is available as it is 


LCM as one test case

Currently every action is available as indivual test cases and to run complete LCM operation including on-boarding and instantiation, this automation script to be modelled as test case, so complete LCM actions could be executed in one shot. so OVP can invoke these test cases either direclty invoking given LCM action or as a whole operation.


Demo

OVP LCM ONS EU demo 

  • No labels