...
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, so . 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. Figure 3 shows the associated overarching LFN CVP vision and Figure 4 shows the vision of checks to VTP and OVP portal.
...
Figure 3: Overarching LFN CVP vision. Figure 4: Vision of checks to VTP and to OVP portal.
Impacts
Project | Usage | Impact |
External APIs |
| New API between plug-in and registry. During the Dublin development registry is considered outside of ONAP. |
Modeling | * Data Model for API between SDC plug-in and registry. * Data Model for NFVI content provisioned to registry. | To be checked: sufficiency of existing Modeling for Data Model needs. |
Portal | * Configuration of registry content to check against. * Presentation of diagnostic results of query to registry. | New fields in Portal screen. |
SDC | * Extraction of VNF template attributes and values. * Creation and sending query to registry. * Registry response processing. * Logging of query results. * Continuation or termination of SDC processing. | New functionality of plug-in. |
VNF Requirements |
| New VNF use cases, VNF requirements, VNF test cases. |
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.
...