...
The objective is to extract / summarize VNF Requirements into a VNF Badge. The VNF Requirements were original developed as prototype RFP text. Not all of the Requirements are testable ( either currently or in the near future).ONAP VNF Requirements evolve with ONAP releases. ( See e.g. Casablanca release notes ). The test implementations are also expected to evolve with ONAP releases. The VVP project is implementing HEAT related test scripts. The VNFSDK project is implementing TOSCA based test scripts. Test scripts may be invoked in a variety of different use cases. The proportion of testable requirements having tests implemented is expected to increase with each ONAP release. The scope of testing is expected to evolve from onboarding (Package inspection), to Life Cycle operations and Functional testing. In Casablanca test descriptions are available for VNF Package inspection tests. Test Case Descriptions for Life Cycle operations may be candidate work items for future releases.
The specific badge would need to be aligned with the LFN guidance on logos, but something along the following lines may be a place to start.
There is some discretion to adjust portions of the logo to reflect the scope of the assurance proposed by the badge. This example proposes a scope around "VNF Management" but other scopes may be possible. More than one badge may be possible if the material is sufficiently independent. The "2018.11" reflects the ONAP release which provides the conformance reference for the badge. VNF Badging should avoid overlap/ duplication with VNF validation based on testing, ideally the two should be linked.
One approach is to use a format similar to the CII Badging website see e.g. CII Badge for VVP. There are some differences for VNF badging vs CII badging ( beyond the obvious subject matter). This would allow human entered data to be supplemented by automated test results (e.g. from the Dovetail framework).
...
As an initial target, it has been proposed to focus on the requirements associated with VNF Management (i.e. Chapter 7 of the ONAP VNF Requirements) . This Chapter 7 represents ~190 of the >750 requirements ie ~25% of the VNF requirements identified.
The specific badge would need to be aligned with the LFN guidance on logos, but something along the following lines may be a place to start.
The current CII badge has ~70 requirements, in 6 pulldown menus. The max requirements in a pulldown is 16.
For usability, we should constrain the number of pulldowns and the number of requirements per pulldown to a similar order of magnitude e.g. pulldowns < 10, reqts/pulldown <20VNF Badging should avoid overlap/ duplication with VNF validation based on testing.
VNF Package Inspection
VNF Test Case Descriptions are provided for VNF Package Inspection from Bejing.
...