ETSI GR NFV-EVE 022 V5.1.1 (2022-12)

Network Functions Virtualisation (NFV) Release 5; Architectural Framework; Report on VNF configuration

DGR/NFV-EVE022

General Information

• Status: Not Published
• Technical Committee: NFV EVE - Evolution and Ecosystem
• Current Stage: 12 - Completion
• Due Date: 09-Jan-2023
• Completion Date: 15-Dec-2022

Standards Content (Sample)

GROUP REPORT
Network Functions Virtualisation (NFV) Release 5;
Architectural Framework;
Report on VNF configuration
Disclaimer
The present 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 participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

2 ETSI GR NFV-EVE 022 V5.1.1 (2022-12)

Reference
DGR/NFV-EVE022
Keywords
configuration, NFV
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
http://www.etsi.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 in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
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
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2022.
All rights reserved.
ETSI
3 ETSI GR NFV-EVE 022 V5.1.1 (2022-12)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 8
3 Definition of terms, symbols and abbreviations . 9
3.1 Terms . 9
3.2 Symbols . 10
3.3 Abbreviations . 10
4 VNF configuration . 10
4.1 General . 10
4.2 VNF configuration items . 10
4.3 VNF configuration methods . 11
4.3.1 Overview . 11
4.3.2 Method #A . 11
4.3.2.1 General description . 11
4.3.2.2 Detailed description . 12
4.3.2.2.1 Push mode . 12
4.3.2.2.2 Pull mode . 14
4.3.2.2.3 Hybrid modes . 14
4.3.3 Method #B . 14
4.3.3.1 General description . 14
4.3.3.2 Detailed description . 15
4.3.3.2.1 General . 15
4.3.3.2.2 Push mode . 16
4.3.3.2.3 Pull mode . 17
4.3.4 Method #C . 17
4.3.4.1 General description . 17
4.3.4.2 Detailed description . 18
4.3.4.2.1 General . 18
4.3.4.2.2 VM-based VNFs . 19
4.3.4.2.3 Containerized VNFs . 20
5 VNF configuration use cases . 21
5.1 General . 21
5.1.1 Introduction. 21
5.1.2 Actors . 21
5.2 Day-0 configuration use cases . 21
5.2.1 UC#Day-0-1: Configuration of a VNF-specific parameter . 21
5.2.1.1 Description . 21
5.2.1.2 Trigger . 21
5.2.1.3 Pre-conditions . 22
5.2.1.4 Post-conditions . 22
5.2.1.5 Operational Flows . 22
5.2.2 UC#Day-0-2: Configuration of the VNFM address . 22
5.2.2.1 Description . 22
5.2.2.2 Trigger . 22
5.2.2.3 Pre-conditions . 22
5.2.2.4 Post-conditions . 22
5.2.2.5 Operational Flows . 23
5.2.3 UC#Day-0-3: Configuration of the EM address . 23
5.2.3.1 Description . 23
5.2.3.2 Trigger . 23
ETSI
4 ETSI GR NFV-EVE 022 V5.1.1 (2022-12)
5.2.3.3 Pre-conditions . 23
5.2.3.4 Post-conditions . 23
5.2.3.5 Operational Flows . 24
5.3 Day-1 configuration use cases . 24
5.3.1 UC#Day-1-1: Modification of a VNF-specific configuration value . 24
5.3.1.1 Description . 24
5.3.1.2 Trigger . 24
5.3.1.3 Pre-conditions . 24
5.3.1.4 Post-conditions . 24
5.3.1.5 Operational Flows . 25
5.3.2 UC#Day-1-2: Configuration of an internal load balancer . 25
5.3.2.1 Description . 25
5.3.2.2 Trigger . 25
5.3.2.3 Pre-conditions . 25
5.3.2.4 Post-conditions . 25
5.3.2.5 Operational Flows . 26
5.3.3 UC#Day-1-3: Configuration of proxy/firewall VNF . 26
5.3.3.1 Description . 26
5.3.3.2 Trigger . 26
5.3.3.3 Pre-conditions . 26
5.3.3.4 Post-conditions . 26
5.3.3.5 Operational Flows . 27
5.3.4 UC#Day-1-4: Distribution and storage of VNF configuration data . 27
5.3.4.1 Description . 27
5.3.4.2 Trigger . 27
5.3.4.3 Pre-conditions . 27
5.3.4.4 Post-conditions . 27
5.3.4.5 Operational Flows . 28
6 Analysis and Key Issues . 28
6.1 General . 28
6.2 Common key issues . 28
6.3 Use case analysis . 29
6.3.1 Day 0 use cases . 29
6.3.1.1 UC#Day-0-1: Configuration of a VNF-specific parameter . 29
6.3.1.1.1 Implementation options . 29
6.3.1.1.2 Key Issues . 30
6.3.1.2 UC#Day-0-2: Configuration of the VNFM address . 30
6.3.1.2.1 Implementation options . 30
6.3.1.2.2 Key Issues . 30
6.3.1.3 UC#Day-0-3: Configuration of the EM address . 30
6.3.1.3.1 Implementation options . 30
6.3.1.3.2 Key Issues . 31
6.3.2 Day 1 use cases . 31
6.3.2.1 UC#Day-1-1: Modification of a VNF-specific configuration value . 31
6.3.2.1.1 Implementation options . 31
6.3.2.1.2 Key Issues . 31
6.3.2.2 UC# Day-1-2: Configuration of an internal load balancer . 31
6.3.2.2.1 Implementation options . 31
6.3.2.2.2 Key Issues . 31
6.3.2.3 UC#Day-1-3: Configuration of proxy/firewall VNF . 32
6.3.2.3.1 Implementation options . 32
6.3.2.3.2 Key Issues . 32
6.3.2.4 UC#Day-1-4: Distribution and storage of VNF configuration data . 32
6.3.2.4.1 Implementation options . 32
6.3.2.4.2 Key Issues . 33
7 Potential Solutions . 33
7.1 Introduction . 33
7.2 Solutions for general key issues . 33
7.2.1 Configuration method #A . 33
7.2.1.1 General key issue#1 (GKI-A-1) . 33
ETSI
5 ETSI GR NFV-EVE 022 V5.1.1 (2022-12)
7.2.1.1.1 Solutions . 33
7.2.1.1.2 Evaluation of solutions . 34
7.2.1.2 General key issue#2 (GKI-A-2) . 34
7.2.1.2.1 Solutions . 34
7.2.1.2.2 Evaluation of solutions . 35
7.2.1.3 General key issue#3 (GKI-A-3) . 36
7.2.1.3.1 Solutions . 36
7.2.1.3.2 Evaluation of solutions . 36
7.2.1.4 General key issue#4 (GKI-A-4) . 36
7.2.1.4.1 Solutions . 36
7.2.1.4.2 Evaluation of solutions . 36
7.2.1.5 General key issue#5 (GKI-A-5) . 36
7.2.1.5.1 Solutions . 36
7.2.1.5.2 Evaluation of solutions . 36
7.2.1.6 General key issue#6 (GKI-A-6) . 37
7.2.1.6.1 Solutions . 37
7.2.1.6.2 Evaluation of solutions . 37
7.2.2 Configuration method #B . 38
7.2.2.1 General key issue#1 (GKI-B-1) . 38
7.2.2.1.1 Solutions . 38
7.2.2.1.2 Evaluation of solutions . 38
7.2.3 Configuration method #C . 39
7.2.3.1 General key issue#1 (GKI-C-1) . 39
7.2.3.1.1 Solutions . 39
7.2.3.1.2 Evaluation of solutions . 39
7.3 Solutions for specific key issues . 40
7.3.1 Configuration method #A . 40
7.3.1.1 Specific key issue#1 (SKI-A-1) . 40
7.3.1.1.1 Solutions . 40
7.3.1.1.2 Evaluation of solutions . 40
7.3.1.2 Specific key issue#1 (SKI-A-2) . 40
7.3.1.2.1 Solutions . 40
7.3.1.2.2 Evaluation of solutions . 41
7.3.2 Configuration method #B . 41
7.3.2.1 Specific key issue#1 (SKI-B-1). 41
7.3.2.1.1 Solutions . 41
7.3.2.1.2 Evaluation of solutions . 41
7.3.2.2 Specific key issue#1 (SKI-B-2). 41
7.3.2.2.1 Solutions . 41
7.3.2.2.2 Evaluation of solutions . 42
7.3.3 Configuration methods related to distribution and storage of VNF configuration data . 42
7.3.3.1 Specific key issue: setting up the "centralized storage for configuration" in the NFV framework . 42
7.3.3.1.1 Overview . 42
7.3.3.1.2 Solutions . 43
7.3.3.1.3 Evaluation of solutions . 45
7.3.3.2 Specific key issue: protocols for centralized storage for configuration. 46
7.3.3.2.1 Overview . 46
7.3.3.2.2 Solutions . 47
7.3.3.2.3 Evaluation of solutions . 48
8 Recommendations for future work . 48
8.1 General recommendations . 48
8.2 Recommendations on functional behaviour . 49
8.3 Recommendations on descriptors . 49
8.4 Recommendations on interfaces . 50
8.5 Security related recommendations . 50
8.6 Recommendations related to cross-organizations collaboration . 50
8.7 Other recommendations . 50
Annex A: VNF Configuration Examples . . 51 ®
A.1 VNF configuration with Ansible . 51
ETSI
6 ETSI GR NFV-EVE 022 V5.1.1 (2022-12) ®
A.2 VNF configuration via Kubernetes ConfigMaps. 53
™
A.3 VNF configuration via Helm chart parameterization . 57
Annex B: Change History . 60
History . 61

ETSI
7 ETSI GR NFV-EVE 022 V5.1.1 (2022-12)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); 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 Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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 document 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 the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
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", "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
8 ETSI GR NFV-EVE 022 V5.1.1 (2022-12)
1 Scope
The present document provides guidelines on the use of the VNF configuration options enabled by the NFV
architectural framework. It identifies gaps in NFV specifications preventing interoperability between VNFs and
independently-developed VNF configuration management functions, and/or preventing easy integration of VNF
configuration management in VNF lifecycle management processes. The present document provides recommendations
on normative work to be carried out to fill these gaps.
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 references, 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 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 GR NFV 003: "Network Functions Virtualisation (NFV); Terminology for main concepts in
NFV".
[i.2] Recommendation ITU-T M.3400 (02/2000):"Telecommunications management network: TMN
management functions".
[i.3] IETF RFC 6241 (06/2011): "Network Configuration Protocol (NETCONF)".
NOTE: Available at https://www.rfc-editor.org/rfc/rfc6241.
[i.4] gNMI - gRPC Network Management Interface.
NOTE: Available at: https://github.com/openconfig/gnmi.
[i.5] ETSI GS NFV-SOL 001: "Network Functions Virtualisation (NFV) Release 4; Protocols and Data
Models; NFV descriptors based on TOSCA specification".
[i.6] ETSI GS NFV-SOL 002: "Network Functions Virtualisation (NFV) Release 4; Protocols and Data
Models; RESTful protocols specification for the Ve-Vnfm Reference Point".
[i.7] ETSI GS NFV-SOL 003: "Network Functions Virtualisation (NFV) Release 4; Protocols and Data
Models; RESTful protocols specification for the Or-Vnfm Reference Point".
[i.8] ETSI GS NFV-SOL 004: "Network Functions Virtualisation (NFV) Release 4; Protocols and Data
Models; VNF Package and PNFD Archive specification".
[i.9] ETSI GS NFV-SOL 005: "Network Functions Virtualisation (NFV) Release 4; Protocols and Data
Models; RESTful protocols specification for the Os-Ma-nfvo Reference Point".
[i.10] ETSI GS NFV-SOL 006: "Network Functions Virtualisation (NFV) Release 4; Protocols and Data
Models; NFV descriptors based on YANG specification".
[i.11] ETSI GS NFV-SOL 014: "Network Functions Virtualisation (NFV) Release 4; Protocols and Data
Models; YAML data model specification for descriptor-based virtualised resource management".
ETSI
9 ETSI GR NFV-EVE 022 V5.1.1 (2022-12)
[i.12] ETSI GS NFV-SOL 018: "Network Functions Virtualisation (NFV) Release 4; Protocols and Data
Models; Profiling specification of protocol and data model solutions for OS Container
management and orchestration".
[i.13] ETSI GS NFV-IFA 006: "Network Functions Virtualisation (NFV) Release 4; Management and
Orchestration; Vi-Vnfm reference point - Interface and Information Model Specification".
[i.14] ETSI GS NFV-IFA 007: "Network Functions Virtualisation (NFV) Release 4; Management and
Orchestration; Or-Vnfm reference point - Interface and Information Model Specification".
[i.15] ETSI GS NFV-IFA 008: "Network Functions Virtualisation (NFV) Release 4; Management and
Orchestration; Ve-Vnfm reference point - Interface and Information Model Specification".
[i.16] ETSI GS NFV-IFA 009: "Network Functions Virtualisation (NFV); Management and
Orchestration; Report on Architectural Options".
[i.17] ETSI GS NFV-IFA 011: "Network Functions Virtualisation (NFV) Release 4; Management and
Orchestration; VNF Descriptor and Packaging Specification".
[i.18] ETSI GS NFV-IFA 013: "Network Functions Virtualisation (NFV) Release 4; Management and
Orchestration; Os-Ma-nfvo reference point - Interface and Information Model Specification".
[i.19] ETSI GR NFV-IFA 029: "Network Functions Virtualisation (NFV) Release 3; Architecture;
Report on the Enhancements of the NFV architecture towards "Cloud-native" and "PaaS"".
[i.20] ETSI GR NFV-IFA 039: "Network Functions Virtualisation (NFV) Release 5; Architectural
Framework; Report on Service Based Architecture (SBA) design".
[i.21] ETSI GS NFV-IFA 040: "Network Functions Virtualisation (NFV) Release 4; Management and
Orchestration; Requirements for service interfaces and object model for OS container management
and orchestration specification".
[i.22] ETSI GR NFV-EVE 019: "Network Functions Virtualisation (NFV) Release 4; Architectural
Framework; Report on VNF generic OAM functions".
[i.23] ETSI Registry for non-MANO artifact sets. .
NOTE: Available at https://nfvwiki.etsi.org/index.php?title=Non_MANO_artifact_sets.
[i.24] IETF RFC 7396: JSON Merge Patch.
[i.25] IETF RFC 8040: "RESTCONF Protocol".
NOTE: Available at https://www.rfc-editor.org/rfc/rfc8040.
[i.26] IETF RFC 8526: "NETCONF Extensions to Support the Network Management Datastore
Architecture".
NOTE: Available at https://www.rfc-editor.org/rfc/rfc8526. ®
[i.27] Kubernetes Documentation: "API Reference".
NOTE: Available at https://kubernetes.io/docs/reference/.
3 Definition of terms, symbols and abbreviations
3.1 Terms
Void.
ETSI
10 ETSI GR NFV-EVE 022 V5.1.1 (2022-12)
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GR NFV 003 [i.1] and the following apply:
DSL Domain Specific Language
gNMI gRPC Network Management Interface
NETCONF Network Configuration
OSI Open Systems Interconnection
SSH Secure SHell
TMN Telecommunications Management Network
4 VNF configuration
4.1 General
Configuration management is one of the five functional areas of the Telecommunications Management Network (TMN)
model. Recommendation ITU-T M.3400 [i.2] defines configuration management as a management functional area that
provides functions to exercise control over, identify, collect data from and provide data to network elements. The
present document focuses on configuration management for providing configuration data to VNFs and collecting such
data from these VNFs.
4.2 VNF configuration items
A VNF instance is a set of software instances and virtualised resources needed for these software instances to execute.
The scope of VNF configuration includes the configuration of both the software and the resources. Resource
configuration is part of the VNF lifecycle management and relies on configuration data available in VNF descriptors
and configuration data generated at runtime. The present document focuses on the configuration of the VNF software,
also known as VNF application configuration.
NOTE 1: In the context of the present document the term "application configuration" should be understood in a
wider sense than the configuration of the application layer of the OSI model.
EXAMPLE: The configuration of forwarding rules in a VNF that provides the functionality of a firewall falls in
the "application configuration" category.
The data items configured as part of the VNF software configuration process can be classified in two broad categories,
as illustrated in figure 4.2-1: virtualisation-dependent items and virtualisation-independent items:
• Virtualisation-dependent items are those items whose value is dependent on decisions made by the NFV
infrastructure and/or the NFV management and orchestration functions. An example of such items is the
VNF's VNFM IP address. Another example is the IP address assigned to a connection point of a VNFC
instance to be configured on another VNFC of the same VNF that needs to communicate with the former (e.g.
a load balancer VNFC).
• Virtualisation-independent items are all other items. Their values are typically determined in the OSS/BSS, as
for a PNF. An example of such items is a forwarding rule for a VNF that provides the functionality of a
firewall.
ETSI
11 ETSI GR NFV-EVE 022 V5.1.1 (2022-12)

Figure 4.2-1: Overview of VNF configuration data
The data items configured as part of the VNF software configuration process can be further classified according to
when to configure them. Some items are intended to be configured during the instantiation process, typically when the
VNF instance cannot be fully up and running without the corresponding values being configured. Others can be
configured at any time once the VNF instance is created and operational. The configuration of the first category of
items is often known as "Day-0" configuration, while the configuration of items in the second category is often
designated as "Day-1" (configured right after instantiation) or "Day-2" configuration (any time after "Day-1"
configuration).
NOTE 2: This classification has to be understood from a VNFC instance viewpoint, e.g. scaling-out a VNF instance
can require Day-0 configuration of the new VNFC instances.
4.3 VNF configuration methods
4.3.1 Overview
Clause 4.3 of the present document provides a description of the configuration methods supported by the NFV
architectural framework at the time of publication. These methods are not mutually exclusive.
4.3.2 Method #A
4.3.2.1 General description
With this configuration method, the VNF receives configuration data directly from the OSS/BSS or from its EM. In the
latter case the data can be originated in the EM or received by the EM from the OSS/BSS.
This method is only applicable to Day-1 and Day-2 configuration as it assumes that the VNF instance can communicate
with the OSS/BSS or an EM. At least one VNFC instance is expected to act a configuration management agent in the
VNF.
The configuration procedure can follow a push (configuration data pushed to the VNF by the OSS/BSS or EM) or pull
model (configuration data retrieved by the VNF instance from the OSS/BSS or
...