VSP Compliance Check within SDC (Dublin)

Table of Contents:

Abstract

This proposal is to add dynamic checks within SDC to (1) check compliance with deployment environment criteria, in order to reduce deployment failures; and (2) check for prior certifications, to eliminate unnecessary tests during onboarding.

Rationale

(1) Currently, metadata values passed by the VSP package can contain values that are either not compliant with ONAP standards or not compatible with 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 repositories. Examples of metadata passed by the VSP to be checked for compliance against a deployment environment are:

• Compute flavour that is not supported by underlying NFV Infrastructure.
• The requirement for SR-IOV PCIe Pass through to a specific Network Interface Card that might not be available.

This proposal will add dynamic checks within SDC against a registry that contains deployment environment criteria. Both standard static criteria and specific deployment environment criteria will be configurable.

(2) 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.

This proposal will add dynamic checks within SDC against a registry that contains prior certifications.

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 us to connect to VTP or third-party repositories to perform deployment environment checks.
• Integrating it into SDC will allow us to connect to industry standard certification program repositories such as OVP or third-party repositories to perform certification checks.
• Integrating it into SDC will allow for better integration with CI/CD tools and automate the compliance 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 is compliant to ONAP platform in general and to the specific deployment environment. Figure 1 below shows the proposal in a high-level view. 

Figure 1: High-Level proposal.

The check itself can be done by introducing a compliance criteria "registry" to be consulted during the VSP validation stage. The validation block sends all passed metadata to the registry and gets the result of compliance checks back. The result of the compliance checks will determine if the VSP needs to be rejected or to be submitted to testing.

Figure 2: ONAP Component interaction with the proposed registry.

Metadata Tags

We need an agreed list of metadata tags plus a list of the values those tags can take in order to effect compliance checks.

Tags should include the ETSI NFV SOL1 data items in the VNFD – if ETSI says some of these are optional and we think they should be mandatory then we should say so.

References

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