The 4th ETSI Plugtests event is round the corner, and in this blog, I will explain how NFVI/VIM vendors, VNF vendors and hardware vendors can work with us to test ANOD (Aarna Networks ONAP Distribution) with their respective offerings at the Plugtests. This is the first time ONAP will be at a Plugtests, and we are very excited to gain end-to-end ONAP testing experience.
First, let us look at NFVI/VIM vendors. The Aarna Networks ONAP Distribution can be connected to any other Openstack/StarlingX deployment that complies to Ocata or later APIs. At the Plugtests, we would like to verify the interoperability with Openstack deployments from various NFVI/VIM vendors.
Next, let us look at VNF vendors. ANOD provides two orchestration paths (SO NFVO/gVNFM for Heat VNF descriptors and SO→VF-C NFVO for TOSCA VNF descriptors using an external sVNFM).
There are broadly 3 areas that need attention from VNF vendors’ point of view for onboarding their VNF’s onto ONAP.
Once the above steps are completed, we can work together with the VNF vendor to execute the official Plugtests test plan. The test plan can include an NFVI/VIM vendor or we can use the OPNFV scenario included with ANOD. Time permitting, we can also perform some closed-loop automation testing by creating a collector, analytics pipeline and a Policy.
The Plugtests can also be used to ensure that ONAP functionality is validated on the target hardware platform. This will involve deploying ANOD on the target servers, and using ONAP and Openstack (either the OPNFV scenario included with ANOD or from any other NFVI/VIM vendor) to test end to end functionality of deploying VNFs (open source or from one of the above vendors). This activity could bring all 4 players together - NFVI/VIM, VNF vendors and hardware vendors along with the Aarna Networks ONAP Distribution to execute the official Plugtests test plan.
