...
| Requirements No | Requirements Description | Implemented or Not In VNFSDK |
|---|---|---|
| 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,VNFMAYVNF Package Structure and Format | No |
| R-01123 | The VNF package Manifest file MUST contain: VNF package meta-data, a list of all artifacts (both internal and external) entry’s including their respected URI’s, an algorithm to calculate a digest and a digest result calculated on the content of each artifacts, as specified in ETSI GS NFV-SOL004. 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. | |
| R-21322 | The VNF provider MUST provide their testing scripts to support testing as specified in ETSI NFV-SOL004 - Testing directory in CSAR | |
| R-40820 | The VNF provider MUST enumerate all of the open source licenses their VNF(s) incorporate. CSAR License directory as per ETSI SOL004. for example ROOT\Licenses\ License_term.txt | |
| R-35854 | The VNF Descriptor (VNFD) provided by VNF vendor MUST comply with TOSCA/YAML based Service template for VNF descriptor specified in ETSI NFV-SOL001. Note: As the ETSI NFV-SOL001 is work in progress the below tables summarizes the TOSCA definitions agreed to be part of current version of NFV profile and that VNFD MUST comply with in ONAP Release 2+ Requirements. | |
| R-65486 | The VNFD MUST comply with ETSI GS NFV-SOL001 document endorsing the above mentioned NFV Profile and maintaining the gaps with the requirements specified in ETSI GS NFV-IFA011 standard. | |
| R-17852 | The VNFD MAY include TOSCA/YAML definitions that are not part of NFV Profile. If provided, these definitions MUST comply with TOSCA Simple Profile in YAML v.1.2. | |
| R-46527 | A VNFD is a deployment template which describes a VNF in terms of deployment and operational behavior requirements. It contains virtualized resources (nodes) requirements as well as connectivity and interfaces requirements and MUST comply with info elements specified in ETSI GS NFV-IFA 011. The main parts of the VNFD are the following:
Note: The deployment aspects (deployment flavour etc.) are postponed for future ONAP releases.
| |
| R-15837 | The table defines the major TOSCA Types specified in ETSI NFV-SOL001 standard draft. The VNFD provided by a VNF vendor MUST comply with the below definitions | |
| R-26885 | The VNF provider MUST provide the binaries and images needed to instantiate the VNF (VNF and VNFC images) either as:
Note: Currently, ONAP doesn’t have the capability of Image management, we upload the image into VIM/VNFM manually. | |
| 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 |
...