| R # | R Text | VNF Package Requirement | Test exists in VNFSDK, VVP or SDC for Beijing release |
| R-01478: | The VNF Package MUST include documentation describing all parameters that are available to monitor the VNF after instantiation (includes all counters, OIDs, PM data, KPIs, etc.) that must be collected for reporting purposes. The documentation must include a list of: | Y | N |
| R-01556: | The VNF Package MUST include documentation describing the fault, performance, capacity events/alarms and other event records that are made available by the VNF. The document must include: | Y | N |
| 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. | N | N |
| R-03070: | The VNF MUST, by ONAP Policy, provide the ONAP addresses as data destinations for each VNF, and may be changed by Policy while the VNF is in operation. We expect the VNF to be capable of redirecting traffic to changed destinations with no loss of data, for example from one REST URL to another, or from one TCP host and port to another. | N | |
| R-04298: | The VNF provider MUST provide their testing scripts to support testing. | Y | Y |
| R-07879: | The VNF Package MUST include all relevant playbooks to ONAP to be loaded on the Ansible Server. | Y | N |
| R-09467: | The VNF MUST utilize only NCSP standard compute flavors. [5] | N | |
| R-13390: | The VNF provider MUST provide cookbooks to be loaded on the appropriate Chef Server. | Y | N |
| R-16065: | The VNF provider MUST provide configurable parameters (if unable to conform to YANG model) including VNF attributes/parameters and valid values, dynamic attributes and cross parameter dependencies (e.g., customer provisioning data). | Y | N |
| R-16560: | The VNF MUST conduct a resiliency impact assessment for all inter/intra-connectivity points in the VNF to provide an overall resiliency rating for the VNF to be incorporated into the software design and development of the VNF. | N | |
| R-16777: | The VNF provider MUST provide a JSON file for each supported action for the VNF. The JSON file must contain key value pairs with all relevant values populated with sample data that illustrates its usage. The fields and their description are defined in Appendix B. | Y | N |
| R-18525: | The VNF provider MUST provide a JSON file for each supported action for the VNF. The JSON file must contain key value pairs with all relevant values populated with sample data that illustrates its usage. The fields and their description are defined in Appendix A. | Y | N |
| R-22888: | The VNF provider MUST provide documentation for the VNF Policy Description to manage the VNF runtime lifecycle. The document must include a description of how the policies (conditions and actions) are implemented in the VNF. | Y | N |
| R-23823: | The VNF Package MUST include appropriate credentials so that ONAP can interact with the Chef Server. | Y | N |
| R-25238: | The VNF PACKAGE MUST validated YANG code using the open source pyang [3] program using the following commands: | Y | N |
| R-26567: | The VNF Package MUST include a run list of roles/cookbooks/recipes, for each supported VNF action, that will perform the desired VNF action in its entirety as specified by ONAP (see Section 8.c, ONAP Controller APIs and Behavior, for list of VNF actions and requirements), when triggered by a chef-client run list in JSON file. | Y | N |
| R-26881: | The VNF provider MUST provide the binaries and images needed to instantiate the VNF (VNF and VNFC images). | Y | Y |
| 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. | Y | N |
| R-27711: | The VNF provider MUST provide an XML file that contains a list of VNF error codes, descriptions of the error, and possible causes/corrective action. | Y | N |
| R-30278: | The VNF provider MUST provide a Resource/Device YANG model as a foundation for creating the YANG model for configuration. This will include VNF attributes/parameters and valid values/attributes configurable by policy. | Y | N |
| R-30654: | The VNF Package MUST have appropriate cookbooks that are designed to automatically ‘rollback’ to the original state in case of any errors for actions that change state of the VNF (e.g., configure). | Y | N |
| R-33280: | The VNF MUST NOT use any instance specific parameters in a playbook. | ||
| 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. | Y | Partial Currently, VNF Package already have the topology of basic network and CP (both internal and external). |
| R-36280: | The VNF provider MUST provide documentation describing VNF Functional Capabilities that are utilized to operationalize the VNF and compose complex services. | Y | N |
| R-37028: | The VNF MUST be composed of one “base” module. | N | |
| R-37692: | The VNFC MUST provide API versioning to allow for independent upgrades of VNFC. | Y | N |
| R-40293: | The VNF MUST make available (or load on VNF Ansible Server) playbooks that conform to the ONAP requirement. | Y | N |
| R-40827: | The VNF provider MUST enumerate all of the open source licenses their VNF(s) incorporate. | Y | N |
| R-41215: | The VNF MAY have zero to many “incremental” modules. | Y | N |
| R-43958: | The VNF Package MUST include documentation describing the tests that were conducted by the VNF provider and the test results. | Y | N |
| R-46567: | The VNF Package MUST include configuration scripts for boot sequence and configuration. | Y | N |
| R-48596: | The VNF Package MUST include documentation describing the characteristics for the VNF reliability and high availability. | Y | N |
| R-56815: | The VNF Package MUST include documentation describing supported VNF scaling capabilities and capacity limits (e.g., number of users, bandwidth, throughput, concurrent calls). | Y | N |
| R-58775: | The VNF provider MUST provide software components that can be packaged with/near the VNF, if needed, to simulate any functions or systems that connect to the VNF system under test. This component is necessary only if the existing testing environment does not have the necessary simulators. | Y | N |
| 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. | Y | Y |
| R-69565: | The VNF Package MUST include documentation describing VNF Management APIs. The document must include information and tools for: | Y | N |
| R-72184: | The VNF MUST have routable FQDNs for all the endpoints (VMs) of a VNF that contain chef-clients which are used to register with the Chef Server. As part of invoking VNF actions, ONAP will trigger push jobs against FQDNs of endpoints for a VNF, if required. | Y | N |
| R-73364: | The VNF MUST support at least two major versions of the VNF software and/or sub-components to co-exist within production environments at any time so that upgrades can be applied across multiple systems in a staggered manner. | Y | N |
| R-74763: | The VNF provider MUST provide an artifact per VNF that contains all of the VNF Event Records supported. The artifact should include reference to the specific release of the VNF Event Stream Common Event Data Model document it is based on. (e.g., VES Event Listener) | Y | Y |
| R-77707: | The VNF provider MUST include a Manifest File that contains a list of all the components in the VNF package. | Y | Y |
| R-77786: | The VNF Package MUST include all relevant cookbooks to be loaded on the ONAP Chef Server. | Y | N |
| R-78010: | The VNF MUST use the NCSP’s IDAM API for Identification, authentication and access control of customer or VNF application users. | N? | |
| R-81777: | The VNF MUST be configured with initial address(es) to use at deployment time. After that the address(es) may be changed through ONAP-defined policies delivered from ONAP to the VNF using PUTs to a RESTful API, in the same way that other controls over data reporting will be controlled by policy. | Y | N |
| R-84366: | The VNF Package MUST include documentation describing VNF Functional APIs that are utilized to build network and application services. This document describes the externally exposed functional inputs and outputs for the VNF, including interface format and protocols supported. | Y | N |
| R-86758: | The VNF SHOULD provide an automated test suite to validate every new version of the software on the target environment(s). The tests should be of sufficient granularity to independently test various representative VNF use cases throughout its lifecycle. Operations might choose to invoke these tests either on a scheduled basis or on demand to support various operations functions including test, turn-up and troubleshooting. | Y | |
| R-96634: | The VNF provider MUST describe scaling capabilities to manage scaling characteristics of the VNF. | Y | N |
| R-97102: | The VNF Package MUST include VM requirements via a Heat template that provides the necessary data for: | Y | TBD |
| R-98617: | The VNF provider MUST provide information regarding any dependency (e.g., affinity, anti-affinity) with other VNFs and resources. | Y | N |
| R-99771: | The VNF MUST provide all code/configuration files in a “Locked down” or hardened state or with documented recommendations for such hardening. All unnecessary services will be disabled. VNF provider default credentials, community strings and other such artifacts will be removed or disclosed so that they can be modified or removed during provisioning. | N | |
| R-nnnnn:** | The VNF MUST have a corresponding environment file for a Cinder Volume Module. | N | |
| R-43125 | R-43125 The VNF Heat **MUST** indent properties and lists with 1 or more spaces. | ||
| R-67888 | R-67888 The VNF Heat **MUST** contain the following | ||
| R-39402 | R-39402 The VNF Heat **MUST** contain the description section. | ||
| R-35414 | R-35414 The VNF Heat **MUST** contain the parameter section. | ||
| R-90279 | R-90279 The VNF Heat **MUST** use in a resource all parameters declared in a template | ||
| R-28657 | R-28657 The VNF Heat **MUST** provide the attribute 'type' on parameters per the OpenStack Heat | ||
| R-44001 | R-44001 The VNF Heat **MUST** provide the attribute 'description' on parameters. (Note that | ||
| R-90526 | R-90526 The VNF Heat **MUST NOT** use the attribute 'default'. | ||
| R-88863 | R-88863 The VNF Heat **MUST** have a constraint of range or allowed\_values for a parameter type 'number'. | ||
| R-23664 | R-23664 The VNF Heat **MUST** have a resources: section with the decleration of at least one resource. | ||
| R-16447 | R-16447 The VNF Heat **MUST** have unique resource IDs across all Heat | ||
| R-97199 | R-97199 The VNF Heat **MUST** use the metadata property for OS::Nova::Server resource type. | ||
| R-03324 | R-03324 The VNF Heat **MUST** contain the following sections in the environment file: | ||
| R-19473 | R-19473 The VNF Heat **MUST** include “base� in the filename for the base module | ||
| R-81339 | R-81339 The VNF Heat **MUST** match one of the following options for the base module file name: | ||
| R-91342 | R-91342 The VNF Heat **MUST** name the base module’s corresponding environment file to be identical | ||
| R-87247 | R-87247 The VNF Heat **MUST NOT** use any special characters or the word “base� in the name of the incremental module. | ||
| R-94509 | R-94509 The VNF Heat **MUST** name the incremental module’s corresponding environment file to be | ||
| R-82732 | R-82732 The VNF Heat **MUST** name the Cinder volume module file name to be the same as the | ||
| R-31141 | R-31141 The VNF Heat **MUST** name the volume module’s corresponding environment file | ||
| R-76057 | R-76057 The VNF Heat **MUST NOT** use special characters | ||
| R-18224 | R-18224 The VNF Heat **MUST** pass in as properties all parameter values associated with the | ||
| R-07443 | R-07443 The VNF Heat **MUST** match the Output parameter name and type with the | ||
| R-23983 | R-23983 The VNF **MUST** pass the external networks into the VNF Heat Orchestration | ||
| R-63345 | R-63345 The VNF Heat **MUST** pass the appropriate external | ||
| R-35666 | R-35666 The VNF Heat **MUST** include the resource(s) to | ||
| R-86972 | R-86972 The VNF Heat **MUST** create internal networks in the Base | ||
| R-68936 | R-68936 The VNF Heat **SHOULD** assign a unique | ||
| R-01455 | R-01455 The VNF Heat **MUST** assign a VNF unique | ||
| R-82481 | R-82481 The VNF Heat **MUST** include {vm-type} as part of the parameter name | ||
| R-66729 | R-66729 The VNF Heat **MUST** include {vm-type} as part of the resource ID | ||
| R-32394 | R-32394 The VNF Heat **MUST** use the same case for {vm-type} for all parameter names in the VNF. | ||
| R-46839 | R-46839 The VNF Heat **MUST** use the same case for {vm-type} for all Resource IDs in the VNF. | ||
| R-05008 | R-05008 The VNF Heat **MUST NOT** be prefixed with a common | ||
| R-15422 | R-15422 The VNF Heat **MUST NOT** be prefixed with a common {vm-type} | ||
| R-21330 | R-21330 The VNF Heat **MUST** include | ||
| R-11168 | R-11168 The VNF Heat **MUST** include | ||
| R-84322 | R-84322 The VNF Heat **MUST** include | ||
| R-96983 | R-96983 The VNF Heat **MUST** include | ||
| R-58424 | R-58424 The VNF Heat **MUST** use the same case for {network-role} for all parameter names in the | ||
| R-21511 | R-21511 The VNF Heat **MUST** use the same case for {network-role} for all Resource IDs in the VNF. | ||
| R-59629 | R-59629 The VNF Heat **MUST** have unique resource IDs within the resources section of a Heat | ||
| R-43319 | R-43319 The VNF Heat **MUST** have unique resource IDs | ||
| R-54517 | R-54517 The VNF Heat **MUST** include {vm-type} in the resource ID | ||
| R-96482 | R-96482 The VNF Heat **MUST** include {network-role} in the resource ID | ||
| R-98138 | R-98138 The VNF Heat **MUST** include int\_{network-role} in the resource ID | ||
| R-82115 | R-82115 The VNF Heat **MUST** include both the {vm-type} and | ||
| R-82551 | R-82551 The VNF Heat **MUST** include both the {vm-type} and | ||
| R-69287 | R-69287 The VNF Heat **MUST** use only alphanumeric characters and “\_� underscores in the | ||
| R-71152 | R-71152 The VNF Heat **MUST** declare as type: string the parameter for property image. | ||
| R-91125 | R-91125 The VNF Heat **MUST** enumerate the parameter for property image in the Heat Orchestration Template | ||
| R-57282 | R-57282 The VNF Heat **MUST** have a separate parameter for image for | ||
| R-50436 | R-50436 The VNF Heat **MUST** declare the paramter property for flavor as type: string. | ||
| R-69431 | R-69431 The VNF Heat **MUST** enumerate the parameter for property flavor in the Heat Orchestration Template | ||
| R-40499 | R-40499 The VNF Heat **MUST** have a separate parameter for flavor for each VM type | ||
| R-22838 | R-22838 The VNF Heat **MUST NOT** enumerate the parameter for property name | ||
| R-51430 | R-51430 The VNF Heat **MUST** declare the paramter for property name as type: string or type: | ||
| R-98450 | R-98450 The VNF Heat **MUST** name the parameter availability\_zone\_{index} in the Heat | ||
| R-13561 | R-13561 The VNF Heat **MUST** start the {index} at zero. | ||
| R-60204 | R-60204 The VNF Heat **MUST** increment the {index} by one. | ||
| R-36887 | R-36887 The VNF Heat **MUST NOT** include the {vm-type} in the parameter name. | ||
| R-17020 | R-17020 The VNF Heat **MUST** include the following three mandatory metadata parameters for an | ||
| R-55218 | R-55218 The VNF Heat **MUST NOT** have parameter constraints defined for the OS::Nova::Server metadata parameter vnf\_id. | ||
| R-20856 | R-20856 The VNF Heat **MUST NOT** enumerate the OS::Nova::Server metadata parameter vnf\_id in environment file. | ||
| R-98374 | R-98374 The VNF Heat **MUST NOT** have parameter constraints defined for the OS::Nova::Server metadata parameter vf\_module\_id. | ||
| R-72871 | R-72871 The VNF Heat **MUST NOT** enumerate the OS::Nova::Server metadata parameter vf\_module\_id in environment file. | ||
| R-44318 | R-44318 The VNF Heat **MUST NOT** have parameter constraints defined for the OS::Nova::Server metadata parameter vnf\_name. | ||
| R-36542 | R-36542 The VNF Heat **MUST NOT** enumerate the OS::Nova::Server metadata parameter vnf\_name in the environment file. | ||
| R-72050 | R-72050 The VNF Heat **MUST** contain {network-role} in the parameter name | ||
| R-57576 | R-57576 The VNF Heat **MUST** contain int\_{network-role} in the parameter name. | ||
| R-93272 | R-93272 The VNF Heat **MUST** adhere to the following parameter naming | ||
| R-65373 | R-65373 The VNF Heat **MUST* adhere to the following parameter naming | ||
| R-47716 | R-47716 The VNF Heat **MUST** adhere to the following parameter naming convention | ||
| R-20106 | R-20106 The VNF Heat **MUST** adhere to the following naming convention for | ||
| R-41177 | R-41177 The VNF Heat **MUST** include {vm-type} and {network-role} in the parameter name, | ||
| R-84898 | R-84898 The VNF Heat **MUST** adhere to the following naming convention, | ||
| R-34960 | R-34960 The VNF Heat **MUST** must adhere to the following | ||
| R-62584 | R-62584 The VNF Heat **MUST** adhere to | ||
| R-29256 | R-29256 The VNF Heat **MUST** must adhere to the following | ||
| R-61282 | R-61282 The VNF Heat **MUST** | ||
| R-16805 | R-16805 The VNF Heat **MUST** adhere to the following naming convention for the property | ||
| R-85734 | R-85734 The VNF Heat **MUST** use the intrinsic function str\_replace | ||
| R-47788 | R-47788 The VNF Heat **MUST** have a 1:1 scope of a cinder volume module, | ||
| R-79531 | R-79531 The VNF Heat **MUST** define “outputs� in the volume template for each Cinder volume | ||
| R-86285 | R-86285 The VNF Heat **MUST** have a | ||
| R-67205 | R-67205 The VNF Heat **MUST** have a corresponding | ||
| R-35727 | R-35727 The VNF Heat **MUST** have a | ||
| R-22656 | R-22656 The VNF Heat **MUST** have a corresponding environment file for a Cinder Volume Module. | ||
| R-89868 | R-89868 The VNF Heat **MUST** have unique file names within the scope | ||
| R-52530 | R-52530 The VNF Heat **MUST NOT** use a directory hierarchy for nested templates. All | ||
| R-11041 | R-11041 The VNF Heat **MUST** have the resource calling the nested yaml file pass | ||
| R-61183 | R-61183 The VNF Heat **MUST NOT** change the parameter names, when OS::Nova::Server metadata parameters are past into a nested heat | ||
| R-76718 | R-76718 The VNF Heat **MUST** reference the get\_files targets in Heat templates by file | ||
| R-41888 | R-41888 The VNE Heat **MUST NOT** use URL-based file retrieval. | ||
| R-62177 | R-62177 The VNF Heat **MUST** have unique file names for the included | ||
| R-87848 | R-87848 The VNF Heat **MUST** have all included files in a single, flat |
Overview
Content Tools