| Requirements No | Requirements Description | Implemented or Not |
|---|---|---|
| R-87234 | The VNF package provided by a VNF vendor **MAY** be either with TOSCA-Metadata directory (CSAR Option 1) or without TOSCA-Metadata directory (CSAR Option 2) as specified in ETSI GS NFV-SOL004. On-boarding entity (ONAP SDC) must support both options. **Note:** SDC supports only the CSAR Option 1 in Casablanca. The Option 2 will be considered in future ONAP releases, VNF MAY VNF Package Structure and Format | No |
| R-51347 | The VNF package **MUST** be arranged as a CSAR archive as specified in TOSCA Simple Profile in YAML 1.2. VNF MUST VNF Package Structure and Format | No |
| R-10087 | The VNF package **MUST** contain all standard artifacts as specified in ETSI GS NFV-SOL004 including Manifest file, VNFD (or Main TOSCA/YAML based Service Template) and other optional artifacts. CSAR Manifest file as per SOL004 - for example ROOT\\ **MainServiceTemplate.mf** VNF MUST VNF Package Contents | No |
R-02454 | The VNF MUST support the existence of multiple major/minor versions of the VNF software and/or sub-components and interfaces that support both forward and backward compatibility to be transparent to the Service Provider usage. | Yes |
| R-04298 | The xNF provider MUST provide their testing scripts to support testing. | Yes |
| R-07879 | The VNF Package MUST include all relevant playbooks to ONAP to be loaded on the Ansible Server. Note: Only applicable if the VNF providers claim this product support Chef, Ansible. | Yes |
| R-09467 | The VNF MUST utilize only NCSP standard computing resource profile (CPU, Disk, Memory, etc.) compute flavors. | Yes |
| R-13390 | The VNF Package MUST include a cookbook to be loaded on the appropriate server if the VNF is managed via Chef. Note: Only applicable if the VNF providers claim this product support Chef, Ansible. | Yes |
| R-23823 | The VNF Package MUST include appropriate credentials so that ONAP can interact with the Chef Server | Yes |
| R-26881 | The VNF provider MUST provide the binaries and images needed to instantiate the VNF (VNF and VNFC images). | Yes |
| R-27310 | The VNF Package MUST include all relevant Chef artifacts (roles/cookbooks/recipes) required to execute VNF actions requested by ONAP for loading on appropriate Chef Server. Note: Only applicable if the VNF providers claim this product support Chef, Ansible. | Yes |
| R-35851 | The VNF Package MUST include VNF topology that describes basic network and application connectivity internal and external to the VNF including Link type, KPIs, Bandwidth, latency, jitter, QoS (if applicable) for each interface. | Yes |
| R-40293 | The VNF MUST make available (or load on VNF Ansible Server) playbooks that conform to the ONAP requirement. Note: Only applicable if the VNF providers claim this product support Chef, Ansible. | Yes |
| R-43958 | The VNF Package MUST include documentation describing the tests that were conducted by the VNF provider and the test results. | Yes |
| R-66070 | The VNF Package MUST include VNF Identification Data to uniquely identify the resource for a given VNF provider. The identification data must include: an identifier for the VNF, the name of the VNF as was given by the VNF provider, VNF description, VNF provider, and version. | Yes |
| R-77707 | The VNF provider MUST include a Manifest File that contains a list of all the components in the VNF package. | Yes |
| R-77786 | The VNF Package MUST include all relevant cookbooks to be loaded on the ONAP Chef Server. Note: Only applicable if the VNF providers claim this product support Chef, Ansible. | Yes |
Overview
Content Tools