ETSI GS NFV-EVE 001-2017 Network Functions Virtualisation (NFV) Virtualisation Technologies Hypervisor Domain Requirements specification (V3 1 1 Release 3).pdf

1、 ETSI GS NFV-EVE 001 V3.1.1 (2017-07) Network Functions Virtualisation (NFV); Virtualisation Technologies; Hypervisor Domain Requirements specification; Release 3 Disclaimer The present document has been produced and approved by the Network Functions Virtualisation (NFV) ETSI Industry Specification

2、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. GROUP SPECIFICATION ETSI ETSI GS NFV-EVE 001 V3.1.1 (2017-07)2 Reference DGS/NFV-EVE001 Keywords network, NFV, virtualisation ETSI 650 Route

3、des Lucioles F-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 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.or

4、g/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

5、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 st

6、atus. 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

7、 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

8、. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand 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 Me

9、mbers 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-EVE 001 V3.1.1 (2017-07)3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs termi

10、nology 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Hypervisor Domain Overview . 7g35 Requirements of the Hypervisor Domain . 9g35.1 Introduction 9g35.2 General Requirements

11、9g35.3 Real Time Guest Support . 10g35.4 vSwitch Resiliency . 10g35.5 NFV Acceleration Support . 10g35.6 Security 11g35.7 Energy Efficiency requirements . 11g35.8 Performance management requirements 11g3Annex A (informative): Authors Essential, or potentially Essential, IPRs notified to ETSI in resp

12、ect 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

13、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 o

14、wnership 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 associate

15、d with those trademarks. Foreword This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Network Functions Virtualisation (NFV). Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “c

16、an“ 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-EVE 001 V3.1.1 (2017-07)5 1 Scope The present

17、 document provides requirements for the hypervisor domain as it pertains to an operators network. It focuses on gaps between Network Functions Virtualisation (NFV) use cases and the industry state of art at the time of publication. Therefore requirements that are deemed to be supported by most hyper

18、visor solutions at the time of publication are not repeated in the present document. 2 References 2.1 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 appli

19、es. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this

20、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. 1 ETSI GS NFV 003: “Network Functions Virtualisation (NFV); Terminology for Main Concepts in NFV“. 2 ETSI GS NFV

21、-IFA 002: “Network Functions Virtualisation (NFV); Acceleration Technologies; VNF interfaces specification“. 3 ETSI GS NFV-IFA 004: “Network Functions Virtualisation (NFV); Acceleration Technologies; Management aspects specification“. 4 ETSI GS NFV-IFA 018: “Network Functions Virtualisation (NFV); A

22、cceleration Technologies; Network Acceleration Interface Specification“. 5 ETSI GS NFV-IFA 019: “Network Functions Virtualisation (NFV); Acceleration Technologies; Acceleration Resource Management Interface Specification“. 6 ETSI GS NFV-SEC 012: “Network Functions Virtualisation (NFV); Security; Sys

23、tem architecture specification for execution of sensitive NFV components“. 7 Unified Extensible Firmware Interface Forum: “Advanced Configuration and Power Interface Specification (ACPI)“. NOTE: Available at http:/www.uefi.org/specifications. 8 ETSI GS NFV-TST 008: “Network Functions Virtualisation

24、(NFV); Testing; NFVI Compute and Network Metrics Specification“. 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 references

25、, 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. ETSI ETSI GS NFV-EVE 001 V3.1.1 (2017-07)6 The following referenced documents

26、are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI GS NFV-INF 004: “Network Functions Virtualisation (NFV); Infrastructure; Hypervisor Domain“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of t

27、he present document, the terms and definitions given in ETSI GS NFV 003 1 and the following apply: hypervisor: piece of software which partitions the underlying physical resources and creates Virtual Machines, and isolates the VMs from each other NOTE: The hypervisor is a piece of software running e

28、ither directly on top of the hardware (bare metal hypervisor) or running on top of a hosting operating system (hosted hypervisor). The abstraction of resources comprises all those entities inside a computer/server which are accessible, like processor, memory/storage, NICs. hypervisor domain: general

29、 area for focus which includes hypervisors NOTE: Other elements such as a vswitch can be implemented in the hypervisor domain. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI GS NFV 003 1 and the following apply: ACPI Advanced Configuration and Power Inter

30、face CD Compute Domain DOPFR Dynamic Optimization of Packet Flow Routing EPD Extended Para-virtualised Device eSwitch embedded Switch HD Hypervisor Domain IND Infrastructure Networking Domain INF Infrastructure MWAIT Monitor Wait NOTE: x86 Instruction Set Reference. NFVI NFV Infrastructure NIC Netwo

31、rk Interface Controllers RDMA Remote Direct Memory Access RDTSC Read Time-Stamp Counter NOTE: x86 Instruction Set Reference. RDTSCP Read Time-Stamp Counter and Processor identifier NOTE: x86 Instruction Set Reference. VIM Virtualisation Infrastructure Manager VM Virtual Machine VN Virtual networkVNF

32、C Virtualised Network Function Component vRouter virtual Router vSwitch virtual SwitchETSI ETSI GS NFV-EVE 001 V3.1.1 (2017-07)7 4 Hypervisor Domain Overview Figure 4-1 describes the logical placement of the hypervisor domain, which is circled in dotted lines, within the NFV architectural framework.

33、 The hypervisor domain abstracts the hardware resources from the compute domain. The hypervisor domain overlaps with the network domain in that it can include virtual switch (vSwitch) and virtual router (vRouter) software elements and abstract network-related hardware resources provided by the compu

34、te domain such as network interface controllers (NIC) and embedded switches (eSwitch). There is a direct reference point to the Virtualisation Infrastructure Manager (VIM) from the hypervisor domain. Figure 4-1: Logical placement of the hypervisor domain The hypervisor domain itself is a software en

35、vironment which abstracts hardware and implements services, such as starting a Virtual Machine (VM), terminating a VM, acting on policies, scaling, live migration, and high availability. Figure 4-2 provides a more detailed view of the hypervisor domain and its reference points to the other elements

36、of the architectural framework. The following reference points are identified: a) The Nf-Vi/H reference point provides the interfaces to the VIM. This is where the requests for hypervisor services occur. Only the VIM shall interact with the hypervisor through these interfaces. Hypervisors shall not

37、implement services autonomously unless within the context of the VIM applied policy. b) The Vi-Ha/Csr reference point provides the interfaces that the hypervisor pulls hardware information from and uses to create virtual hardware components which the VM utilizes. c) The Vn-Nf/VM reference point repr

38、esents the execution environment provided by the NFVI to a VNF. A VNF is created essentially via one or more VMs. A VM is in essence software running a function, algorithm, application without being aware of the type, model or number of actual physical units underneath the function, algorithm and/or

39、 application. The purpose of the other reference points identified in figure 4-2 are described in table 1 of ETSI GS NFV-INF 004 i.1. ETSI ETSI GS NFV-EVE 001 V3.1.1 (2017-07)8 Figure 4-2: Hypervisor domain reference points The general architecture of the hypervisor domain is shown in figure 4-3. Fi

40、gure 4-3 also illustrates how VMs interact with CPU cores, NICs and vSwitches. It highlights that high performance VMs can be given: exclusive access to specific CPU cores; exclusive access to allocated memory regions; direct access the physical NICs using direct memory mapped polled drivers and use

41、r mode instructions requiring no context switching; direct memory mapped polled drivers for interVM communications using user mode instructions requiring no context switching. ETSI ETSI GS NFV-EVE 001 V3.1.1 (2017-07)9 Figure 4-3: Example hypervisor architecture 5 Requirements of the Hypervisor Doma

42、in 5.1 Introduction Some of the requirements on the hypervisor domain are implicitly placing requirements on the underlying hardware. If the hardware does not fulfil such requirements, then the corresponding hypervisor requirements cannot be fulfilled. 5.2 General Requirements Table 5.2-1 specifies

43、general requirements applicable to the hypervisor domain. Table 5.2-1: general requirements Numbering Requirement description REQ.HYP.GEN.001 The hypervisor shall support partitioning of the resources of a compute node. REQ.HYP.GEN.002 The hypervisor should support nested virtualisation. REQ.HYP.GEN

44、.003 The hypervisor shall support acceleration requirements as specified in ETSI GS NFV-IFA 002 2. REQ.HYP.GEN.004 The hypervisor should support partitioning of the resources. ETSI ETSI GS NFV-EVE 001 V3.1.1 (2017-07)10 5.3 Real Time Guest Support Table 5.3-1 specifies requirements for supporting re

45、al time VM execution Table 5.3-1: Real time VM execution Numbering Requirement description REQ.HYP.RT.001 The hypervisor domain shall be able to support memory bandwidth allocation Infrastructure Overview“. ETSI GS NFV-INF 003: “Network Functions Virtualisation (NFV); Compute Domain“. ETSI GS NFV-IN

46、F 005: “Network Functions Virtualisation (NFV); Infrastructure; Network Domain“. ETSI GS NFV-IFA 001: “Network Functions Virtualisation (NFV); Acceleration Technologies; Report on Acceleration Technologies Virtual Network Functions Architecture“. ETSI GS NFV-EVE 005: “Network Functions Virtualisatio

47、n (NFV); Ecosystem; Report on SDN Usage in NFV Architectural Framework“. ETSI ETSI GS NFV-EVE 001 V3.1.1 (2017-07)14 Annex C (informative): Change History Date Version Information about changes January 12, 2015 V0.0.1 ToC added February 20, 2015 V0.0.2 Overview and Scope added March 25, 2015 V0.0.3

48、Added NFV INF 004 approved components January 20, 2016 V0.0.4 Added approved contributions EVE(15)000253r1 and 4 EVE(15)000409r1 January 21, 2016 V0.0.5 Added history information, and disclosure on title page February 11, 2016 V0.0.6 Scope update NFVEVE(16)000022 March 22, 2016 V0.0.7 Editorial clea

49、n-up based on NFVEVE(16)000032 May 5, 2016 V0.0.8 Output of NFV#14, incorporating NFVEVE(16)00068, NFVEVE(16)00069R1, NFVEVE(16)00070R1 July 28, 2016 V0.0.9 Incorporating NFVEVE(16)000133 (editorial cleanup) agreed at EVE#40 September 9, 2016 V0.0.10 Incorporating NFVEVE(16)134R1 and 131R1 agreed at EVE#43 September 22, 2016 V0.0.11 Output of NFV#15, incorporating agreed NFVEVE(16)132R1 December 19, 2016 V0.1.0 Output of NFV#15, incorporating agreed NFVEVE(16)222 February 27, 2017 V0.2.0 Output of NFV#17, incorporating N