PoC Feedback on Hot Topic#2 Test Methodology for NFV –
TST002 IOP Test Methodology for NFV
0. References
[TST002 WI]
[TST002 Draft]
[TST002 WIKI]
Template version
http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46043
http://docbox.etsi.org/ISG/NFV/Open/Drafts/TST002
http://nfvprivatewiki.etsi.org/index.php?title=IOP_Methodology
1.0
1. PoC Details
PoC#:
PoC Project Name:
2. SUT configurations
Describe and provide a diagram of each of the SUT configurations tested by the PoC. See [TST002 Draft] for
details and examples of SUT configurations.
2.1
SUT configuration #1
2.2
SUT configuration #2
….
2.x
Recommendations
Provide here general feedback and recommendations for NFV SUT configuration documentation.
3. NFV Options
Identify the NFV Options implemented and tested in the PoC. Check one or several boxes.
3.1
Resource management
By VNFO
□
By VNFM
□
Comments:
3.2
Resource Commitment Model
Resource Reservation Model
□
Quota Based Model
□
On-demand Model
□
Comments:
3.3
Other options
Document here other options implemented and tested by the PoC. Provide a reference for each of them.
1/4
3.4
Recommendations
Provide here general feedback and recommendations for testing NFV options.
4. NFV IOP Features
Provide the list of NFV IOP Features (*) tested by the PoC. See [TST002 WIKI] for additional details and
examples of NFV IOP features.
(*) NFV generic features that require the interaction of 2 or more NFV Functional Blocks over one or more NFV
Reference Points.
NFV IOP Features
VNF Package management
VNF on-board
VNF integrity validation
…
Other functional areas
Another feature
…
NFVO
VNFM
Impacted Entities
VIM NFVI EM VNF VNFD NSD
x
x
x
x
2/4
Comments
5. IOP Test Descriptions
Document here the interoperability performed during the PoC.
5.0
TD Template
Use the following template and guidelines for documenting IOP Test Descriptions. This section can be removed
once the document completed.
Interoperability Test Description
Unique test ID according to the following scheme: TD_POCXX_YYYY, where XX is
the PoC number.
Concise summary of the test, which should reflect its purpose and allow readers to
easily distinguish this test from any other test in the document
List of all the required entities for running this test, possibly also including a
(reference to) an illustration of the SUT configuration
List of references to the base specification section(s), use case(s), requirement(s),
etc. which are either used in the test or define the functionality being tested
List of features and capabilities (IOP Features and options) which are required to be
supported by the SUT in order to execute this test
Identifier
Test Purpose
Configuration
References
Applicability
Pre-test conditions
Test
Sequence
List of test specific pre-conditions that need to be met by the SUT including
information about configuration, i.e. precise description of the initial state of the SUT
prior to start executing the test sequence


Step
Type
1
2
3
4
5
6
<Type>
Description
Result
Step description
IOP Verdict
Step Types:

A stimulus corresponds to an event that triggers a specific action on a Function Under Test (FUT), like
sending a message for instance.

A configure corresponds to an action to modify the FUT or SUT configuration.

An IOP check consists of observing that one FUT behaves as described in the standard: i.e. resource creation,
update, deletion, etc… For each IOP check in the Test Sequence, a result can be recorded.
5.1
TD #1
…
5.2
TD #2
…
5.x
Recommendations
Provide here general feedback and recommendations for NFV IOT TD template and documentation.
3/4
…
6. Additional feedback and recommendations
Provide here any additional feedback or recommendation for NFV test methodology that you would like to share
with the ISG NFV TST Working Group
4/4