VNF Test Case Descriptions

VNF Package Test Cases

The information in this section deals with the Test Cases corresponding to the the VNF Requirements. There are two types:

  1. VNF Package Information Element Present: which is the base case of a Test Case, please refer to Annex.

  2. VNF Package Information Element within Range Limits: refers to a Test Case when there are Range Limits placed, please refer to Annex.

VNF Package Information Element Present

Summary

This test case validates whether information elements corresponding to VNF requirements are present in the VNF Package

ONAP Actors (VNF, Operator, ONAP Platform components etc.)

  1. VNF Package

  2. VNF Requirements

  3. ONAP Information Model

Preconditions (ONAP, VNF states, test equipment/ data patterns, measurements)

  1. VNF Package available

  2. VNF Requirements related to VNF Package identified (Mandatory or Optional)

  3. Information Elements corresponding to these VNF Package requirements identified

Operational sequence (e.g. Message Sequence chart + text explanations)

  1. Search the VNF Package for the Presence/ Absence of each Information Elementidentified in the VNF Package requirements.

  2. Flag as an error any Mandatory information Elements that are missing

  3. Report and optional Information Elements that are present.

Post conditions (any post processing of the measurements, any cleanup of the ONAP configuration, reset of the test equipment etc.)

  1. Generate consolidated report on presence/Absence of Information Elements identified in VNF Requirements

Test Result decision ( measurement decision criteria )

  1. Fail if and Mandatory Information Elements are Absent.

VNF Package Information Element within Range Limits

Summary

This test case validates whether information elements corresponding to VNF requirements are present in the VNF Package

ONAP Actors (VNF, Operator, ONAP Platform components etc.)

  1. VNF Package

  2. VNF Requirements

  3. ONAP Information Model

Preconditions (ONAP, VNF states, test equipment/ data patterns, measurements)

  1. VNF Package available

  2. VNF Requirements related to VNF Package identified (Mandatory or Optional)

  3. Information Elements corresponding to these VNF Package requirements identified

  4. Range Limits for Information Elements identified

Operational sequence (e.g. Message Sequence chart + text explanations)

  1. Search the VNF Package for the Presence/ Absence of each Information Element identified in the VNF Package requirements.

  2. Flag as an error any Mandatory information Elements that are missing

Post conditions (any post processing of the measurements, any cleanup of the ONAP configuration, reset of the test equipment etc.)

  1. Generate consolidated report on presence/Absence of Information Elements identified in VNF Requirements

Test Result decision ( measurement decision criteria )

  1. Fail if and Mandatory Information Elements are Absent.

VNF Onboard and Instantiate Test Specification

Scope

This specification defines the logical steps and activities required to implement a test case that validates that a arbitrary Virtual Network Function (VNF) that is packaged in compliance with the ONAP VNF Requirements can be successfully be onboarded into ONAP and instantiated. This specification only covers up to instantiation of the VNF and does not address the VNF’s compliance with requirements governing other lifecycle functions controlled by ONAP (ex: Lifecycle Management, Monitoring, etc.)

Two test cases will be defined based on the VNF package used:

  1. ZIP file containing ONAP-compliant OpenStack Heat

  2. Cloud Service Archive (CSAR) containing a Topology and Orchestration Specification for Cloud Applications (TOSCA) VNF Descriptor

References

Actors

The following defines the various actors that will be referenced within this specification. It is expected and permissable that a given user or entity can serve in multiple roles for the purposes of the test.

  • VNF Provider - Responsible for developing, packaging, and distributing a VNF that is compliant with ONAP VNF Requirements as well as providing any additional artifacts required to setup the Test Lab or Test Engine.

  • Test Lab - Hosts the ONAP and Cloud environment used to execute the test cases. The environment will host a deployed instance of ONAP using the official El Alto release of ONAP and a compatible OpenStack cloud instance.

  • Test Lab Provider - Responsible for establishing the Test Lab and supporting the Tester in the configuration of the Test Lab for any VNF specific requirements such as virtual machine images or networks. This will include providing the Test Engine access to the necessary ONAP APIs/GUIs as well as access to the OpenStack APIs.

  • Tester - Responsible for:

    1. Ensuring the test lab is configured per the VNF’s requirements and needs.

    2. Configuring the Test Engine for execution. The artifacts required will be provided by the VNF Provider.

    3. Executing the the test cases using the Test Engine.

    4. Reporting the results of the test case to the VNF Provider.

  • Test Engine - Provides automation of the test execution and verification of the success or failure of the individual test cases. The Test Engine must also provide further documentation on how it and the Test Lab must be configured for successful execution and verification of the test cases.

Test Case Description: VNF Onboarding and Instantiation using OpenStack Heat

This test case is specific to executing and validating the onboarding of a VNF using OpenStack Heat.

Assumptions

  • The specific configuration of the Vendor License Model is not relevant to the successful execution of this test case. The Test Engine shall create a generic Vendor License Model to assign to the VNF for the purposes of this test.

  • Testing will support the instantiation of a SDC Service that is composed of a single VNF. The scope of this test is focused on the instantiation of a single VNF defined in a single Heat package. Testing services that comprise multiple VNFs is beyond the scope of this specification.

  • The Test Engine will have access to the ONAP APIs in terms of both network connectivity and API access.

  • VNF Instantiation for either ONAP legacy VNF API or Generic Resource API is supported.

Prerequisites

  • VNF Provider has:

    • Provided the Tester the VNF package containing OpenStack Heat that has been certified compliant by the OPNFV Verification Program for VNFs or validated by the El Alto release of the ONAP VNF Validation Platform

    • Provided the Tester any custom virtual machine image required by the VNF

    • Provided the Tester network requirements for any ONAP external networks (i.e. networks not created in the Heat template itself) required by the VNF.

    • Provided the Tester with any additional artifacts required by the Test Engine. Additional artifacts required by the Test Engine are outside the scope of this document. Please refer to the Test Engine documentation for more details.

  • Test Lab Provider has:

    • Successfully deployed an OpenStack cloud instance for ONAP to deploy and instantiate the VNF.

    • Successfully deployed the certified El Alto release version of ONAP.

    • Configured the ONAP instance to work with the OpenStack instance.

      • NOTE: Documentation of OpenStack and ONAP setup are beyond the scope of this document. Please refer to the References section for more information.

    • Provided the Test Engine network connectivity to both the ONAP and OpenStack control planes.

    • Provided the Test Engine permissions to invoke the required ONAP and OpenStack APIs. Full details to be provided in the Test Engine documentation.

  • The Tester has:

    • Created any external networks in ONAP and OpenStack cloud environment in compliance with the VNF Providers request and specification.

    • Registered any custom virtual machine images provided by the VNF Provider in the OpenStack Glance repository.

    • Configured the Test Engine with the necessary artifacts from the VNF Provider for successful test execution. The Test Engine must provide the full documentation on what is required to configure it for successful execution.

    • Ensured connectivity from the Test Engine to any Operations, Administration, and Management (OAM) interfaces provided by the VNF. This connectivity must allow PING requests which will be used as part of the validation process to ensure the VNF has been properly instantiated.

Execution Steps

The following steps will all be executed by the Test Engine. The steps depicts the actions that will be taken and which ONAP component the Test Engine will interact with to perform the action.

Failure encountered at any step will halt all subsequent steps and result in the overall failure of the test case.

Any additional required fields that must be assigned or input within ONAP will be defined in a configuration file whose format will be defined in the documentation of the Test Engine.

Steps

  1. Execute VVP validation scripts to ensure VNF Heat Templates are compliant with the VNF Heat Template Requirements.

  2. Create the generic Vendor License Model (VLM) in SDC

  3. Create the Vendor Software Product (VSP) in SDC. The VSP will be auto-assigned a unique name to avoid collisions with other VSPs in the lab environment.

  4. Upload the ONAP-compliant Heat archive (zip file) as an artifact of the VSP in SDC.

  5. Assign any “Unassigned Files” in SDC to Artifacts

  6. Validate the VSP and ensure no SDC errors are raised, but warnings are acceptable. If errors are reported, then halt the test and report a failure.

  7. Assign the generic VLM to the VSP in SDC.

  8. Create the Virtual Function (VF) in SD. The VF will be auto-assigned a unique name to avoid collisions with other VSPs in the lab environment.

  9. Create the Service in SDC. The Service will be auto-assigned a unique name to avoid collisions with other VSPs in the lab environment.

  10. Assign the VF/VNF to the Service Model in SDC.

  11. Distribute the Service Model from SDC.

  12. Register Preload (i.e. per instance configuration data) with SDNC

  13. For each VF module in the VNF, starting with the base module, trigger instantiation from VID.

  14. After VNF Instantiation, query openstack for heat stack details to validate successful instantiation.

Pass/Fail Criteria

Following, or during, test execution the tests below will be executed to evaluate the success of the overall test case. As previously stated above, if any individual test step fails, then the test case will fail.

  1. The Heat stack has been successfully created in OpenStack without errors

  2. The Heat stack configuration matches the definition from the associated Heat templates and environment settings provided as input (or derived by) the Test Engine

Test Case Description: VNF Onboarding and Instantiation using TOSCA

This test case is specific to executing and validating the onboarding of a VNF written in TOSCA and packaged in a CSAR.

Assumptions

  • The specific configuration of the Vendor License Model is not relevant to the successful execution of this test case. The Test Engine shall create a generic Vendor License Model to assign to the VNF for the purposes of this test.

  • Testing will support the instantiation of a SDC Service that is composed of a single VNF. The scope of this test is focused on the instantiation of a single VNF defined in a single TOSCA package. Testing services that comprise multiple VNFs is beyond the scope of this specification.

  • The Test Engine will have access to the ONAP APIs in terms of both network connectivity and API access.

  • All instantiations will use the ONAP Generic Resource API from VFC instead of the legacy VNF API.

Prerequisites

  • VNF Provider has:

    • Provided the Tester the TOSCA based VNF Package that has been certified compliant by the LFN OVP(OPNFV Verification Program) for VNFs or validated by the El Alto release of the ONAP VNFSDK

    • Provided the Tester any custom virtual machine image required by the VNF

    • Provided the Tester network requirements for any ONAP external networks (i.e. networks not created in the TOSCA template itself) required by the VNF.

    • Provided the Tester with any additional artifacts required by the Test Engine. Additional artifacts required by the Test Engine are outside the scope of this document. Please refer to the Test Engine documentation for more details.

  • Test Lab Provider has:

    • Successfully deployed an OpenStack cloud instance for ONAP to deploy and instantiate the VNF.

    • Successfully deployed the certified El Alto release version of ONAP.

    • Configured the ONAP instance to work with the OpenStack instance.

      • NOTE: Documentation of OpenStack and ONAP setup are beyond the scope of this document. Please refer to the References section for more information.

    • Provided the Test Engine network connectivity to both the ONAP and OpenStack control planes.

    • Provided the Test Engine permissions to invoke the required ONAP and OpenStack APIs. Full details to be provided in the Test Engine documentation.

  • The Tester has:

    • Created any external networks in ONAP and OpenStack cloud environment in compliance with the VNF Providers request and specification.

    • Registered any custom virtual machine images provided by the VNF Provider in the OpenStack Glance repository.

    • Configured the Test Engine with the necessary artifacts from the VNF Provider for successful test execution. The Test Engine must provide the full documentation on what is required to configure it for successful execution.

    • Ensured connectivity from the Test Engine to any Operations, Administration, and Management (OAM) interfaces provided by the VNF. This connectivity must allow PING requests which will be used as part of the validation process to ensure the VNF has been properly instantiated.

Execution Steps

The following steps will all be executed by the Test Engine. The steps depicts the actions that will be taken and which ONAP component the Test Engine will interact with to perform the action.

Failure encountered at any step will halt all subsequent steps and result in the overall failure of the test case.

Any additional required fields that must be assigned or input within ONAP will be defined in a configuration file whose format will be defined in the documentation of the Test Engine.

Steps

  1. Register VIM and VNFM to ONAP environment through ESR.

  2. Create the generic Vendor License Model (VLM) in SDC.

  3. Create the Vendor Software Product (VSP) in SDC. The VSP will be auto-assigned a unique name to avoid collisions with other VSPs in the lab environment.

  4. Upload the ONAP-compliant TOSCA archive (zip file) as an artifact of the VSP in SDC.

  5. Assign any “Unassigned Files” in SDC to Artifacts.

  6. Validate the VSP and ensure no SDC errors are raised, but warnings are acceptable. If errors are reported, then halt the test and report a failure.

  7. Assign the generic VLM to the VSP in SDC.

  8. Create the Virtual Function (VF) in SDC. The VF will be auto-assigned a unique name to avoid collisions with other VSPs in the lab environment.

  9. Add original VNF CSAR as artifacts to VF.

  10. Assign nf_type property with required VNFM driver.

  11. Certify VF model

  12. Create the Service in SDC. The Service will be

auto-assigned a unique name to avoid collisions with other VSPs in the lab environment.

  1. Assign the VF/VNF to the Service Model in SDC.

  2. Attach original NS CSAR with service model.

  3. Test the Service model in SDC.

  4. Approve the Service model in SDC.

  5. Distribute the Service Model from SDC.

  6. Onboard VNF CSAR from SDC to VFC Catalog.

  7. Onboard Service CSAR from SDC to VFC Catalog.

  8. Call VFC NSLCM Create API to create service instance.

  9. Call VFC NSLCM Instantiate API to instantiate service.

Pass/Fail Criteria

Following, or during, test execution the tests below will be executed to evaluate the success of the overall test case. As previously stated above, if any individual test step fails, then the test case will fail.

  1. The virtual machine has been successfully created in OpenStack without errors.

  2. Each virtual machine in the OpenStack must have a corresponding vserver ONAP’s Available and Active Inventory (AAI) component with all required data elements.

  3. The VNF has a Generic-VNF object recorded in AAI with all required data elements.

Appendix

List of Requirements with associated Tests

Currently, there VNFs can be packaged as HEAT templates or in a CSAR file using TOSCA. At this stage, there are two different tools used for validating the packages based on the package type:

  • CSAR/TOSCA packages leverage VNFSDK

  • HEAT packages leverage VVP

HEAT Package Validations

This table shows all the requirements within the VNF Requirements project and if they are validated by VVP. If they are validated by VVP, then the test module and test method is provided. This is generated dynamically within the VVP project, where it pulls down the latest JSON from Req List and maps the requirements to the tests in VVP to output this table.

Note: Tests on the bottom do not map to any requirements.

Note: VVP only validates Heat for Requirements in Chapter 5.

Download

You can download the table here.

Test Traceability

Requirement ID

Test Module

Test Name

R-00977

test_nova_servers_vm_types

test_vm_type_network_role_collision

R-01455

test_vm_class_has_unique_type

test_vm_class_has_unique_type

R-02164

test_contrail_fqdn

test_contrail_fqdn

R-02691

test_environment_file_parameters

test_nova_server_workload_context_parameter_doesnt_exist_in_environment_file

R-03324

test_environment_file_structure

test_environment_file_contains_required_sections

R-04697

test_fixed_ips_include_vm_type_network_role

test_external_fip_format

R-04747

test_cloud_config_resource_id

test_cloud_config

R-05257

test_forbidden_resources

test_neutron_floating_ip_resource_type

R-07443

test_volume_outputs_consumed

test_volume_outputs_consumed

R-07507

test_server_parameters

test_vnf_id_parameter_type_and_parameter_name

R-08975

test_software_config_resource_id

test_software_config_vm_type

R-09811

test_required_parameters_no_constraints

test_vf_module_index_parameter_has_no_constraints

R-100000

test_contrail_instance_ip_parameters

test_contrail_external_instance_ip_address_parameter

R-100010

test_contrail_instance_ip_parameters

test_contrail_external_instance_ip_address_parameter

R-100020

test_environment_file_parameters

test_contrail_external_instance_ip_does_not_exist_in_environment_file

R-100030

test_contrail_instance_ip_parameters

test_contrail_external_instance_ip_address_parameter

R-100040

test_environment_file_parameters

test_contrail_external_instance_ip_does_not_exist_in_environment_file

R-100050

test_contrail_instance_ip_parameters

test_contrail_external_instance_ip_address_parameter

R-100060

test_environment_file_parameters

test_contrail_external_instance_ip_does_not_exist_in_environment_file

R-100070

test_contrail_instance_ip_parameters

test_contrail_external_instance_ip_address_parameter

R-100080

test_environment_file_parameters

test_contrail_external_instance_ip_does_not_exist_in_environment_file

R-100090

test_contrail_instance_ip_parameters

test_contrail_internal_instance_ip_address_parameter

R-100100

test_environment_file_parameters

test_contrail_internal_instance_ip_does_exist_in_environment_file

R-100110

test_contrail_instance_ip_parameters

test_contrail_internal_instance_ip_address_parameter

R-100120

test_environment_file_parameters

test_contrail_internal_instance_ip_does_exist_in_environment_file

R-100130

test_contrail_instance_ip_parameters

test_contrail_internal_instance_ip_address_parameter

R-100140

test_environment_file_parameters

test_contrail_internal_instance_ip_does_exist_in_environment_file

R-100150

test_contrail_instance_ip_parameters

test_contrail_internal_instance_ip_address_parameter

R-100160

test_environment_file_parameters

test_contrail_internal_instance_ip_does_exist_in_environment_file

R-100170

test_environment_file_parameters

test_contrail_external_instance_ip_does_not_exist_in_environment_file

R-100180

test_environment_file_parameters

test_contrail_internal_instance_ip_does_exist_in_environment_file

R-100190

test_contrail_instance_ip_parameters

test_contrail_external_instance_subnet_id_parameter

R-100200

test_contrail_instance_ip_parameters

test_contrail_external_instance_subnet_id_parameter

R-100210

test_environment_file_parameters

test_contrail_subnet_uuid_does_not_exist_in_environment_file

R-100220

test_contrail_instance_ip_parameters

test_contrail_external_instance_subnet_id_parameter

R-100230

test_environment_file_parameters

test_contrail_subnet_uuid_does_not_exist_in_environment_file

R-100240

test_contrail_instance_ip_parameters

test_contrail_incremental_module_internal_subnet_usage

R-100250

test_environment_file_parameters

test_contrail_subnet_uuid_does_not_exist_in_environment_file

R-100260

test_contrail_instance_ip_parameters

test_contrail_incremental_module_internal_subnet_usage

R-100270

test_environment_file_parameters

test_contrail_subnet_uuid_does_not_exist_in_environment_file

R-100280

test_allowed_address_pairs_include_vm_type_network_role

test_external_aap_format_contrail

R-100310

test_allowed_address_pairs_include_vm_type_network_role

test_external_aap_format_contrail

R-100330

test_allowed_address_pairs_include_vm_type_network_role

test_external_aap_format_contrail

R-100350

test_allowed_address_pairs_include_vm_type_network_role

test_external_aap_format_contrail

R-100360

test_allowed_address_pairs_include_vm_type_network_role

test_contrail_internal_vmi_aap_parameter

R-100370

test_allowed_address_pairs_include_vm_type_network_role

test_contrail_internal_vmi_aap_parameter

R-10834

test_nested_parameter_args

test_nested_parameter_args

R-11041

test_nested_template_parameters

test_nested_template_parameters

R-11200

test_volume_outputs_consumed

test_volume_outputs_consumed

R-11441

test_heat_template_structure

test_parameter_type

R-11690

test_resource_indices

test_indices_start_at_0_increment

R-13194

test_environment_file_parameters

test_nova_server_environment_context_parameter_doesnt_exist_in_environment_file

R-15287

test_neutron_port_fixed_ips_subnet

test_external_subnet_format

R-15480

test_required_parameters_no_constraints

test_vf_module_name_parameter_has_no_constraints

R-16241

test_network_format

test_network_has_subnet

R-16437

test_contrail_resource_id

test_contrail_servicetemplate_resource_id

R-16447

test_unique_resources_across_all_templates

test_unique_resources_across_all_yaml_files

R-16968

test_network_format

test_network_resource_id_format

R-17528

test_nesting_level

test_nesting_level

R-18008

test_neutron_port_network_parameter

test_neutron_port_network_param_is_string

R-18683

test_oam_address_outputs

test_oam_address_v4_zero_or_one

R-19756

test_contrail_irt_routes

test_contrail_irt_route_param_type

R-20065

test_contrail_resource_id

test_contrail_porttuple_resource_id

R-20308

test_nova_servers_environment_context

test_environment_context

R-20453

test_port_resource_ids

test_port_resource_ids

R-20856

test_environment_file_parameters

test_nova_server_vnf_id_parameter_doesnt_exist_in_environment_file

R-22288

test_environment_file_parameters

test_neutron_port_fixedips_subnet_parameter_doesnt_exist_in_environment_file

R-22688

test_neutron_port_network_attachment

test_internal_network_parameters

R-22838

test_environment_file_parameters

test_nova_server_name_parameter_doesnt_exist_in_environment_file

R-23311

test_server_parameters

test_availability_zone_parameter_type

R-23503

test_fixed_ips_include_vm_type_network_role

test_external_fip_format

R-23664

test_heat_template_structure

test_heat_template_structure_contains_resources

R-25720

test_neutron_net_resource_id

test_neutron_net_resource_id

R-25877

test_heat_parameter_section

test_parameter_names

R-26351

test_port_resource_ids

test_port_resource_ids

R-26506

test_port_resource_ids

test_port_resource_ids

R-270358

test_volume_templates

test_volume_templates_contains_cinder_or_resource_group

R-27078

test_heat_template_structure

test_heat_template_structure_contains_heat_template_version

R-27818

test_fixed_ips_include_vm_type_network_role

test_internal_fip_format

R-28222

test_contrail_irt_routes

test_contrail_irt_route_param_format

R-28795

test_environment_file_parameters

test_neutron_port_internal_fixedips_ipaddress_parameter_exists_in_environment_file

R-29751

test_nova_server_resource_id

test_nova_server_resource_id

R-29765

test_fixed_ips_include_vm_type_network_role

test_internal_fip_format

R-29872

test_environment_file_parameters

test_neutron_port_network_parameter_doesnt_exist_in_environment_file

R-304011

test_server_and_port_vm_indices_match

test_server_and_port_vmtype_indices_match

R-30753

test_contrail_resource_id

test_contrail_networkipam_resource_id

R-30804

test_multipart_mime_resource_id

test_multipart_mime

R-31141

test_heat_pairs_provided

test_heat_pairs_provided

R-32394

test_vm_type_case

test_vm_type_case

R-34037

test_fixed_ips_include_vm_type_network_role

test_external_fip_format

R-34055

test_required_parameters_no_constraints

test_workload_context_parameter_has_no_constraints

R-348813

test_no_image_files

test_no_image_files_included

R-35414

test_heat_template_structure

test_heat_template_structure_contains_parameters

R-35666

test_internal_networks

test_networks_exist_for_internal_network_params

R-35735

test_allowed_address_pairs_include_vm_type_network_role

test_external_aap_format

R-36542

test_environment_file_parameters

test_nova_server_vnf_name_parameter_doesnt_exist_in_environment_file

R-36772

test_heat_template_parameters_contain_required_fields

test_heat_template_parameters_contain_required_fields

R-37028

test_base_template_names

test_base_template_names

R-37039

test_environment_file_parameters

test_nova_server_vf_module_index_parameter_doesnt_exist_in_environment_file

R-37437

test_servers_have_required_metadata

test_servers_have_required_metadata

R-38236

test_neutron_port_fixed_ips_subnet

test_external_subnet_format

R-38474

test_env_and_yaml_same_name

test_env_and_yaml_same_name

R-39067

test_server_parameters

test_vf_module_name_parameter_type_and_parameter_name

R-39402

test_heat_template_structure

test_heat_template_structure_contains_description

R-39841

test_environment_file_parameters

test_neutron_port_external_fixedips_ipaddress_parameter_doesnt_exist_in_environment_file

R-40499

test_nova_servers_vm_types

test_nova_server_flavor_parameter

R-40971

test_fixed_ips_include_vm_type_network_role

test_external_fip_format

R-41492

test_allowed_address_pairs_include_vm_type_network_role

test_external_aap_format

R-41493

test_allowed_address_pairs_include_vm_type_network_role

test_external_aap_format

R-41888

test_get_file_only_reference_local_files

test_get_file_no_url_retrieval

R-44001

test_heat_template_parameters_contain_required_fields

test_heat_template_parameters_contain_required_fields

R-44318

test_required_parameters_no_constraints

test_vnf_name_parameter_has_no_constraints

R-45188

test_nova_servers_vm_types

test_nova_server_flavor_parameter

R-46128

test_contrail_instance_ip_resource_id

test_contrail_instance_ip_resource_id_external

R-46839

test_vm_type_resource_id

test_vm_type_resource_id

R-48067

test_nova_servers_vm_types

test_vm_type_network_role_collision

R-481670

test_nova_servers_vm_types_use_get_param

test_vm_type_assignments_on_nova_servers_only_use_get_param

R-50011

test_environment_file_parameters

test_heat_rg_count_parameter_exists_in_environment_file

R-50436

test_nova_servers_vm_types

test_nova_server_flavor_parameter

R-50468

test_contrail_vmi_resource_id

test_contrail_instance_ip_resource_id_internal

R-50816

test_servers_metadata_use_get_param

test_servers_vf_module_index_metadata_use_get_param

R-511776

test_files_in_flat_dir

test_files_in_flat_dir

R-51430

test_nova_servers_vm_types

test_nova_server_name_parameter

R-53310

test_contrail_instance_ip_resource_id

test_contrail_instance_ip_resource_id_external

R-53433

test_env_and_yaml_same_name

test_env_and_yaml_same_name

R-53952

test_no_http_resources

test_no_http_resources

R-54171

test_nova_servers_vm_types

test_nova_server_name_parameter

R-54340

test_server_parameters

test_vf_module_index_parameter_type_and_parameter_name

R-55218

test_required_parameters_no_constraints

test_vnf_id_parameter_has_no_constraints

R-55306

test_volume_templates

test_no_vf_module_index_in_cinder

R-55307

test_vf_module_index

test_no_vf_module_index_contrail_ips

R-56183

test_required_parameters_no_constraints

test_environment_context_parameter_has_no_constraints

R-56438

test_heat_pairs_provided

test_heat_pairs_provided

R-57282

test_nova_servers_vm_types

test_nova_server_image_parameter

R-58670

test_nova_servers_vm_types

test_nova_server_image_parameter

R-589037

test_volume_module_naming

test_detected_volume_module_follows_naming_convention

R-59568

test_environment_file_parameters

test_nova_server_az_parameter_doesnt_exist_in_environment_file

R-599443

test_env_parameters_defined_in_template

test_env_params_are_defined_in_template

R-60011

test_nesting_level

test_nesting_level

R-610030

test_incremental_module

test_incremental_module_has_server

R-62187

test_contrail_instance_ip_resource_id

test_contrail_instance_ip_resource_id_internal

R-62428

test_server_parameters

test_vnf_name_parameter_type_and_parameter_name

R-62590

test_environment_file_parameters

test_neutron_port_external_fixedips_ipaddress_parameter_doesnt_exist_in_environment_file

R-62802

test_neutron_port_fixed_ips_subnet

test_external_subnet_format

R-62983

test_neutron_port_network_attachment

test_external_network_parameter

R-663631

test_nova_servers_vm_types_use_get_param

test_vm_type_assignments_on_nova_servers_only_use_get_param

R-67231

test_env_no_resource_registry

test_env_no_resource_registry

R-67597

test_required_parameters_no_constraints

test_vm_role_parameter_has_no_constraints

R-68023

test_servers_metadata_use_get_param

test_servers_vf_module_name_metadata_use_get_param

R-681859

test_port_resource_ids

test_port_resource_ids

R-69431

test_environment_file_parameters

test_nova_server_flavor_parameter_exists_in_environment_file

R-69634

test_environment_file_parameters

test_neutron_port_fixedips_subnet_parameter_doesnt_exist_in_environment_file

R-70276

test_filename_is_vmtype_dot_yaml

test_filename_is_vmtype_dot_yaml

R-708564

test_nested_parameters

test_iip_instance_ip_parameter_name_doesnt_change_in_nested_template

R-71152

test_nova_servers_vm_types

test_nova_server_image_parameter

R-71493

test_servers_have_required_metadata

test_servers_have_required_metadata

R-71577

test_fixed_ips_include_vm_type_network_role

test_external_fip_format

R-71699

test_no_http_resources

test_no_http_resources

R-717227

test_allowed_address_pairs_include_vm_type_network_role

test_internal_aap_format

R-72483

test_servers_have_required_metadata

test_servers_have_required_metadata

R-72871

test_environment_file_parameters

test_nova_server_vf_module_id_parameter_doesnt_exist_in_environment_file

R-74304

test_heat_pairs_provided

test_heat_pairs_provided

R-74978

test_nova_servers_workload_context

test_workload_context

R-75141

test_resource_ids_alphanumeric_only

test_alphanumeric_resource_ids_only

R-76014

test_contrail_resource_id

test_contrail_servicehealthcheck_resource_id

R-76057

test_base_template_names

test_base_template_names

R-76160

test_neutron_port_fixed_ips_subnet

test_internal_subnet_format

R-76449

test_forbidden_resources

test_neutron_floating_ip_association_resource_type

R-76682

test_environment_file_parameters

test_contrail_route_prefixes_parameter_doesnt_exist_in_environment_file

R-76718

test_get_file_only_reference_local_files

test_get_file_only_reference_local_files

R-78380

test_fixed_ips_include_vm_type_network_role

test_internal_fip_format

R-80374

test_environment_file_parameters

test_nova_server_vf_module_name_parameter_doesnt_exist_in_environment_file

R-805572

test_allowed_address_pairs_include_vm_type_network_role

test_internal_aap_format

R-80829

test_environment_file_parameters

test_neutron_port_fixedips_subnet_parameter_doesnt_exist_in_environment_file

R-81214

test_contrail_resource_id

test_contrail_interfaceroutetable_resource_id

R-81339

test_base_template_names

test_base_template_names

R-81725

test_env_and_yaml_same_name

test_env_and_yaml_same_name

R-82134

test_server_parameters

test_vf_module_id_parameter_type_and_parameter_name

R-82732

test_volume_outputs_consumed

test_volume_module_name_matches_incremental_or_base_module

R-83412

test_environment_file_parameters

test_neutron_port_external_aap_ip_parameter_doesnt_exist_in_environment_file

R-83677

test_environment_file_parameters

test_neutron_port_fixedips_subnet_parameter_doesnt_exist_in_environment_file

R-84123

test_neutron_port_fixed_ips_subnet

test_internal_subnet_format

R-85235

test_fixed_ips_include_vm_type_network_role

test_internal_fip_format

R-85734

test_non_server_name

test_non_server_name

R-86182

test_neutron_port_network_attachment

test_internal_network_parameters

R-86285

test_heat_pairs_provided

test_heat_pairs_provided

R-86476

test_vm_role_value

test_vm_role_from_env_file

R-87123

test_environment_file_parameters

test_neutron_port_external_fixedips_ipaddress_parameter_doesnt_exist_in_environment_file

R-87247

test_base_template_names

test_base_template_names

R-87485

test_base_template_names

test_base_template_names

R-87563

test_contrail_instance_ip_resource_id

test_contrail_instance_ip_resource_id_internal

R-87817

test_nova_servers_vm_types

test_nova_server_name_parameter

R-89913

test_volume_templates_outputs

test_volume_templates_contains_outputs

R-901331

test_nova_servers_vm_types_use_get_param

test_vm_type_assignments_on_nova_servers_only_use_get_param

R-90152

test_initial_configuration

test_06_heat_template_resource_section_has_resources

R-90206

test_environment_file_parameters

test_neutron_port_internal_fixedips_ipaddress_parameter_exists_in_environment_file

R-90279

test_all_parameters_used_in_template

test_all_parameters_used_in_template

R-90526

test_heat_parameter_section

test_default_values

R-91125

test_environment_file_parameters

test_nova_server_image_parameter_exists_in_environment_file

R-91342

test_heat_pairs_provided

test_heat_pairs_provided

R-92193

test_environment_file_parameters

test_network_fqdn_parameter_doesnt_exist_in_environment_file

R-92635

test_initial_configuration

test_02_no_duplicate_keys_in_file

R-93030

test_environment_file_parameters

test_neutron_port_external_fixedips_ipaddress_parameter_doesnt_exist_in_environment_file

R-93496

test_environment_file_parameters

test_neutron_port_internal_fixedips_ipaddress_parameter_exists_in_environment_file

R-94509

test_heat_pairs_provided

test_heat_pairs_provided

R-94669

test_oam_address_outputs

test_oam_address_v6_zero_or_one

R-95303

test_initial_configuration

test_00_valid_yaml

R-96253

test_contrail_vmi_resource_id

test_contrail_instance_ip_resource_id_external

R-97201

test_environment_file_parameters

test_neutron_port_internal_fixedips_ipaddress_parameter_exists_in_environment_file

R-98374

test_required_parameters_no_constraints

test_vf_module_id_parameter_has_no_constraints

R-98407

test_vm_type_syntax

test_vm_type_syntax

R-98450

test_availability_zone

test_availability_zone_naming

R-98569

test_environment_file_parameters

test_neutron_port_internal_fixedips_ipaddress_parameter_exists_in_environment_file

R-98905

test_environment_file_parameters

test_neutron_port_external_fixedips_ipaddress_parameter_doesnt_exist_in_environment_file

R-99110

test_contrail_vn_resource_id

test_neutron_net_resource_id

R-99646

test_files_in_flat_dir

test_files_in_flat_dir

R-99812

test_environment_file_parameters

test_nova_server_name_parameter_doesnt_exist_in_environment_file

CSAR/TOSCA Package Validations

Please refer to the VNFSDK project’s list of verified requirements for the current coverage for CSAR and TOSCA.

VNF Requirements corresponding Information Elements w/Range limits

Will be generated in future releases.

VNF Test Case Release Notes

Version: 1.0.0

Release Date

2018-06-06

New Features

Initial release of VNF Test Cases for Open Network Automation Platform (ONAP)

This intitial releases is based on seed documents that came from Open-O and Open ECOMP. For details, refer Seed Document Mappings to VNFRQTS Deliverable Outlines.

CSV table of testable requirements in VNF Requirements Document

Bug Fixes
  • None

Known Issues
  • No known issues

Security Issues
  • No known security issues.

Upgrade Notes
  • Initial release - none

Deprecation Notes
  • Initial release - none

Other


End of Release Notes