1、 ETSI GR NFV-IFA 023 V3.1.1 (2017-07) Network Functions Virtualisation (NFV); Management and Orchestration; Report on Policy Management in MANO; Release 3 Disclaimer The present document has been produced and approved by the Network Functions Virtualisation (NFV) ETSI Industry Specification Group (I
2、SG) 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 REPORT ETSI ETSI GR NFV-IFA 023 V3.1.1 (2017-07) 2 Reference DGR/NFV-IFA023 Keywords MANO, NFV, policy management ETSI 650 Route des Lucioles F
3、-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.org/standards-se
4、arch 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 contents betwe
5、en 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 status. Informat
6、ion 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 Copyright Not
7、ification 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. The copyrigh
8、t and the foregoing restriction extend to reproduction in all media. ETSI 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 the benefit of its Members and of
9、 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-IFA 023 V3.1.1 (2017-07) 3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31
10、 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Background and Overview . 7g35 Use cases 8g35.1 General . 8g35.2 Policy creation and transfer 8g35.2.1 Use case description 8g35.2.2
11、Actors and conditions . 8g35.2.3 Base flow 9g35.3 Policy deletion 9g35.3.1 Use case description 9g35.3.2 Actors and conditions . 9g35.3.3 Base flow 10g35.4 Policy update 10g35.4.1 Use case description 10g35.4.2 Actors and conditions . 10g35.4.3 Base flow 10g35.5 Policy query 11g35.5.1 Use case descr
12、iption 11g35.5.2 Actors and conditions . 11g35.5.3 Base flow 11g35.6 Policy activation . 11g35.6.1 Use case description 11g35.6.2 Actors and conditions . 12g35.6.3 Base flow 12g35.7 Policy deactivation . 12g35.7.1 Use case description 12g35.7.2 Actors and conditions . 12g35.7.3 Base flow 13g35.8 NFV
13、 MANO specific policy management use cases 13g35.8.1 Overview 13g35.8.2 Granting policy in VNF lifecycle management operation 13g35.8.2.1 Use case description 13g35.8.3 Optimization of NFVI-PoPs resource utilization 14g35.8.3.1 Use case description 14g35.8.3.2 Actors and roles 16g35.8.3.3 Base flow
14、16g35.8.4 Transferring NS healing policy to the NFVO . 17g35.8.4.1 Use case description 17g35.8.5 Auto-scaling policy pre-defined in the VNFD 17g35.8.5.1 Use case description 17g35.8.6 Associating VNF LCM policies with VNF instances . 18g35.8.6.1 Use case description 18g35.8.7 Disassociating VNF LCM
15、 policies from VNF instances 18g35.8.7.1 Use case description 18g35.8.8 Policy conflict detection in the PF 19g3ETSI ETSI GR NFV-IFA 023 V3.1.1 (2017-07) 4 5.8.8.1 Use case description 19g35.8.9 Policy conflict detection in the PAP . 19g35.8.9.1 Use case description 19g35.8.10 Enforcement among mult
16、i-layer polices . 20g35.8.10.1 Use case description 20g35.8.11 Transferring VNF healing policy from the EM 20g35.8.11.1 Use case description 20g35.8.12 Transferring virtualized resource allocation policy for the VIM 21g35.8.12.1 Use case description 21g35.8.13 Distribution of energy efficiency polic
17、ies . 21g35.8.13.1 Use case description 21g35.9 Recommendations 22g35.9.1 Overview 22g35.9.2 General recommendations 22g35.9.3 Recommendations for policy lifecycle management 23g36 Key issue analysis 25g36.1 Key Issue 1: Mapping of PAP and PF to MANO functional blocks 25g36.1.1 Overview 25g36.1.2 Ma
18、pping the PF to the NFVO and the PAP to the OSS/BSS 25g36.1.3 Mapping the PF to the VNFM and the PAP to the NFVO and/or the EM 25g36.1.4 Mapping the PF to the VIM and the PAP to the NFVO or VNFM . 26g36.1.5 Summary of PAP mapping . 26g36.2 Key Issue 2: Categorizing policies in MANO architecture 26g3
19、6.2.1 Overview 26g36.2.2 MANO policy categories 26g36.3 Key Issue 3: Principles on information modelling of MANO policies. 27g36.3.1 Overview 27g36.3.2 Lessons learnt from other work 27g36.3.3 Principles on MANO policy information modelling 28g37 Architectural options 29g37.1 Introduction 29g37.2 Ar
20、chitectural option #1: Managing policies by using existing MANO reference points . 29g37.2.1 Overview 29g37.2.2 Managing MANO policies using Os-Ma-nfvo . 29g37.2.3 Managing MANO policies using Or-Vnfm 29g37.2.4 Managing MANO policies using Or-Vi 30g37.2.5 Managing MANO policies using Ve-Vnfm 30g37.2
21、.6 Managing MANO policies using Vi-Vnfm 31g37.2.7 Impact on MANO Architecture 31g37.2.7.1 Introduction . 31g37.2.7.2 Policy conflict avoidance 31g37.2.7.3 Policy conflict detection and resolution 31g37.2.7.4 Summary . 32g37.3 Analysis 32g38 Recommendations 33g3Annex A: Authors Essential, or potentia
22、lly 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 investigation, including IPR searches, has been carried out by ETSI. No gu
23、arantee 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 may include trademarks and/or tradenames which are asserted and/or
24、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 the present document does not constitute an endorsement by ETSI of p
25、roducts, 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 present document “should“, “should not“, “may“, “need not“, “will“,
26、 “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 in direct citation. ETSI ETSI GR NFV-IFA 023 V3.1.1 (2017-07) 6 1 S
27、cope The present document provides a study on managing policies in the NFV MANO architecture. High-level use cases, key functionality analysis and potential architectural options for fulfilling this objective are proposed in the present document. As an output of the study, recommendations for the no
28、rmative work are provided. 2 References 2.1 Normative references 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 refere
29、nces, only the cited version applies. For non-specific references, 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
30、 referenced documents 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 003: “Network Functions Virtualisation (NFV); Terminology for main concepts in NFV“. i.2 ETSI GS NFV-MAN 001: “Network Functions Virt
31、ualisation (NFV); Management and Orchestration“. i.3 ETSI GS NFV-IFA 007: “Network Functions Virtualisation (NFV); Management and Orchestration; Or-Vnfm reference point - Interface and Information Model Specification“. i.4 ETSI GS NFV-IFA 011: “Network Functions Virtualisation (NFV); Management and
32、Orchestration; VNF Packaging Specification“. i.5 TM Forum TR235: “Report on ZOOM policy model and architecture snapshot“. i.6 IETF draft-ietf-supa-policy-based-management-framework-00: “SUPA policy-based management framework“. i.7 OpenStackReleases. NOTE: Available at https:/releases.openstack.org/t
33、eams/congress.html. i.8 ETSI GS NFV-IFA 014: “Network Functions Virtualisation (NFV) Release 2; Management and Orchestration; Network Service Templates Specification“. i.9 IETF draft-ietf-supa-generic-policy-info-model-02: “Generic Policy Information Model for Simplified Use of Policy Abstractions (
34、SUPA)“. i.10 IETF draft-ietf-supa-generic-policy-data-model-03: “Generic Policy Data Model for Simplified Use of Policy Abstractions (SUPA)“. i.11 IETF RFC 3060: “Policy Core Information Model - Version 1 Specification“. i.12 IETF RFC 3460: “Policy Core Information Model (PCIM) Extensions“. ETSI ETS
35、I GR NFV-IFA 023 V3.1.1 (2017-07) 7 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI GS NFV 003 i.1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI GS NFV 003 i.1 and t
36、he following apply. NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in ETSI GS NFV 003 i.1. PAP Policy Administration Point PF Policy Function 4 Background and Overview Policy is one of the key enablers for constructing fle
37、xible management and orchestration functions in the NFV MANO architecture. Assisted with policies, MANO functions may be provided with more automatic characteristics which fit in with the dynamic requirements of resource management and network service orchestration in the virtualized network environ
38、ment. Although the importance of policy management in MANO has been identified by ETSI GS NFV-MAN 001 i.2, there is not a systematic study on how to integrate policy management in NFV MANO architecture during the timeframe of releases 1 and 2. Following a model consisting of a Policy Administration
39、Point (PAP), which defines policies, and a Policy Function (PF), which evaluates policies and makes the policy decisions, the following aspects are to be investigated in the present document: The model of PAP and PF can be applied to the management of MANO policy. Particularly, a MANO entity such as
40、 the NFVO can act as both the PAP and the PF ( i.e. acting as the former on one policy and as the latter on another policy). There can be multiple sources that create policy information enforced by a PF, e.g. the policy information on scaling for a certain VNF instance can be created by either the O
41、SS/BSS, the NFVO or be pre-defined in the VNF descriptor. Potential conflicts of policy enforcement can occur during the enforcement of MANO policies distributed in different layers. From management point of view, MANO policy can apply to lifecycle management and resource orchestration. Therefore, t
42、he study in the present document is targeted to deliver recommendations on a functional framework of policy management with the analysis on the above aspects. ETSI ETSI GR NFV-IFA 023 V3.1.1 (2017-07) 8 5 Use cases 5.1 General The following use cases describe the processes involving MANO policy mana
43、gement. In clauses 5.2 to 5.7, rather than the method of designating assigned management functions to one or more MANO functional block(s), the abstracted roles are introduced (see table 5.1-1) in the use case description for improving the flexibility of functionality mapping to MANO architecture. T
44、hese roles capture the generic processes as well as the action required to be performed by different actors. How does each role be mapped to the actual MANO functional block(s) is addressed under clause 6 of key issue analysis. Table 5.1-1: Use case roles and description Role Description Policy Admi
45、nistration Point (PAP) The PAP is responsible for defining MANO policies. It is not in the scope of this document to define a jurisdiction (one administrative domain or multiple administrative domains) for a PAP. Policy Function (PF) The PF is responsible for making policy decisions, i.e. to evaluat
46、e whether the policy conditions are met and to define what is to be done when they are met. These responsibilities are referred to as “policy enforcement“ in the presentdocument. NOTE: Both the PAP and the PF can be mapped to MANO functional blocks (e.g. NFVO, VNFM, VIM) in different ways. Clause 5.
47、8 provides NFV MANO specific use cases which are applied to specific VNF/NS lifecycle management or resource management scenarios. Finally, clause 5.9 proposes the recommendation of potential requirements which are derived from the use cases. 5.2 Policy creation and transfer 5.2.1 Use case descripti
48、on This use case describes the process of creating a MANO policy, which is initiated by the PAP, along with the consequent process of transferring the created MANO policy to the PF for storage. It is assumed that policy creation occurs only inside the PAP and is not exposed to the PF. 5.2.2 Actors a
49、nd conditions Table 5.2.2-1: Actors # Actor 1 PAP 2 PF Table 5.2.2-2: Pre-conditions # Pre-conditions Comment 1 The PAP knows about the MANO functional entities and the necessary information for creating the MANO policy. ETSI ETSI GR NFV-IFA 023 V3.1.1 (2017-07) 9 Table 5.2.2-3: Post-conditions # Post-conditions Comment 1 The PAP is aware of the acceptance of created MANO policy. 5.2.3 Base flow Table 5.2.3-1: Base flow # Actor Action/Description 1 PAP The PAP creates a certain MANO policy (e.g. NS LCM policy, VNF LCM policy, resource
