1、 ETSI GS NFV-INF 003 V1.1.1 (2014-12) Network Functions Virtualisation (NFV); Infrastructure; Compute 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 par
2、ticipated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS NFV-INF 003 V1.1.1 (2014-12) 2Reference DGS/NFV-INF003 Keywords NFV ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33
3、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/or in print. T
4、he 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 Portab
5、le 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 http:/portal.e
6、tsi.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 mechanical, incl
7、uding 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 Telecommunications Standards
8、Institute 2014. 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 logo are Trad
9、e Marks registered and owned by the GSM Association. ETSI ETSI GS NFV-INF 003 V1.1.1 (2014-12) 3Contents Intellectual Property Rights 6g3Foreword . 6g3Modal verbs terminology 6g31 Scope 7g32 References 7g32.1 Normative references . 7g32.2 Informative references 8g33 Definitions and abbreviations . 8
10、g33.1 Definitions 8g33.2 Abbreviations . 8g34 Domain Overview 10g34.1 Domain Scope 11g34.2 High Level NFV Framework 11g34.3 Compute Domain and Inter-Domain Interfaces . 11g34.3.1 Relevant Interfaces . 12g34.4 Relation to NFV Architecture Framework . 12g34.4.1 Elements of the Compute Domain 14g34.4.1
11、.1 Processor 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 (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, ha
12、s 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. Foreword This Group Specification (GS) has been produced by ETSI I
13、ndustry Specification Group (ISG) Network Functions Virtualisation (NFV). The present document gives an overview to the series of documents covering the NFV Infrastructure. Table 1: NFV infrastructure architecture documents Infrastructure Architecture Document Document # Overview GS NFV INF 001 Arch
14、itecture of the Infrastructure Domains Compute Domain GS NFV INF 003 Hypervisor Domain GS NFV INF 004 Infrastructure Network Domain GS NFV INF 005 Architectural Methodology Interfaces and Abstraction GS NFV INF 007 Service Quality Metrics GS NFV INF 010 Modal verbs terminology In the present documen
15、t “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 deli
16、verables except when used in direct citation. ETSI ETSI GS NFV-INF 003 V1.1.1 (2014-12) 71 Scope The present document presents an architectural description of the compute ( Use Cases“. 2 ETSI GS NFV 002 (V1.1.1): “Network Functions Virtualisation (NFV); Architectural Framework“. 3 ETSI GS NFV 003 (V
17、1.1.1): “Network Functions Virtualisation (NFV); Terminology for Main Concepts in NFV“. 4 ETSI GS NFV 004 (V1.1.1): “Network Functions Virtualisation (NFV); Virtualisation Requirements“. 5 ETSI GS NFV-INF 001 (V1.1.1): “Network Function Virtualisation (NFV); Infrastructure Overview“. 6 DMTF DSP 0217
18、: “SMASH Implementation Requirements“. 7 ETSI GS NFV-PER 001 (V1.1.1): “Network Function Virtualisation (NFV); NFV Performance Resiliency Requirements“. i.4 IEEE 1588TM: “IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems“. 3 Definitions and ab
19、breviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: composite-NFVI: NFVI hardware resources are composed of field replaceable units that are COTS elements field replaceable unit: unit of hardware resources designed for easy replacement dur
20、ing the operational life of a network element gateway node: See ETSI GS NFV-INF 001 5. network node: See ETSI GS NFV-INF 001 5. NFVI components: NFVI hardware resources that are not field replaceable, but are distinguishable as COTS components at manufacturing time NFVI-Plugin: NFVI hardware resourc
21、es are deployable as a COTS field replaceable unit for another network element NFVI-Pod: NFVI hardware resources are deployable as a single COTS entity with no field replaceable units portability: See ETSI GS NFV-INF 001 5. storage node: See ETSI GS NFV-INF 001 5. 3.2 Abbreviations For the purposes
22、of the present document, the following abbreviations apply: ACL Access Control List ACPI Advanced Configuration and Power Interface AES Advanced Encryption Standard API Application Programming Interface ARM Acorn RISC Machine ARP Address Resolution Protocol ETSI ETSI GS NFV-INF 003 V1.1.1 (2014-12)
23、9ASIC Application Specific Integrated Circuit AT NFVI; and NFV Management forwarding and exchange state information. Figure 3: High-level overview of the NFVI domains and interfaces ETSI ETSI GS NFV-INF 003 V1.1.1 (2014-12) 14Characteristics of NFVI reference points. Table 3: Characteristics of NFVI
24、 reference points INF ContextNFV Framework Reference PointINF Reference PointReference Point TypeCorrespondence with figure 2 InterfacesDescription and Comment Internal Vl-Ha Vl-Ha/CSr Execution Environment 12 The framework architecture 2 shows a general reference point between the infrastructure ha
25、rdware and the virtualisation layer. This reference point is the aspect of this framework reference point presented to hypervisors by the servers and storage of the compute domain. It is the execution environment of the server/storage. Vl-Ha/Nr Execution Environment The framework architecture 2 show
26、s a general reference point between the infrastructure hardware and the virtualisation layer. While the infrastructure network has hardware, it is often the case that networks are already layered (and therefore virtualised) and that the exact choice of network layering may vary without a direct impa
27、ct on NFV. The infrastructure architecture treats this aspect of the Vi-Ha reference point as internal to the infrastructure network domain. Ha/CSr-Ha/Nr Traffic Interface 14 This is the reference point between the infrastructure network domain and the servers/storage of the compute domain. External
28、 Nf-Vi Nf-Vi/C Management, and Orchestration Interface 11 This is the reference point between the management and orchestration agents in compute domain and the management and orchestration functions in the virtual infrastructure management (VIM). It is the part of the Nf-Vi interface relevant to the
29、 compute domain. 4.4.1 Elements of the Compute Domain The compute domain consists of consists of a server, network interface controller (NIC), accelerator, storage, rack, and any associated components within the rack including the physical aspects of a networking switch and all other physical compon
30、ents within NFVI. For example a blade server including a built-in Ethernet switch - see figure 4. Figure 4: Functional elements of the Compute domain - Chassis can also be a Rack ETSI ETSI GS NFV-INF 003 V1.1.1 (2014-12) 154.4.1.1 Processor and any impact on latency and delay variation will be withi
31、n the SLA specification for the function. 6.7 Service Assurance (E2E Requirements) SeA.1 The NFV framework shall provide mechanisms for time-stamping of hardware (e.g. network interface cards, NICs, and network interface devices, NIDs, that sit beneath virtualisation infrastructure) . The minimum su
32、pport from hardware shall be to: - copy packets or frames; - accurately time-stamp the copies, using a clock synchronized to a source of appropriate precision (e.g. IEEE 1588 i.4); and - forward the time-stamped copies to a configured destination. Once the precise time-stamps have been added in hard
33、ware, all other instrumentation and diagnosis functions can then proceed as virtualised functions without strict time constraints, e.g. filtering headers, removing payloads, local analysis, forwarding for remote analysis, logging, storage, etc. SeA.2 It should be possible to interrogate whether part
34、icular network interface hardware provides hardware time-stamping facilities.Key Concept proposal - A NFV service is composed of different types (1 or more) resource pools. Each pool contains a Class of Service that has specific types of resources that are composed to deliver a specific subset of pe
35、rformance. ETSI ETSI GS NFV-INF 003 V1.1.1 (2014-12) 27Figure 14: NFV types of services 6.8 Operations & Management (E2E Requirements) OaM.4 As part of VNF life cycle management, the orchestration functionality shall be able to interact with other systems (when they exist) managing the NFV infrastru
36、cture comprised of compute/storage machines, network software/hardware and configurations and/or software on these devices. OaM.5 The orchestration functionality shall be able to use standard information models that describes how to manage the VNF life cycle. Information models describe the deployme
37、nt and operational attributes of VNFs, for example: - Deployment attributes and environment of a VNF e.g. VM images, required computational and storage resources and network reachability. 6.8.1 Statistics Collection - Objectives in NFV Framework Statistics collection is important for supporting NFV
38、management and orchestration functions, especially in resource allocation when instantiating VNFs and global resource management functions. NFV-MANO performs resource allocation (compute, storage and network), as well as interconnection setup. A VNFD (virtual network function descriptor) describes t
39、he resource requirements of the VNF, and it is primarily used by the VNFM in the process of instantiating a VNF on the NFVI (NFV infrastructure), and for other life cycle management functions. The information provided in the VNFD is also used by the NFVO to manage and orchestrate network services, a
40、nd virtualized resources across multiple VIMs. VNFD also contains connectivity, interface and KPIs (key performance indicators) requirements that can be used by NFV-MANO to establish appropriate virtual links within the NFV Infrastructure between VNF instances, or between a VNF instance and the lega
41、cy network. NFV-MANO keeps track of attributes of resource pools so that it can allocate the resources which can meet the VNFD described requirements, ideally in an optimal manner. NFV global resource management performs resource discovery, resource optimization, access control, policy management, a
42、uditing, and fault management. ETSI ETSI GS NFV-INF 003 V1.1.1 (2014-12) 28Statistics collection enables the hierarchy of management and orchestration functions to monitor that the resource pools (compute, storage and network) are functioning properly and are conforming to their specifications and e
43、xpected performance and quality. In addition, statistics collection on VNFs provides additional insight into whether the VNFs perform as expected and whether relevant SLAs are adhered to. Some of the key performance indicators and key quality indicators which NFV-MANO uses are expected to be updated
44、 constantly by collected statistics. Examples of such indicators include average, maximum, and minimum values of throughput and latencies for certain VNFs or known functions, memory usage, power consumption of resources, number of active virtual machines running on a physical server, etc. 6.8.2 Prop
45、osed Hierarchy of resources and management software for statistics collection The NFV management and orchestration architecture includes a hierarchy of resources, virtualisation layer, VNFs, and corresponding managers and management systems. The managers are responsible for collecting the relevant s
46、tatistics. Table 5 shows the resources and VNFs as well as the corresponding managers and the statistics collected and maintained. Table 5: Proposed hierarchy of statistics collection Resource/VNF Manager(s) MANO manager Compute hardware Hypervisor, virtualisation manager (e.g. OpenStack) Virtualize
47、d infrastructure manager(s) Storage hardware Hypervisor, virtualisation manager (e.g. OpenStack) Virtualized infrastructure manager(s) Network hardware Hypervisor and vSwitch (e.g. OpenStack) Virtualized infrastructure manager(s)VNF instance EMS instance VNF manager(s) Service OSS/BSS Orchestrator6.
48、9 Energy Efficiency (E2E Requirements) EE.1 The NFV framework shall support the capability to place only VNF components that can be moved or placed in a sleep state on a particular resource (compute, storage) so that resource can be placed into a power conserving state. EE.2 The NFV framework shall
49、be able to provide mechanisms to enable an authorized entity to control and optimize energy consumption on demand, by e.g. scheduling and placing VNF instances on specific resources, including hardware and/or hypervisors, placing unused resources in energy saving mode, and managing power states as needed. EE.3 The NFV framework shall provide an information model that defines the timeframe required for a compute resource, hypervisor and/or VNFC (e.g. VM) to return to a normal operating mode after leaving a sp
