Disclaimer

The present document has been produced and approved by the <long ISGname> (<short ISGname>) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this ISG.

It does not necessarily represent the views of the entire ETSI membership.

ETSI GS NFV-TST010 V0.0.5 (2018-11)

Network Function Virtualisation (NFV) Release 2;Testing;

API Conformance Testing SpecificationRelease #2

GROUP SPECIFICATION

The GS (ETSI Group Specifications) are deliverables produced by Industry Specification Groups (ISG). GSs are written with the style of a Technical Specification (TS), and represent the sole view of the ISG members.

The guidance text (green) shall be removed when no longer needed or the skeleton without guidance text also available via the editHelp! website should be used.

<<

Release #2

Reference<Workitem>

Keywords<keywords>

ETSI

650 Route des LuciolesF-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-préfecture de Grasse (06) N° 7803/88

Important notice

The present document can be downloaded from:http://www.etsi.org/standards-search

The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any

existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.

Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at

https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx

If you find errors in the present document, please send your comment to one of the following services:https://portal.etsi.org/People/CommiteeSupportStaff.aspx

Copyright Notification

No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI.

The content of the PDF version shall not be modified without the written authorization of ETSI.The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI yyyy.All rights reserved.

DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.3GPPTM and LTE™ are trademarks of ETSI registered for the benefit of its Members and

of the 3GPP Organizational Partners.oneM2M logo is protected for the benefit of its Members.

GSM® and the GSM logo are trademarks registered and owned by the GSM Association.

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)2

Release #2

Copyrights on page 2This paragraph should be used for deliverables processed before ISG/WG approval and used in meetings.

Reproduction is only permitted for the purpose of standardization work undertaken within ETSI.The copyright and the foregoing restriction extend to reproduction in all media.

If an additonal copyright is necessary, it shall appear on page 2 after the ETSI copyright notification

The additional EBU copyright applies for EBU and DVB documents.

© European Broadcasting Union yyyy.

The additional CENELEC copyright applies for ETSI/CENELEC documents.

© Comité Européen de Normalisation Electrotechnique yyyy.

The additional CEN copyright applies for CEN documents.

© Comité Européen de Normalisation yyyy.

The additional WIMAX copyright applies for WIMAX documents.

© WIMAX Forum yyyy.

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)3

Release #2

Contents (style TT)

To unlock the Table of Contents: select the Table of Contents, click simultaneously: Ctrl + Shift + F11.To update the Table of Contents: F9.To lock it: select the Table of Contents and then click simultaneously: Ctrl + F11.

Copyrights on page 2..........................................................................................................................................

Intellectual Property Rights (style H1)................................................................................................................

Foreword (style H1)............................................................................................................................................Multi-part documents............................................................................................................................................................

Modal verbs terminology (style H1)...................................................................................................................

Executive summary (style H1)............................................................................................................................

Introduction (style H1)........................................................................................................................................

1 Scope (style H1)........................................................................................................................................

2 References (style H1)................................................................................................................................2.1 Normative references (style H2)..........................................................................................................................2.2 Informative references (style H2)........................................................................................................................

3 Definitions, symbols and abbreviations (style H1)...................................................................................3.1 Definitions (style H2)..........................................................................................................................................3.2 Symbols (style H2)..............................................................................................................................................3.3 Abbreviations (style H2)......................................................................................................................................

4 Methodology (style H1).........................................................................................................................4.1 General...............................................................................................................................................................4.2 System under test...............................................................................................................................................4.3 Test configurations............................................................................................................................................4.3.1 General.........................................................................................................................................................114.3.2 Config_prod_VE..........................................................................................................................................124.3.3 Config_prod_VNFM....................................................................................................................................124.3.4 Config_prod_NFVO....................................................................................................................................134.5 Generic test description.....................................................................................................................................4.5.1 General.........................................................................................................................................................134.5.2 Scope of the tests..........................................................................................................................................134.5.3 Verification..................................................................................................................................................134.5.4 Test templates............................................................................................................................................................144.6 Test Suite Structure.......................................................................................................................................................

5 Os-Ma-Nfvo Reference Point.................................................................................................................5.1 General..........................................................................................................................................................................5.2 ICS 155.2 Test configuration.........................................................................................................................................................5.3 Interface #1 (TBD).......................................................................................................................................................5.3.1 Operation #1..............................................................................................................................................................155.3.2 Operation #2..............................................................................................................................................................155.4 Interface #2...................................................................................................................................................................

6 Ve-Vnfm Reference Point......................................................................................................................6.1 General..........................................................................................................................................................................6.2 Test configuration.........................................................................................................................................................6.3 15

7 Or-Vnfm Reference Point.......................................................................................................................7.1 General..........................................................................................................................................................................7.2 Test configuration.........................................................................................................................................................7.3 16Annexes 17

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)4

Release #2

Annex A (normative or informative): Title of annex (style H8)..................................................................17

Annex B (normative or informative): Title of annex (style H8)..................................................................18

B.1 First clause of the annex (style H1)........................................................................................................B.1.1 First subdivided clause of the annex (style H2).................................................................................................

Annex <X> (informative): Authors & contributors (style H8)...................................................................18

Annex <Y> (informative): Bibliography (style H8)......................................................................................18

Annex <Z> (informative): Change History (style H8).................................................................................19

History (style H1)..............................................................................................................................................

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)5

Release #2

<PAGE BREAK>

Intellectual Property Rights (style H1)

Essential patents

IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https://ipr.etsi.org).

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.

Trademarks

The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.

Foreword (style H1)

This unnumbered clause is mandatory and shall appear just after the IPR clause.

Replace all <parameters> with the appropriate text.

This Group Specification (GS) has been produced by ETSI Industry Specification Group <long ISGname> (<short ISGname>).

Multi-part documentsThe following block is required in the case of multi-part deliverables.

the <common element of the title> is the same for all parts;

the <part element of the title> differs from part to part; and if appropriate;

the <sub-part element of the title> differs from sub-part to sub-part.

For more details see clause 2.5 of the ETSI Drafting Rules (EDRs).

The best solution for maintaining the structure of series is to have a detailed list of all parts and subparts mentioned in one of the parts (usually it is part 1).

If you choose this solution, the following text has to be mentioned in all of the other parts and sub-parts:

The present document is part <i> of a multi-part deliverable. Full details of the entire series can be found in part [x] [Bookmark reference].

Modal verbs terminology (style H1)

This unnumbered clause is a mandatory informative element and shall appear just after the "Foreword".

In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).

"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)6

Release #2

Executive summary (style H1)

This unnumbered clause, if present, appears after the "Modal verbs terminology" and before the "Introduction". It is an optional informative element and shall not contain requirements.

The "Executive summary" is used, if required, to summarize the ETSI deliverable. It contains enough information for the readers to become acquainted with the full document without reading it. It is usually one page or shorter.

Introduction (style H1)

This unnumbered clause, if present, appears just before the "Scope". It is an optional informative element and shall not contain requirements.

CLAUSE NUMBERING STARTS HEREAFTER.

Automatic numbering may be used in ETSI deliverables but it is highly recommended to use sequence numbering.For more details see clause 2.12.1.1 and 6.9.2 of the ETSI Drafting Rules (EDRs).

Editor’s note: Describe here: How can NFV APIs conformance be beneficial for NFV interoperability. Still, conformance is necessary but not always sufficient for interoperability. Therefore, this work is complementary with NFV TST 007 [REF].

Editor’s note: Explain here the goals of the methodology such as testing both “syntactical” and “semantic” conformance of the operations – which means checking on the actual result of the operations, to leverage any possible degree of automation (generation of the test suite out of OpenAPIs as well as entirely automated test execution supported), openness towards any organizations and especially Open Source initiatives.

<PAGE BREAK>

1 Scope (style H1)

This clause numbered 1 shall start on a new page. More details can be found in clause 2.9 of the EDRs.

The Scope shall not contain requirements. Forms of expression such as the following should be used:

Scope of API conformance is the functionality test in an automated way for ETSI NFV APIs as defined by SOL WG.

Editor’s note: Insert references of all APIs in scope

Editor’s note: correct and expand.

The goal of the present document is to specify the means to test conformance of NFV implementations with specific interfaces as in the following NFV specifications: NFV SOL 002 [REF] for the Ve-Vnfm reference point, NFV SOL 003 [REF] for the Or-Vnfm reference point and NFV SOL 005 [REF] for the Os-ma-nfvo reference point.

Each deliverable specifies a set of interfaces built on the on the RESTful approach and meant to be used over the HTTP protocol. The aim of the present document is to define the methodologies and the procedures to test conformance of the exchanged HTTP payloads and the implementation of required actions for one or more of the available interfaces within a reference point.

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)7

Release #2

2 References (style H1)

This clause numbered 2 appears just after the "Scope". It is a required element.

The following text block applies. More details can be found in clause 2.10 of the EDRs.

2.1 Normative references (style H2)

Clause 2.1 only shall contain normative (essential) references which are cited in the document itself. These references have to be publicly available and in English.

Legal acts can never be used as normative references

References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.

Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference.

NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.

The following referenced documents are necessary for the application of the present document.

Use the EX style, enclose the number in square brackets and separate it from the title with a tab (you may use sequence fields for automatically numbering references, see clause 6.9.2: "Sequence numbering") (see example).

EXAMPLE:

[1][tab] <Standard Organization acronym> <document number>: "<Title>".

[2][tab] <Standard Organization acronym> <document number>: "<Title>".

2.2 Informative references (style H2)

Clause 2.2 shall only contain informative references, which are cited in the document itself.

References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.

NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.

The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.

[1] ETSI EG 202 237: “Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Generic approach to interoperability testing”.

[2] ETSI EG 202 568: “Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Testing: Methodology and Framework”.

[3] ISO/IEC 9646-1: “Information Technology - Open Systems Interconnection – Conformance Testing Methodology and Framework - Part 1: General concepts”.

[4] Robot Framework: http://robotframework.org

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)8

Release #2

3 Definitions, symbols and abbreviations (style H1)

Delete from the above heading the word(s) which is/are not applicable, (see clause 2.11 of EDRs).

Definitions and abbreviations extracted from ETSI deliverables can be useful when drafting documents and can be consulted via the Terms and Definitions Interactive Database (TEDDI) (https://webapp.etsi.org/Teddi/).

3.1 Definitions (style H2)

Clause numbering depends on applicability.

A definition shall not take the form of, or contain, a requirement.

The form of a definition shall be such that it can replace the term in context. Additional information shall be given only in the form of examples or notes (see below).

The terms and definitions shall be presented in alphabetical order.

The following text block applies. More details can be found in clause 2.11.1 of the EDRs.

For the purposes of the present document, the [following] terms and definitions [given in ... and the following] apply:

Definition format Use the Normal style.

The term shall be in bold, and shall start with a lower case letter (unless it is always rendered with a leading capital) followed by a colon, one space, and the definition starting with a lower case letter and no ending full-stop.

<defined term>: <definition>

EXAMPLE: text used to clarify abstract rules by applying them literally

NOTE: This may contain additional information.

3.2 Symbols (style H2)

Symbols should be ordered alphabetically. Clause numbering depends on applicability.

The following text block applies. More details can be found in clause 2.11.2 of the EDRs.

For the purposes of the present document, the [following] symbols [given in ... and the following] apply:

Symbol format Use the EW style and separate this from the definition with a tab. Use the EX style for the last term.

<1st symbol> [tab]<1st Explanation> (style EW)<2nd symbol> [tab]<2nd Explanation> (style EW)<3rd symbol> [tab]<3rd Explanation> (style EX)

3.3 Abbreviations (style H2)

Abbreviations should be ordered alphabetically. Clause numbering depends on applicability.

The following text block applies. More details can be found in clause 2.11.2 of the EDRs.

For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)9

Release #2

Abbreviation format Use the EW style and separate this from the definition with a tab. Use the EX style for the last term.

<1st ACRONYM> [tab]<Explanation> (style EW)<2nd ACRONYM> [tab]<Explanation> (style EW)<3rd ACRONYM> [tab]<Explanation> (style EX)

4 Methodology (style H1)

4.1 General Editor’s note: explain the relationship between this WI (conformance) and Plugtest, interoperability in general (maybe in scope)

Editor’s note: Quote or reference NFV TST 002 definition of conformance

The purpose of general conformance testing is to determine to what extent a single implementation of a particular standard conforms to the individual requirements of that standard. (as defined in ETSI EDR [REF]).

The important factors which characterize conformance testing are as follows:

the System or Implementation Under Test (SUT or IUT) defines the boundaries (open interfaces) for testing; the conformance test system is a specialized tool (system) built for the purpose of testing and on which specific

test scripts can be run;  the SUT comes from a single supplier (or, at least, a single product line);  the tests are executed by a dedicated test system that has full control of the SUT and the ability to observe all

communications from the SUT;  the tests are performed at open standardized interfaces that are not (usually) accessible to a normal user (i.e.

they are specified at the protocol level);  the tests are specified at the detailed protocol level and are not usually based on functionality as experienced

by a user. the tests verify response or related request operation from SUT.

Editor’s note: Insert other relevant documents and general definitions

4.2 System under test Editor’s note: generic description of producer and consumer under test. Introduce the terminology

The system under test is identified by an implementation of the function under test producing or consuming the API under test e.g. in the case of the Or-vnfm reference point the function under test may be either a NFVO implementation or a NVFM implementation.

The function shall be tested in isolation with respect to other functional blocks in a NFV platform, to guarantee that the outcomes of the conformance tests are not result of interoperability issues with other components.

Editor’s note: there is a corner case when the SUT is going to ask the TestSys some info in order to respond (e.g. VNFM with NFVO). In this case the SUT needs to be instructed not to use the initiator of the request as a real component.

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)10

Test Environment Test system

FUT

AUT

API Consumer 

Notification Endpoint 

API exchangesAPI notificationsTest interface

Release #2

4.3 Test configurationsEditor’s note: discussion on the isolation of the FUT. Test environment needed?

Editor’s note: Here are described the test configurations, i.e. function under tests, test system and its components and their reciprocal connections. All the test configurations are described and assigned a unique identifier, to be later on referenced.

4.3.1 General In accordance with Sect. 1, the scope of the present document is to define a testing methodology and test suite for both the conformant protocol exchange (i.e. valid serialization and order of messages) and the initialization or execution of the functionalities mandated for each protocol operation, including the conformant management of internal state.

In order to enable the FUT to correctly execute the operations mandated the FUT shall be tested while being executed in a test environment (TSTENV) which provides all the functional elements needed for the correct outcome of the operation.

NOTE: For example, to correctly execute an instantiation a VNFM requires to be executed in a test environment which provides a VIM and NFVI plus the NFVO to grant the operation.

The test system shall provide the implementation of an API Consumer and a Notification Endpoint for the API Under Test (AUT). Moreover, the test configuration may contain observation interfaces between the Test System and the FUT or any other functional block which is part of the test environment. The specification of the mentioned observation interfaces is out of the scope of the present document.

Stimuli to the FUT shall be injected by the Test System via the AUT only.

Conformance checks on the status and outcome of the operations triggered by the protocol shall be verified by the Test System by means of:

read operations issued via the AUT or reception of notifications on the Notification Endpoint exposed by the test system or other test interfaces to support triggers or verifications.

Fig X: Generic SUT configuration

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)11

Test Environment Test system

VNF/EM

AUT

API Consumer 

Notification Endpoint 

API exchangesAPI notificationsTest interface

Test Environment Test system

VNFM

AUT

API Consumer 

Notification Endpoint 

API exchangesAPI notificationsTest interface

Release #2

The test configurations specified in the following clauses fulfil the requirements stated below for the different FUTs and AUTs in scope of the present specification.

4.3.2 Config_prod_VEThe configuration config_prod_VE shall be implemented to test APIs which are produced by FUTs in a VNF or EM. The test environment of the VNF/EM is the NFVI where the it is executed.

Figure 0-1:Configuration for tests of APIs with a FUTs as Producer run in a VNF/EM.

4.3.3 Config_prod_VNFM

The configuration config_prod_VNFM shall be implemented to test APIs produced by FUTs which implement a VNFM. The test environment of the virtual element is the NFVI where the VE is executed.

IMG TBD

Figure 0-2: Configuration for tests of APIs with VNFM as Producer.

4.3.4 Config_prod_NFVO

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)12

Test Environment Test system

NFVO

AUT

API Consumer 

Notification Endpoint 

API exchangesAPI notificationsTest interface

Release #2

The configuration config_prod_NFVO shall be implemented to test APIs produced by FUTs which implement a NFVO. The test environment of the virtual element is an NFV platform providing VNFM, VIM and NFVI.

Figure 0-3: Configuration for tests of APIs with NFVO as Producer.

4.5 Generic test description

4.5.1 General Editor’s note: the selected test description language will be described here

The machine readable language used for the test descriptions is the Robot Framework [4].

4.5.2 Scope of the tests Editor’s note: examples: content of the messages to be tested, logic, etc

4.5.3 Verification Test system verifies URIs, HTTP headers and payloads of responses from SUT.

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)13

Release #2

Figure X-X: verification procedure.

Editor’s note: A verification method and steps for each items is FFS.

4.5.4 Test templates

4.6 Test Suite StructureEach test case in the scope of this document will be uniquely identifies by the fields identified in Table XX:

FieldDescription

Example

Reference point

TBD TBD

Interface TBD TBD

Operation TBD TBD

Function under test

TBD TBD Editor’s note: (producer/consumer)

Expected outcome

TBD TBD

Editor’s note: Specify a table with all possible identifiers for the fields below

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)14

Release #2

5 Os-Ma-Nfvo Reference Point

5.1 General

5.2 ICS

5.2 Test configuration

5.3 Interface #1 (TBD)

5.3.1 Operation #1

5.3.2 Operation #2

5.4 Interface #2

6 Ve-Vnfm Reference Point

6.1 General

6.2 Test configuration

6.3

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)15

Release #2

7 Or-Vnfm Reference Point

7.1 General Or-Vnfm is the reference point between NFVO and VNFM, and the RESTful protocol for that reference point is specified in ETSI NFV SOL003 [1]. This clause describes the basic principles of the SOL 003 which shall be considered in API conformance test.

From the API conformance test point of view, Or-Vnfm reference point has below characteristics:

NOTE: The “notification” may be optional.

Asynchronous API and State handling by notifications

Due to the varieties of the reasons, e.g. consuming time of process handling, “VNF Lifecycle Management interface” defined in SOL003 [1] clause 5 is designed as asynchronous way, i.e. API designed is based on the combination of the specific methods with task resources and state handling by related attributes signalled via notification messages.

For example, the operation “Instantiate VNF” is triggered by POST message with task “Instantiate VNF” sent from NFVO to VNFM , then VNFM sends “provisional” response “202 accepted” back to NFVO, which means “accepted request” (SOL003 [1] clause5.4.4). Based on the subscriptions registered in VNFM, the appropriate notification message will be sent toward NFVO with the state of the processing in the VNFM at that time. After finishing the process of instantiating VNF in the VNFM, the notification message with the notification endpoint resource which is set to “operationState=COMPLETED” shall be sent (SOL003 [1] clause5.4.18 and clause 5.4.20), which mean that the VNF has been instantiated.

Linked resource

According to the SOL003 [1] clause 4.3.3.1, “link” pointing to the resources which may be fetched by API consumer, may be used on the reference point. It is used in order to avoid “big” response messages and to avoid repeating information request messages. Therefore the validity of such linked resources shall also be verified by test, as same as resources in the response message itself.

7.2 Test configuration

7.3

From clause 4, the technical content of the deliverable shall be inserted. Each clause shall have a title which shall be placed after its number separated by a tab.

A clause can have numbered subdivisions, e.g. 5.1, 5.2, 5.1.1, 5.1.2, etc. This process of subdivisions may be continued as far as the sixth heading level (e.g. 6.5.4.3.2.1).

For numbering issues, see clause 2.12.1 of the EDRs.

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)16

Release #2

Use the Heading style appropriate to its level (see clause 6.1, table 8 of the EDRs).

Separate the number of the heading and the text of the heading with a tab.

Treat clause titles as normal text (i.e. no additional capitalization), but no full stop.

IF YOUR DOCUMENT CONTAINS FIGURES, TABLES AND/OR MATHEMATICAL FORMULAE, THIS IS THE WAY THEY SHALL BE PREPARED:

- Figures shall be prepared in accordance to clauses 7.5.2 and/or 7.1 of the EDRs. The figure number and title shall be below the figure. An explicit figure title is optional. See clause 5.1.5 if you need to include notes to figures.

Use TF style for the figure number and title.

Use FL style on the paragraph which contains the figure itself.

If applicable, the figure number is followed by a colon, a space and the table title.

Maximum width for figures is 17 cm and maximum height is 22 cm.

Should you wish to number figures automatically, "Sequence numbering and bookmarking" (see clause 6.9.2 of the EDRs) is highly recommended.

- Tables shall be prepared in accordance to clause 5.2 of the EDRs. If you have tables in your document, the table number and title shall be above the table itself. An explicit table title is optional.

Use TH style for the table number and title.

If applicable, the table number is followed by a colon, a space and the table title.

Should you wish to number tables automatically, "Sequence numbering and bookmarking" (see clause 6.9.2 of the EDRs) is highly recommended.

- Mathematical formulae shall be prepared in accordance to clause 5.3 of the EDRs.

Numbers given to the clauses, tables, figures and mathematical formulae of an annex shall be preceded by the letter designating that annex followed by a full-stop (e.g. figure B.1, table C.4). The numbering shall start afresh with each annex. A single annex shall be designated "Annex A".

NOTE: For an easy application of the ETSI styles download "the ETSI styles toolbar" from editHelp! website.

AnnexesEach annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.).

Numbers given to the clauses, tables, figures and mathematical formulae of an annex shall be preceded by the letter designating that annex followed by a full-stop. The numbering shall start afresh with each annex. A single annex shall be designated "Annex A".

Clauses in annex A shall be designated "A.1", "A.2", "A.3", etc. (further details in clause 2.12.1 of the EDRs).

Use the Heading 8 style. Insert a line break ("shift" + "enter") between the colon and the title.

For all annex clause headings use the appropriate Heading styles, starting from Heading 1, e.g. for clause A.1 use Heading 1, for clause A.1.1 use Heading 2. (See clause 6.1, table 8 of the EDRs).

<PAGE BREAK>

Annex A (normative or informative):Title of annex (style H8)

<Text>.

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)17

Release #2

<PAGE BREAK>

Annex B (normative or informative):Title of annex (style H8)

B.1 First clause of the annex (style H1)

B.1.1 First subdivided clause of the annex (style H2)

<Text>.

<PAGE BREAK>

Annex <X> (informative):Authors & contributors (style H8)

The annex entitled "Authors & contributors" is optional. When present it describes the list of persons and companies that contributed to the elaboration of the present Group Specification.

The following people have contributed to the present document:

Rapporteur:Title, Firstname, Lastname, company

Other contributors:Title, Firstname, Lastname, company

<PAGE BREAK>

Annex <Y> (informative):Bibliography (style H8)

This optional informative clause shall start on a new page and be the last annex of an ETSI deliverable or the last but one if followed by the "Change history/Change request history" annex, if any. The Bibliography shall not contain requirements.

The Bibliography identifies additional reading material not mentioned within the document. Those publications might or might not be publicly available (no check is made by the ETSI Secretariat).

The Bibliography shall include list of standards, books, articles, or other sources on a particular subject which are not referenced in the document.

The Bibliography shall not include references mentioned in the deliverable.

Use Heading 8 style for the "Bibliography" annex, see clause 2.13 for examples.

For the listed material use the Normal style or bulleted lists (e.g. B1+), do not use numbered references.

<Publication>: "<Title>".

OR

<Publication>: "<Title>".

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)18

Release #2

<PAGE BREAK>

Annex <Z> (informative):Change History (style H8)

The informative clause shall start on a new page and be the last annex before the "History" clause. It is an optional, informative element and shall not contain requirements.

If it is desired to keep a detailed record of the changes implemented in a new version it is recommended that this is done by inserting a "Change history/Change request" annex, see clause 2.15.

It shall be presented as a table. Apply the normal style format for tables (see clause 5.2.2 of the EDRs).

Date Version Information about changes

October 2011 1.1.1 First publication of the GS after approval(30 September - 2 October 2011; Prague)

February 2012 1.2.1

Implemented Change Requests:Error message information clarificationsRevised error message informationupdate of figure 3 clause 9.2Version 1.2.1 prepared by the Rapporteur

July 2013 1.3.1 Version 1.3.1 prepared by the Rapporteur

<PAGE BREAK>

History (style H1)

Document history

<Version> <Date> <Milestone>

0.0.1 Skeleton

0.0.2 Apr 8 2018 NFVTST(18)000021r2: TST010 - Scope and inputs for the methodology

0.0.3 July 11, 2018 NFVTST(18)000059r1: Test configuration introduction

0.0.4 Nov 9, 2018 NFVTST(18)000106r1 - TST010 -Test Language SelectionNFVTST(18)000124r3 - TST010 Clarify Asynchronous API of Or-Vnfm reference pointNFVTST(18)000134 - TST010 Clarify linked resources of Or-Vnfm reference point

0.0.5 Nov 21 2018 NFVTST(18)000084r1 - TST010 Add verification

Latest changes made on 2017-07-10

ETSI

ETSI GS NFV-TST010 V0.0.5 (2018-11)19