ETSI GR NFV-REL 007-2017 Network Function Virtualisation (NFV) Reliability Report on the resilience of NFV-MANO critical capabilities (V1 1 2).pdf

1、 ETSI GR NFV-REL 007 V1.1.2 (2017-10) Network Function Virtualisation (NFV); Reliability; Report on the resilience of NFV-MANO critical capabilities 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-REL 007 V1.1.2 (2017-10)2 Reference RGR/NFV-REL007ed112 Keywords management, MANO, NFV, orchestration, resilience ETSI 650 Ro

3、ute 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.ets

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

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

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

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

8、ETSI. 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 it

9、s 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 GR NFV-REL 007 V1.1.2 (2017-10)3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs t

10、erminology 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Abbreviations . 6g34 Introduction 7g35 NFV resiliency and its recommendations towards MANO 8g35.1 Resiliency and its application to NFV 8g35.2 Resiliency recommendations towards MANO . 9g35.2.1 MAN

11、O-related resiliency requirements classification 9g35.2.2 Non MANO-related resiliency requirements 13g36 Critical capabilities identification and ranking . 13g36.1 Critical capabilities analysis . 13g36.2 Mapping of capabilities vs. resiliency requirements 16g36.2.1 Introduction. 16g36.2.2 Mapped re

12、siliency requirements . 17g36.2.3 Unmapped resiliency requirements . 24g37 Resiliency mechanisms applied to MANOs critical capabilities . 26g37.1 Introduction 26g37.2 Diversity . 27g37.3 Redundancy 28g37.4 Availability monitoring 29g37.4.1 MANO components monitoring . 29g37.4.2 Virtual links monitor

13、ing 30g38 Recommendations 31g39 Security considerations. 33g3Annex A: MANO: from initial needs to current capabilities . 34g3A.1 Brief history of NFV 34g3A.2 MANO architectural framework 35g3A.2.1 MANO main functionality . 35g3A.2.2 MANO key components . 36g3Annex B: Resiliency requirements issued f

14、rom ETSI GS NFV-REL 001 . 39g3Annex 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 inves

15、tigation, 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 documen

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

17、 the 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 th

18、e 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 use

19、d in direct citation. ETSI ETSI GR NFV-REL 007 V1.1.2 (2017-10)5 1 Scope The present document investigates the building of a resilient NFV-MANO functional block from the reliability/availability perspective. In order to achieve this objective, the present document: 1) Identifies critical NFV-MANO ca

20、pabilities required to provide reliable services to the VNFs and the NSs. 2) Maps the resiliency requirements, e.g. established in ETSI GS NFV-REL 001 i.2, with existing NFV-MANO capabilities as listed in up to Release 2 GSs. 3) Studies specific needs and constraints for the identified capabilities.

21、 The work reports on possible mechanisms that enable high-availability within the different entities of NFV-MANO to render the identified capabilities dependable and trustworthy. 2 References 2.1 Normative references Normative references are not applicable in the present document. 2.2 Informative re

22、ferences 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.

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

24、a. i.1 ETSI GS NFV 003: “Network Functions Virtualisation (NFV); Terminology for Main Concepts in NFV“. i.2 ETSI GS NFV-REL 001: “Network Functions Virtualisation (NFV); Resiliency Requirements“. i.3 ETSI GS NFV-IFA 010 (V2.2.1): “Network Functions Virtualisation (NFV); Management and Orchestration;

25、 Functional requirements specification“. i.4 ETSI GS NFV-IFA 005: “Network Functions Virtualisation (NFV) Release 2; Management and Orchestration; Or-Vi reference point - Interface and Information Model Specification“. i.5 ETSI GS NFV-IFA 006: “Network Functions Virtualisation (NFV) Release 2; Manag

26、ement and Orchestration; Vi-Vnfm reference point - Interface and Information Model Specification“. i.6 ETSI GS NFV-IFA 008: “Network Functions Virtualisation (NFV) Release 2; Management and Orchestration; Ve-Vnfm reference point - Interface and Information Model Specification“. i.7 ETSI GS NFV-IFA 0

27、11: “Network Functions Virtualisation (NFV) Release 2; Management and Orchestration; VNF Packaging Specification“. i.8 ETSI GS NFV-SWA 001: “Network Functions Virtualisation (NFV); Virtual Network Functions Architecture“. i.9 ETSI GS NFV-REL 003: “Network Functions Virtualisation (NFV); Reliability;

28、 Report on Models and Features for End-to-End Reliability“. ETSI ETSI GR NFV-REL 007 V1.1.2 (2017-10)6 i.10 M. Chiosi et al.: “Network Functions Virtualisation - An Introduction, Benefits, Enablers, Challenges Management and Orchestration“. i.14 ETSI GS NFV-IFA 014: “Network Functions Virtualisation

29、 (NFV) Release 2; Management and Orchestration; Network Service Templates Specification“. i.15 ETSI GS NFV-SEC 013: “Network Functions Virtualisation (NFV) Release 3; Security; Security Management and Monitoring Specification“. i.16 ETSI GR NFV-IFA 021: “Network Functions Virtualisation (NFV); Manag

30、ement and Orchestration; Report on Management of NFV-MANO and Automated Deployment of EM and Other OSS Functions“. i.17 IETF RFC 4412 (2006): “Communications Resource Priority for the Session Initiation Protocol (SIP)“. i.18 IETF RFC 4594 (2006): “Configuration Guidelines for DiffServ Service Classe

31、s“. i.19 IETF RFC 5865 (2010): “A Differentiated Services Code Point (DSCP) for Capacity-Admitted Traffic“. i.20 IETF RFC 4090 (2005): “Fast Reroute Extensions to RSVP-TE for LSP Tunnels“. i.21 Recommendation ITU-T E.412 (2003): “Network management controls“. i.22 ETSI GS NFV-INF 003: “Network Funct

32、ions Virtualisation (NFV); Infrastructure; Compute Domain“. 3 Abbreviations For the purposes of the present document, the following abbreviations apply: (D)DoS (Distributed) Denial of Service API Application Programming Interface BFD Bidirectional Forwarding Detection BSS Business Support System COT

33、S Commercial Off The Shelf CPU Central Processor Unit DF Deployment FlavourEM Element Manager FCAPS Fault, Configuration, Accounting, Performance and Security HA High Availability ID Infrastructure DomainIFA (ETSI ISG NFV) Interface and Architecture (Working Group) IMS IP Multimedia Subsystem IO Inp

34、ut Output IT Information Technology KPI Key Performance Indicator L2 Layer 2L3 Layer 3LSA Link State Advertisement MANO Management and Orchestration NF Network Function ETSI ETSI GR NFV-REL 007 V1.1.2 (2017-10)7 NFP Network Forwarding Path NFV Network Functions Virtualisation NFVI NFV Infrastructure

35、 NFVO NFV OrchestratorNS Network Service NSD NS DescriptorNSR NS Record OS Operating System OSPF Open Shortest Path First OSS Operations Support System P-CSCF Proxy - Call Session Control Function PNF Physical Network Functions SAL Service Availability Level S-CSCF Serving - Call Session Control Fun

36、ction SDN Software Defined Networking SDO Standard Developing Organization SLA Service Level Agreement TD Tenant Domain TTM Time To Market VDU Virtualisation Deployment Unit VIM Virtualised Infrastructure Manager VLD Virtual Link Descriptor VLR Virtual Link Record VM Virtual MachineVN Virtual Networ

37、k VNF Virtualised Network Function VNFC VNF Component VNFD VNF DescriptorVNFFG VNF Forwarding Graph VNFFGD VNFFG Descriptor VNFFGR VNFFG Record VNFM VNF ManagerVNFR VNF Record WG Working Group4 Introduction Based on NFV resiliency requirements resulting from i.2, the present document aims to verify

38、that the current MANO capabilities as specified in i.3 cover all these requirements. It also proposes, with respect to network services reliability and availability, a classification of those resiliency requirements in two categories: requirements of normal importance and critical requirements. Thro

39、ugh a mapping of the MANO capabilities vs. the resiliency requirements, it identifies the missing capabilities for some resiliency requirements. It finally lists some mechanisms which could be exploited to enhance the identified critical capabilities resiliency. To this end, the items processed are

40、the followings: listing of the NFV resiliency characteristics; identification of resiliency requirements related to MANO; alignment of the MANO resiliency requirements within its functional blocks; resiliency requirements classification; mapping of MANO capabilities vs. resiliency requirements; iden

41、tification of and recommendations for missing MANO capabilities following the mapping; proposals for resiliency mechanisms related to the identified critical capabilities. ETSI ETSI GR NFV-REL 007 V1.1.2 (2017-10)8 5 NFV resiliency and its recommendations towards MANO 5.1 Resiliency and its applicat

42、ion to NFV Resiliency - as defined in i.1 - provides the ability “to limit disruption and return to normal or at a minimum acceptable service delivery level in the face of a fault, failure, or an event that disrupts the normal operation“. The definition above mentions fault as distinct from failure.

43、 i.2 has introduced the fault as leading to a failure chain. In a PNF environment, redundancy, the core mechanism of dependability, can be exploited in the following way. In a redundant system composed of two servers, one active and one standby, if the active fails (i.e. a fault occurs), the service

44、 is still rendered thanks to the standby one which takes over. It is noteworthy to mention that, in some cases (e.g. the standby server is less performant), the service may be degraded after the failover. Moreover, if the failed server is not replaced in a timely fashion and the new active one also

45、fails, the failure is observed at the service level. The resiliency engineering for a network service consists of the following phases: definition of the resiliency requirements, e.g. availability which can be done through different service availability levels and grades of the service i.2; design f

46、or resiliency - this important step mainly targets failure prevention, e.g. with the use of a redundant architecture; operations - once the network service is deployed, three other tasks help to maintain the service resiliency: - continuous monitoring, e.g. using health check, watchdog mechanisms; -

47、 detection of abnormal situations, e.g. threshold exceeded; - potential actions based on anomalous events - with the use of, e.g. fault correlation, root cause analysis: square4 launch corrective actions, e.g. prevent failures to happen; square4 prevent propagation of a breakdown, i.e. failure conta

48、inment - needless to say, as not all failures are equal, the study of failure severity, e.g. number of users impacted, is generally done in the design phase; square4 diagnose that an entity is deteriorating, i.e. failure prediction. During the operations, the failures are diverse: they can come from

49、 the infrastructure level, the VNF layer, or can concern the MANO software (see annex A for a reminder of MANO). As such, the MANO components NFVO, VNFM and VIM play critical roles in ensuring VNFs resiliency from their instantiation through their operation and recovery from failures. With respect to some life cycle management tasks (e.g. instantiation, scaling, migration), MANO is responsible for adhering to affinity and anti-affinity rules to ensure there is no single point of failure. Actually, the app