Requirement:

ONAP is a system focused on automating the management of vNF. As such it is interested in the O&M interfaces of the vNF's much more than the traffic interfaces. 

In order to test all the functionality of ONAP it must be possible to fulfill all the O&M interfaces of the vNF. It would be better if this could be done  independently of the actual vNFs so that the ONAP functionality can be tested independently of the vNF as the vNF will usually be more focused on traffic functionality.

Also ONAP needs a way to simulate many different error scenarios which will be very difficult to reproduce using "real" vNFs

ONAP also needs to be able to test against 1000's of vNF's which will not be possible to simulate using real vNFs for cost and capacity reasons.

ONAP also needs a way to demonstrate to vendors what are the O&M capabilities required from a vNF as documented in the VNF requirements/VNF SDK

A list of possible requirements for this dummy vNF are below

1.It could be started by heat template

2.It could be started by a TOSCA template

3.It should provide a defined Netconf Yang interface that works towards APPC

4. It should be able to send Alarms to the VesCollector

5. It should send PM events to the VesCollector

6. It should fulfill the LCM functions required by the VNF requirements restart/vm restart etc

7. It should be possible to schedule the sending of events 

8. It should be possible to configure what events are send.

9. It should be possible to add new Yang Models and get defined responses.

10. It should be possible to configure faulty responses to requests.

 11. It must be possible to deploy 1000's of the nodes with low resource usage.

 

This VNF does not negate the need for the vFW/vLB VNFs as currently produced. This VNFs are essential for the next level of tests i.e. that the VNFs deployed can actually execute full traffic.