...
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.
...
(1) Currently, metadata values passed by the VSP package can contain values that are either not compliant with either general ONAP standards or not compatible with 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 repositories. Examples of metadata passed by the VSP to be checked for compliance against a specific deployment environment are:
- Compute flavour that is not flavor check as to whether it is supported by underlying NFV Infrastructure.
- The requirement for SR-IOV PCIe Pass through to a specific Network Interface Card that might not be availableas to whether that is available in the underlying NFV Infrastructure.
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.
...
- 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 queries to VTP or third, as well as to third-party repositories, to perform deployment environment checks.
- Integrating it into SDC will allow us to connect queries to industry standard certification program repositories such as OVP or third, as well as to 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.
...
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 (1) compliant to the specific deployment environment and (2) fetch prior certifications. The checks can be done by introducing a "registry" to be consulted during the VSP validation stage. 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 shows a query to a registry.
Figure 2: ONAP Component interaction with the proposed registry.
As outlined in the Rationale above, integrating these checks into SDC will allow queries to VTP and OVP, as well as to third-party repositories. Figure 3 below shows such checks specifically to VTP and OVP. Figure 4 below shows such the overarching VTP-based program for compliance, validations, and testing.
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.
...