VSP Compliance Check within SDC (Dublin)

Overview

Abstract

This proposal is to add dynamic checks within SDC to (1) Query a certification repository such as OVP to what certification a VNF has undergone and (2) invoke VTP to run custom Ad-hoc testing (checks) against VSP (VNF)  prior accepting the VSP (VNF). 

Rationale

1. Industry standard certification program repositories such as the OVP portal or third-party repositories can be checked in order to minimize or even remove the need for local testing. The first part of this proposal is to add the support within SDC to query a certification repository.
2. Currently, metadata values passed by the VSP package can contain values that are not compliant with either general ONAP requirements or specific requirements of the CSP installed deployment environment. That can lead to VNF deployment failure. Reducing the risk of such failure can be achieved by checking the metadata passed by the VSP against criteria in VTP or third-party testing frameworks. Examples of metadata passed by the VSP to be checked for compliance against a specific deployment environment are:

• • Compute flavor check as to whether it is supported by underlying NFV Infrastructure.
  • SR-IOV PCIe Pass through to a specific Network Interface Card as to whether that is available in the underlying NFV Infrastructure.

This second part of the proposal will add a capability within SDC to perform custom tests against a given VSP (VNF). This can be done by invoking VTP framework to run that tests and get the result back into SDC,

Other Options Considered

It has been considered that these compliant checks can be carried out offline but this will be restrictive in the following way:

• It is a big overhead to carry out those checks offline especially as VID deployments might vary from one instance of ONAP to another and hence the compliance criteria will change.
• Integrating it into SDC will allow queries to industry standard certification program repositories such as the OVP portal, as well as to third-party repositories, to perform certification checks.
• Integrating it into SDC will allow queries to VTP, as well as to third-party repositories, to perform deployment environment checks.
• Integrating it into SDC will allow for better integration with CI/CD tools and automate the checks, especially when rolling out VNF updates.

Code Structure

ONAP code can be found in: https://git.onap.org/

Will follow soon.

Proposal

From a high-level perspective, the proposal will allow VSP, when uploaded into SDC, to go through a set of checks to make sure it (1) has gone though certifications process and the result is satisfactory. (2) is compliant to the deployment environment and custom requirements.

Those checks can be done during the VSP validation stage by implementing plug-ins to SDC and introducing both a "certification repository" and a testing framework to be consulted. Figure 1 shows the proposal in a high-level view. 

Figure 1: High-Level proposal.

As outlined in the Rationale section above, integrating these checks into SDC will allow queries to VTP and the OVP portal as well as to third-party repositories. Thus the APIs will be designed to interoperate SDC with that range of end-points. In order to meet the Dublin release schedule for the development of  plug-ins and APIs, a registry is planned to be implemented as a discrete hosted component outside ONAP. Integration to VTP and OVP portal can be performed when those environments are ready. 

Impacts

References

Links to any additional resources referenced in or related to this proposal.

VTP New API changes for this 

VNF Test Platform (VTP)

Project Action Log 

		Cloud & Automation E2E
ID (Unique Ref.)	Origin	Workstream \ Area	Detail	Dependency	Assigned To (Responsible)	Date Raised (Meeting Date)	Due Date	Date Closed	Status	Critical Path Y\N	Update \ Comment
1	WorkShop (15/01/19)	Technical	Arrange meting with VTP PTL to understand if they can act as a broker and iConnective registry and be the main end point (also retain API Specs, can I use inside or outside, suncrouns vs async)		Bryan	15/01/2019	19/01/2019		Open
2	WorkShop (15/01/19)	Technical	Need to discuss whether the call can be aync or sync, PUB SUB or what ?	1	Bryan	15/01/2019	19/01/2019		Open
3	WorkShop (15/01/19)	Technical	Need to discuss the UI and subsequent approval of user experience with PTL of SDC and PTL of VTP		Prabhu Balan	15/01/2019			Open		15/01/19 : Prabhu to provide a proposal for UI and to present this to SDC team to approve
4	WorkShop (15/01/19)	Project Management	Forward all SDC meetings to Prabhu		Susan	15/01/2019			Open		15/01/19 : Susan from iconetiv and prabhu from vodafone to attend weekly SDC meetings.
5	WorkShop (15/01/19)	Technical	Find the VTP API specification to keep the experience similar to what it is today	1	Bryan	15/01/2019			Open
6	WorkShop (15/01/19)	Project Management	We need to define a way of working and list of stories that can be delivered in Dublin			15/01/2019			Open
7	WorkShop (15/01/19)	Technical	Atul to come up with an example document to come up with a user story -> user manual -> user guide		Atul	15/01/2019			Open
8	WorkShop (15/01/19)	Documentation	Documentation for the E2E scenario that goes live with Release D –we need to discuss the delivery milestone (what EPIC it relates to etc)	7	Everyone	15/01/2019			Open
9	WorkShop (15/01/19)	Technical	What parser we need to use – J-PARSER ?, is that a wrapper called SDC TOSCA Parser ? need to talk to VNF SDK PTL, reason is there are two parsers, one for package and other for payload – Viktor Gao?		Susan, Martin	15/01/2019			Open
10	WorkShop (15/01/19)	Project Management	agree framework and Setup scrum meetings		David, Robin	15/01/2019		21/01/2019	Closed
11	WorkShop (15/01/19)	Lab Management	Give lab access to iconectiv		Prabhu Balan	15/01/2019	18/01/2019	16/01/2019	Closed
12	WorkShop (15/01/19)	Lab Management	Instructions of how to upload to lab and use it.		Prabhu Balan	15/01/2019	18/01/2019	16/01/2019	Closed
13	WorkShop (15/01/19)	Communications	Slide update to inlcue VTP as a broker		Bryan	15/01/2019	19/01/2019	15/01/2019	Closed
14	WorkShop (15/01/19)	Technical	update impact table in wiki		Bryan	15/01/2019	19/01/2019	15/01/2019	Closed
15	WorkShop (15/01/19)	Documentation	Present slides to SDC on Tuesday 15th		Bryan + Rabi	15/01/2019			Open
16	WorkShop (15/01/19)	Project Management	Keep/Upload this sheet in ONAP wiki		Rabi	15/01/2019		15/01/2019	Closed
17	WorkShop (15/01/19)	Project Management	David and Robin to figure out a plan for syncing delivaries, etc.		David, Robin	15/01/2019			Open
18	WorkShop (15/01/19)	Technical	Create JIRA stories in ONAP Jira		Susan	15/01/2019			Open
19	WorkShop (15/01/19)	Technical	Confirm with Offir what he needs from us by the deadline.		Susan	15/01/2019			Open
20	WorkShop (15/01/19)	Technical	Add workflows into Sprints and share with vodaofne to confirm.		Bryan	15/01/2019	20/01/2019		Open		15/01/19 :  Bryan to flesh out sprints and share with vodafone in next Monday meeitng to confirm
21	WorkShop (15/01/19)	Testing	Unit testing for BES		iconectiv	15/01/2019			Open
22	WorkShop (15/01/19)	Testing	Unit testing for Fes		Vodafone	15/01/2019			Open
23	WorkShop (15/01/19)	Testing	E2E test		?	15/01/2019			Open		15/01/19 :  need to create that before deadline of commiting code. Do we need one.
24	WorkShop (15/01/19)	Technical	CI/CT & CI/CD		Prabhu Balan	15/01/2019			Open
25	WorkShop (15/01/19)	Technical	Code commit and upstream		Vodafone	15/01/2019			Open
26	WorkShop (15/01/19)	Project Management	Timeline Creation		David, Robin,	15/01/2019			Open
27