1、 ETSI GR NFV-TST 004 V1.1.1 (2017-05) Network Functions Virtualisation (NFV); Testing; Guidelines for Test Plan on Path Implementation throught NGVI Disclaimer The present document has been produced and approved by the Network Functions Virtualisation (NFV) ETSI Industry Specification Group (ISG) an
2、d represents the views of those members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP REPORT ETSI ETSI GR NFV-TST 004 V1.1.1 (2017-05) 2 Reference DGR/NFV-TST004 Keywords NFV, NFVI, SDN, testing ETSI 650 Route des Lucioles F-06921 Soph
3、ia 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 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The pr
4、esent 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 ver
5、sions 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
6、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 N
7、o 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 f
8、oregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for t
9、he 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 Trade Marks registered and owned by the GSM Association. ETSI ETSI GR NFV-TST 004 V1.1.1 (2017-05) 3 Contents Intellectual Property Rights 4g3Foreword .
10、 4g3Modal verbs terminology 4g3Introduction 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Test Plan and Approach . 8g35 Taxonomy of Options for SUT 9g36 Metrics and Methods of
11、 Measurement . 10g37 Test Procedures 13g37.1 Prerequisites . 13g37.2 Virtual Machine and VNF Instantiation . 13g37.3 Network Preparation and Address Assignment 13g37.4 Path Instantiation 13g37.5 Path Performance . 14g38 Results Presentation . 14g39 Follow-on Activities . 14g3Annex A: Example of Prer
12、equisites for Path Testing . 15g3A.1 Description and Figures of the System Under Test (SUT) . 15g3Annex B: Examples of Measurements and Results for Path Testing 19g3B.1 Instantiation Time Measurements 19g3B.2 Latency Measurements . 20g3B.2.1 Introduction 20g3B.2.2 First Packet Latency . 21g3B.2.3 Su
13、bsequent Packet Latency 21g3Annex C: Authors 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 investi
14、gation, 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
15、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 t
16、he present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) Network Functions Virtualisation (NFV). Modal verbs terminology In the
17、present document “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
18、in direct citation. Introduction There are many technological options available to implement paths through the Network Function Virtualisation Infrastructure (NFVI) to realize Virtual Network Forwarding Graphs (VNFFG) or Service Function Chains (SFC). In the present document, paths can be composed o
19、f physical and virtual links (including wide-area network links connecting locations and their NFVI), physical and virtual switches and routers, and other virtual network functions (VNF). VNFs are composed of one or more VNF Components (VNFC). VNFC are synonymous with Virtual Machines (VM) or OS con
20、tainers (OSC) as in ETSI GS NFV 003 i.21. A VM or OSC is referred to with the general term virtualization container in the present document. The present document is motivated by the design needs of many NFV actors. Service Providers and NFVI Operators need to select the best alternatives in order to
21、 implement cost-effective services. NFVI Providers and VNF Providers need to understand the preferred alternatives so they can support them efficiently. What configurations work well in combination, and possibly enhance performance? How can the actors above begin to objectively evaluate the various
22、alternatives? These questions are to be evaluated before NFV deployments, and re-evaluated as new technology alternatives emerge. The present document recognizes the need to evaluate the various path-implementation alternatives operating together, and begins by providing a high level test plan. Ulti
23、mately, the results from tests comparing the alternatives may influence the architectural choices when implementing the NFV framework. ETSI ETSI GR NFV-TST 004 V1.1.1 (2017-05) 5 1 Scope The present document provides guidelines for test plans that assess different approaches to defining SDN Applicat
24、ions, different ways of arranging and federating SDN Controllers, and arrangements of network switching/forwarding functions (both physical and virtual) to create the various path-implementations between and among NS Endpoints and VNFs. These guidelines support development of detailed test plans, an
25、d ultimately influence the NFV framework (when testers share their results from testing arrangements encouraged by these guidelines). The test plan guidelines should be sufficiently abstract to include all envisioned possibilities, and will also pursue the details of technologies of interest. Althou
26、gh the primary emphasis of testing is the performance and benchmarking of systems composed of the components above, the attempts to combine different protocols and functions will undoubtedly uncover combinations which are non-interoperable, and these should be noted. 2 References 2.1 Normative refer
27、ences Normative references are not applicable in the present document. 2.2 Informative 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 refe
28、rences, 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
29、 of the present document but they assist the user with regard to a particular subject area. i.1 ETSI GS NFV-EVE 005 (V1.1.1) (2015-12): “Network Functions Virtualisation (NFV); Ecosystem; Report on SDN Usage in NFV Architectural Framework“. i.2 IETF RFC 6241(June 2011): “Network Configuration Protoc
30、ol (NETCONF)“. i.3 ONOSTM. NOTE: Available at http:/onosproject.org/. i.4 OpenDaylightTM. NOTE: Available at http:/www.opendaylight.org/. i.5 OpenContrailTM. NOTE: Available at http:/www.opencontrail.org/. i.6 FloodlightTM. NOTE: Available at http:/www.projectfloodlight.org/floodlight/. i.7 OpenStac
31、kTMSM. NOTE: Available at https:/www.openstack.org/. i.8 IETF RFC 4271 (January 2006): “A Border Gateway Protocol 4 (BGP-4)“. i.9 IETF RFC 5440 (March 2009): “Path Computation Element (PCE) Communication Protocol (PCEP)“. ETSI ETSI GR NFV-TST 004 V1.1.1 (2017-05) 6 i.10 OpenFlowSM. NOTE: Available a
32、t https:/www.opennetworking.org/sdn-resources/openflow. i.11 P4TMlanguage for programming the network dataplane. NOTE: Available at http:/p4.org/. i.12 ETSI GS NFV-INF 003 (V1.1.1) (2014-12): “Network Functions Virtualisation (NFV); Infrastructure; Compute Domain“. i.13 VLOOP-VNF. NOTE: Available at
33、 https:/lists.linuxfoundation.org/pipermail/opnfv-tech-discuss/2015-May/002601.html. i.14 IETF RFC 7348 (August 2014): “Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks“. i.15 IETF RFC 7432 (February 2015): “BGP MPLS-Based E
34、thernet VPN“. i.16 IETF RFC 1701 (October 1994): “Generic Routing Encapsulation (GRE)“. i.17 Internet Draft (Work in Progress): “Geneve: Generic Network Virtualization Encapsulation, draft-ietf-nvo3-geneve-04“. i.18 Internet Draft (Work in Progress): “Network Service Header, draft-ietf-sfc-nsh-11“.
35、i.19 Internet Draft (Work in Progress): “Benchmarking Methodology for SDN Controller Performance, draft-ietf-bmwg-sdn-controller-benchmark-meth-03“. i.20 ETSI GS NFV-INF 010 (V1.1.1) (2014-12): “Network Functions Virtualisation (NFV); Service Quality Metrics“. i.21 ETSI GS NFV 003 (V1.2.1) (2014-12)
36、: “Network Functions Virtualisation (NFV); Terminology for Main Concepts in NFV“. i.22 ETSI GS NFV-TST 001 (V1.1.1) (2016-04): “Network Functions Virtualisation (NFV); Pre-deployment Testing; Report on Validation of NFV Environments and Services“. i.23 IETF RFC 2544 (March 1999): “Benchmarking Metho
37、dology for Network Interconnect Devices“. i.24 IETF RFC 2889 (August 2000): “Benchmarking Methodology for LAN Switching Devices“. i.25 ETSI GS NFV-IFA 003 (V2.1.1) (2016-04): “Network Functions Virtualisation (NFV); Acceleration Technologies; vSwitch Benchmarking and Acceleration Specification“. i.2
38、6 Internet Draft (Work in Progress): “Benchmarking Virtual Switches in OPNFV, draft-ietf-bmwg-vswitch-opnfv-01“. i.27 Open Platform for NFV VSPERF Project. NOTE: Available at https:/wiki.opnfv.org/display/vsperf. i.28 IETF Benchmarking Methodology Working Group (BMWG). NOTE: Available at https:/data
39、tracker.ietf.org/wg/bmwg/documents/. i.29 ETSI GS NFV-PER 001 (V1.1.2) (2014-12): “Network Functions Virtualisation (NFV); NFV Performance - OpenFlow 1.3 Network Resource control (south bound) interface. ACL SDN application: Network Intent Composition (NIC) with ODL Beryllium Release, SR4, embedded
40、in controller or RESTconf application (north bound) interface. vSwitch: OVS version 2.0.2 and Kernel version (mininet 2.1.0+). VIM and virtualization layer: mininet 2.1.0+. ETSI ETSI GR NFV-TST 004 V1.1.1 (2017-05) 16 The following NFVI configuration parameters are fixed for this testing: Table A.1:
41、 NFVI Configuration Parameters Configuration Parameter Value Host Processor 2,5 GHz Intel Core i7 Dedicated Cores 2 (shared for all VM resources) Memory 8 192 MB (1 600 MHz DDR3) Acceleration KVM Paravirtualization, VT-x, Nested Paging OS Ubuntu 14.04 LTS 64 bit (Guest in Virtual Box 5.x on Mac OSX
42、10.11.5) The following metrics will be collected for each alternative test configuration: VNF Instantiation Time Path Instantiation Time First Packet Latency Standard Packet Transfer Performance Metrics (loss, delay, delay variation) Provisioning Latency for the SDN Controller and VIM are desirable
43、metrics to measure, where applicable. It is also helpful to illustrate the packet headers at key points in the SUT, especially when overlay networking and encapsulation is used. In this example, all data path packets use IP and Ethernet headers, and so the figures are omitted for simplicity. Figure
44、A.1: ACL in VNF, vSwitch (Kernel and OVS) internal control for L2 switching, shared host with router function ETSI ETSI GR NFV-TST 004 V1.1.1 (2017-05) 17 Figure A.2: ACL in VNF, vSwitch with independent SDN control, shared host with router function Figure A.3: ACL in vSwitch with independent SDN co
45、ntrol and ACL SDN Application, shared host with router function ETSI ETSI GR NFV-TST 004 V1.1.1 (2017-05) 18 NOTE 1: ToR Switches provide connectivity between hosts. NOTE 2: Either a cross-connect cable or physical switch provides connectivity between Hosts (not shown). Figure A.4: ACL in VNF, vSwit
46、ch with independent SDN control, ACL VNFCs in separate hosts from router function NOTE 1: ToR Switches provide connectivity between hosts. NOTE 2: Either a cross-connect cable or physical switch provides connectivity between Hosts (not shown). Figure A.5: ACL in vSwitch with independent SDN control
47、and ACL SDN Application, ACL in vSwitches in separate hosts from router function ETSI ETSI GR NFV-TST 004 V1.1.1 (2017-05) 19 Annex B: Examples of Measurements and Results for Path Testing B.1 Instantiation Time Measurements As described in clause 7, clear presentation of the results adds value to t
48、he study. This experiment was conducted using mininet as the VIM. mininet uses process virtualization to create network resources (network namespaces) and hosts, which is similar to Linux containers but with fewer features. As a result VNF and Path Instantiation times are extremely fast with mininet
49、, but all aspects of mininet share the compute environment with their host. The steps to establish the figure A.2 path with OVS and ODL controller are shown below as an example of the procedure (which could be scripted for automation, as mentioned in clause 4, item 7): The line below adds the features to the ODL controller, once started (with ./bin/karaf), and completion of this step comprises the SDN Controller Instantiation Time: opendaylight-userrootfeature:install odl-restconf-all odl-mds
