ETSI GS NFV-INF 004-2015 Network Functions Virtualisation (NFV) Infrastructure Hypervisor Domain (V1 1 1)《网络虚拟化技术 (NFV) 虚拟机监控程序域 (V1 1 1)》.pdf

1、 ETSI GS NFV-INF 004 V1.1.1 (2015-01) Network Functions Virtualisation (NFV); Infrastructure; Hypervisor Domain Disclaimer This document has been produced and approved by the Network Functions Virtualisation (NFV) ETSI Industry Specification Group (ISG) and represents the views of those members who

2、participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS NFV-INF 004 V1.1.1 (2015-01) 2Reference DGS/NFV-INF004 Keywords interface, NFV ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 4

3、2 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 The present document may be made available in electronic versions and/

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

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

6、http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or me

7、chanical, 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. European Telecommunicati

8、ons Standards Institute 2015. 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 the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM

9、 logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS NFV-INF 004 V1.1.1 (2015-01) 3Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abb

10、reviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Domain Overview 9g35 External Interfaces of the Domain 14g35.1 Overview 15g35.2 Hypervisor to VIM (Nf-Vi-H) Interface 16g35.2.1 Nature of the Interface 16g35.2.1.1 Example of MIB information 16g35.2.2 Specifications in Current Widespread Is

11、sue . 19g35.2.2.1 Metrics for VNF performance characteristics . 19g35.2.3 Achieving Interoperability 20g35.2.4 Recommendations . 20g36 Architecture and Functional Blocks of the Hypervisor Domain 20g37 Requirements for the Hypervisor Domain . 22g37.1 General . 22g37.2 Portability . 22g37.3 Elasticity

12、/Scaling 24g37.4 Resiliency . 25g37.5 Security 26g37.6 Service Continuity 27g37.7 Operational and Management requirements . 28g37.8 Energy Efficiency requirements . 29g37.9 Guest RunTime Environment . 30g37.10 Coexistence with existing networks - Migration 31g38 Service Models . 31g38.1 General . 31

13、g38.2 Deployment models 31g38.3 Service models . 32g3Annex A (informative): Informative Reference: VIM Categories . 34g3A.1 Logging for SLA, debugging . 35g3A.2 Host Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat

14、. Latest updates are available on the ETSI Web server (http:/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 ET

15、SI Web server) which are, or may be, or may become, essential to the present document. Foreword This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Network Functions Virtualisation (NFV). Infrastructure Architecture Documents Document # Overview GS NFV INF 001

16、Architecture of Compute Domain GS NFV INF 003 Architecture of Hypervisor Domain GS NFV INF 004 Architecture of Infrastructure Network Domain GS NFV INF 005 Scalability GS NFV INF 006 Interfaces and Abstraction GS NFV INF 007 Test Access GS NFV INF 009 Modal verbs terminology In the present document

17、“shall“, “shall not“, “should“, “should not“, “may“, “may not“, “need“, “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 delive

18、rables except when used in direct citation. ETSI ETSI GS NFV-INF 004 V1.1.1 (2015-01) 61 Scope The present document presents the architecture of the Hypervisor Domain of the NFV Infrastructure which supports deployment and execution of virtual appliances. The present document will primarily focus on

19、 the use of hypervisor for virtualisation, due to time and resource constraints, However, the hypervisor requirements are similar if not the same for implementing linux containers or other methods for virtualisation. NOTE: From WikiArch: “Linux Containers (LXC) are an operating system-level virtuali

20、sation method for running multiple isolated server installs (containers) on a single control host. LXC does not provide a virtual machine, but rather provides a virtual environment that has its own process and network space. It is similar to a chroot, but offers much more isolation“. There needs to

21、be further research w.r.t to Linux Containers, including developing the ecosystem. As well as presenting a general overview description of the NFV Infrastructure, the present document sets the NFV infrastructure and all the documents which describe it in the context of all the documents of the NFV.

22、It also describes how the documents which describe the NFV infrastructure relate to each other. The present document does not provide any detailed specification but makes reference to specifications developed by other bodies and to potential specifications, which, in the opinion of the NFV ISG could

23、 be usefully developed by an appropriate Standards Developing Organisation (SDO). 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 applies.

24、 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 http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this cl

25、ause 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-INF 001 (V1.1.1): “Network Functions Virtualisation (NFV); Infrastructure Overview“. 2.2 Informative

26、 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) appli

27、es. 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

28、area. i.1 ETSI GS NFV 004: “Network Functions Virtualisation (NFV); Virtualisation Requirements“. i.2 IETF RFC 4133: “Entity MIB (Version 3)“. i.3 IEEE 802.1DTM: “IEEE Standard for Local and Metropolitan Area Networks - Media access control (MAC) Bridges“. ETSI ETSI GS NFV-INF 004 V1.1.1 (2015-01) 7

29、i.4 IEEE 802.1QTMMIB: “IEEE Standard for Local and Metropolitan Area Networks, Management Information Base“. i.5 IETF draft-ietf-opsawg-vmm-mib-00: “Management Information Base for Virtual Machines Controlled by a Hypervisor“. NOTE: Available at http:/tools.ietf.org/html/draft-ietf-opsawg-vmm-mib-00

30、. i.6 IEEE 1588TM: “Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems“. i.7 IEEE 802.11TM: “Wireless LANS IEEE Standard for Information technology - Telecommunications and information exchange between systems Local and metropolitan area networks -

31、Specific requirements Part 11: Wireless LAN“. i.8 IEEE 802.3adTM: “Link Aggregation“. i.9 IEEE 802.3TMMIB: “Link Aggregation, Management Information Base“. i.10 Hotlink: http:/ i.11 Systems Management Architecture for Server Hardware (SMASH). NOTE: Available at http:/www.dmtf.org/standards/smash. i.

32、12 NFVINF(13)VM_019_Data_plane_performance. i.13 http:/ i.14 http:/ i.15 http:/ i.16 ETSI GS NFV-INF 010: “Network Functions Virtualisation (NFV); Service Quality Metrics“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions a

33、pply: application VMs: VM not utilizing an OS hypervisor: virtualisation environment running on a host NOTE: The virtualisation environment includes the tools, BIOS, firmware, Operating Systems (OS) and drivers. portability: See ETSI GS NFV-INF 001 1. standard: is de-jure, de-facto or open standard

34、that fulfils the requirement NOTE: This assumption should be applied to all requirements through the entire document. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: API Application Programming Interface BIOS Basic Input Output System ETSI ETSI GS NFV-I

35、NF 004 V1.1.1 (2015-01) 8BSD Berkeley Software Distribution CIM Centralized Interference Mitigation CLI Comand Line Interface CMS Call Management System CPU Compute Processing Unit DMA Direct Memory AccessDpdk Data plane development kit EE Electrical Engineering FFS For Further Specification GUI Gra

36、phical User Interface HA High Availability IETF Internet Engineering Task Force INF Infrastructure IO Input Output IP Internet ProtocolIPMI Intelligent Platform Interface JVM Java Virtual Machine KVM Kernel Virtual Machine LAN Local Area NetworksLLC Lower Level Cache LLDP Link Layer Discovery Protoc

37、ol LXC Linux Containers MAC Media Access Controller MANO Management and Orchastration MIB Management Information Base NF Network Function NFVi Network Function Virtualisation Infrastructure NFVINF Network Function Virtualisation Infrastructure NIC Network Interface Card NOC Network Operator Council

38、NUMA Non Uniform Memory Access OAM Operations and Maintenance OS Operating System OSS Operations Systems and Software OVF Open Virtual Framework PAE Physical Address ExtensionPCI Peripheral Component Interconnect RAID Redundant Array of Independent Disks RAM Random Access Memory RAS Row Address Stro

39、be RELAV Reliability and Resiliency Work Group RFC Request For Comment SCSI Small Computer System Interface SDO Standards Development Organizations SEC Security Working Group SLA Service Level Agreement SNMP Signalling Network Management Protocol SR-IOV Single Root I/O Virtualisation SWA Software Ar

40、chitecture Work group TCP Transport Control Protocol TLB Translation Lookaside Buffer UDP User Datagram Protocol UUID Universally Unique Identifier VIM Virtualisation Infrastructure Manager VM Virtual Machine VN Virtual networkVNF Virtual Network Function VNFC Virtual Network Function Component VNFI

41、 Virtual Network Function Interface VSCSI Virtual Small Computer System Interface vSwitch virtual Switch VT VirtualisationETSI ETSI GS NFV-INF 004 V1.1.1 (2015-01) 9WG Working Group XAPI eXtended Application Programming Interface 4 Domain Overview Popek and Goldberg paper Formal Requirements for Thi

42、rd Generation Architectures: set the definition of hypervisors in 1974. Equivalence: the hypervisor provides an environment for programs which is essentially identical to the original machine. Resource control: the hypervisor is in complete control of system resources. Efficiency: programs run on th

43、is (virtualised) environment show at worst only minor decreases in speed. Equivalence The environment provided by a hypervisor is functionally equivalent to the original machine environment. This implies that the same operating systems, tools and application software can be used in the virtual envir

44、onment. This does not preclude para-virtualisation and other optimization techniques which may require operating systems, tools and application changes. Resource Control The hypervisor domain mediates the resources of the computer domain to the virtual machines of the software appliances. Hypervisor

45、s as developed for public and enterprise cloud requirements place great value on the abstraction they provide from the actual hardware such that they can achieve very high levels of portability of virtual machines. In essence, the hypervisor can emulate every piece of the hardware platform even in s

46、ome cases, completely emulating a CPU instruction set such that the VM believes it is running on a completely different CPU architecture from the actual CPU on which it is running. Such emulation, however, has a significant performance cost. The number of actual CPU cycles needed to emulate virtual

47、CPU cycle can be large. Efficiency Even when not emulating a complete hardware architecture, there can still be aspects of emulation which cause a significant performance hit. Typically, computer architectures provide means to offload these aspects to hardware, as so called virtualisation extensions

48、, the set of operations that are offloaded and how they are offloaded varies between different hardware architectures and hypervisors as innovation improves virtualisation performance. EXAMPLE: Intel VT and ARM virtualisation extensions minimise the performance impact of virtualisation by offloading to hardware certain frequently performed operations. There can be many virtual machines running on the same host machine. The VMs on the same host may want to communicate between each