...
The breakdown of requirements by keyword is
| Row Labels | Count of ID |
| MAY | 73 |
| MAY NOT | 1 |
| MUST | 553 |
| MUST NOT | 81 |
| SHOULD | 78 |
| SHOULD NOT | 3 |
| Grand Total | 789 |
Scoring with simple counts of Met/Unmet will not be sufficient:
R-89571 provides for alternatives (one or more of) : Netconf/ Chef/ Ansible
Section 7.4 has MAY or SHOULD requirements which should not have the same weight as a MUST requirement.
The breakdown of requirements by target is
| Row Labels | Count of ID |
| PNF | 19 |
| VNF | 559 |
| VNF PACKAGE | 1 |
| XNF | 204 |
| XNF PROVIDER | 4 |
| (blank) | 2 |
| Grand Total | 789 |
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.
...
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 <20
Scoring with simple counts of Met/Unmet will not be sufficient:
R-89571 provides for alternatives (one or more of) : Netconf/ Chef/ Ansible
Section 7.4 has MAY or SHOULD requirements which should not have the same weight as a MUST requirement.
VNF Badging should avoid overlap/ duplication with VNF validation based on testing.
...
Eliminating the requirements that are inspectable in the xNF Package would reduce the number of requirements in the table above - ~30 of the 190 requirements are on the xNF or VNF Package ie ~15%
ONAP supports several different VNF Package formats for onboarding : HEAT based, TOSCA Based (VFC:Generic VNFM, VFC:SVNFM) and (Proposed for Dublin: Helm based ( see Req #1)). In Casablanca the number of Requirements & tests for these formats is:
| VNF Package format | No. Requirements | No. Tests |
|---|---|---|
| HEAT | 298 | |
| TOSCA | 11 | |
| HELM | 0 | 0 |
Some Analysis of candidates for VNF Badging are discussed below:
...