| Status | Choose One: DRAFT |
|---|---|
| Submitter | Abdel Rabi (Vodafone) |
| Contributors | Names of additional contributors |
| Proposed Release | Dublin Release |
| JIRA Ticket(s) | Each proposal should have at least 1 JIRA ticket for tracking purposes. |
Abstract
Currently, Metadata values passed by VSR package can contain values that are either not compliance to ONAP standards or not compatible with the installed VID environment that can lead to deployment failures. This proposal proposes to add dynamic checks within SDC to be able to check passed metadata values against a registry that contains the check criteria. the content of the registry can be pre-loaded with standard static criteria, but also can be configured to add custom checks that are related to specific VID deployments.
Rationale
Reducing the risk of VNFs failing to be deployed in a given Virtualization infrastructure deployment can be achieved by checking the metadata passed by the VSP against a defined criteria (both coming as part of a standard, and also configured for a specific environment).
Examples of metadata to be cheeked:
- Compute flavor that is not supported by underlying VID.
- Requirement for SR-IOV PCIe Pass thought to specific Network Interface Card that might not be available.
Other Options Considered
It has been considered that this 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.
- The potential of integrating it into SDC will allow us to connect to industry standard certification programs repositories such as OVP or third party repositories to perform extra checks before on boarding which will minimize the local tests required (or even be skipped completely)
- Integrating it into SDC will allow for better integration with CI/CD tools and automate the compliance checks especially when rolling out VNFs updates.
Code Structure
ONAP code can be found in: https://git.onap.org/
Proposal
From a high level prospective, the proposal will allow VSP, when uploaded into SDC, to go through set of checks to make sure it is compliant to ONAP platform in general and to the deployed VID in specific. Figure 1 below shows the proposal in a high level view.
Figure 1: High Level proposal.
The check itself can be done by intruding a compliance criteria "registry" will be consulted during the VSP validation stage. The validation block sends all passed metadata 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.
References
Links to any addtional resources referenced in or related to this proposal.