The present document reviews virtualisation technologies and studies their impact on the NFV architectural framework and specifications. It also provides an analysis of the pros and cons of these technologies.
The present document provides requirements for the hypervisor domain as it pertains to an operator's network. It focuses on gaps between Network Functions Virtualisation (NFV) use cases and the industry state of art at the time of publication. Therefore requirements that are deemed to be supported by most hypervisor solutions at the time of publication are not repeated in the present document.
The widespread adoption of virtualised implementation of functions has brought about many changes and challenges for the testing and benchmarking industries. The subjects of the tests perform their functions within a virtualisation system for additional convenience and flexibility, but virtualised implementations also bring challenges to measure their performance in a reliable and repeatable way, now that the natural boundaries and dedicated connectivity of physical network functions are gone. Even the hardware testing systems have virtualised counterparts, presenting additional factors to consider in the pursuit of accurate results.
The present document specifies vendor-agnostic definitions of performance metrics and the associated methods of measurement for Benchmarking networks supported in the NFVI. The Benchmarks and Methods will take into account the communication-affecting aspects of the compute/networking/virtualisation environment (such as the transient interrupts that block other processes or the ability to dedicate variable amounts of resources to communication processes). These Benchmarks are intended to serve as a basis for fair comparison of different implementations of NFVI, (composed of various hardware and software components) according to each individual Benchmark and networking configuration evaluated. Note that a Virtual Infrastructure Manager (VIM) may pay a supporting role in configuring the network under test. Examples of existing Benchmarks include IETF RFC 2544 Throughput and Latency (developed for physical network functions).
Although many metrics for the performance and utilization of the Network Function Virtualisation Infrastructure (NFVI) components have been in wide use for many years, there were no independent specifications to support consistent metric development and interpretation. The present document provides the needed specifications for key NFVI metrics.
The present document specifies detailed and vendor-agnostic key operational performance metrics at different layers of the NFVI, especially processor usage and network interface usage metrics. These metrics are expected to serve as references for processed and time-aggregated measurement values for performance management information that traverses the Or-Vi and/or Vi-Vnfm reference points of the NFV architectural framework. The present document contains normative provisions.
Although many metrics for the performance and utilization of the Network Function Virtualisation Infrastructure (NFVI) components have been in wide use for many years, there were no independent specifications to support consistent metric development and interpretation. The present document provides the needed specifications for key NFVI metrics.
The present document specifies detailed and vendor-agnostic key operational performance metrics at different layers of the NFVI, especially processor usage and network interface usage metrics. These metrics are expected to serve as references for processed and time-aggregated measurement values for performance management information that traverses the Or-Vi and/or Vi-Vnfm reference points of the NFV architectural framework. The present document contains normative provisions.
The present document provides methodology guidelines for interoperability testing of NFV features, starting from a review of some basic concepts for interoperability testing and their fit in an NFV environment and a methodology for the development of interoperability test specifications illustrated with examples of basic NFV operations. A high level analysis of some core NFV capabilities allows to identify a generic architecture for the associated System Under Test configurations, and to classify some initial Interoperability Feature areas.
The present document is organized as follows:
Clause 4 provides an overview of common interoperability concepts and testing methodology guidelines.
Clause 5 identifies a generic system under test (SUT) architecture and some initial SUT configurations for interoperability testing of basic NFV capabilities.
Clause 6 identifies and analyses some initial NFV interoperability feature areas and outlines for each of them the impacted functional blocks and interfaces, as well as the applicable SUT configurations described in clause 5.
The present document focusses on the characterization of Virtualised Network Functions (VNF) as part of their configuration and deployment in "the Cloud". Such VNFs are assumed to be implemented using generic cloud computing techniques beyond virtualization [i.1]. For example, the VNFs can be built with re-usable components as opposed to a unique - and potentially proprietary - block of functions.
Cloud native VNFs are expected to function efficiently on any network Cloud, private, hybrid, or public. The VNF developer is therefore expected to carefully engineer VNFs such that they can operate independently in the desired Cloud environment. Cloud environment can be implemented based on hypervisor/VM or container technology. This is an indication of the "readiness" of VNFs to perform as expected in the Cloud. The objective of the present document is to develop the characterization of the "Cloud Readiness" of VNFs.
From an operator perspective, it is essential to have a complete description of cloud native readiness of VNFs; this description will help operators in their VNF selection process. To do this, it is essential that a set of non-functional parametric characterizations be developed that appropriately describe the cloud native nature of VNFs. Non-functional parameters describe the environmental behaviour of VNFs residing in the Cloud. They do not describe the actual working functions of the VNF; rather they describe how the VNF can reside independently in the Cloud without constant operator involvement.
The present document considers not only the "pure" cloud native VNF implementations (e.g. no internal resiliency or state) but also some transition implementations to cloud native such as the VNFs with internal resiliency.
Non-functional characteristics of a cloud native VNF are described through a VNF Product Characteristic Descriptor (VNFPCD) created by the VNF provider. Usage of the cloud native VNFPCD is as follows:
The cloud native VNFPCD is used by an operator to decide on what VNF product to deploy to fulfil a particular functionality, when the decision is based on non-functional parameters.
The VNFPCD can be used in a VNF market place for a standardized description of the VNF products non- functional characteristics and as such can be checked/searched for automatically.
The intent of the present document is to identify a minimum set of non-functional parameters by which VNFs are characterized as cloud native. The non-functional parameters are classified according to the specific environmental behaviour of the VNF.
Each behaviour then provides a list of specific non-functional parameters along with specific requirements such that the cloud native nature of the VNF can be satisfactorily established.
The present document specifies requirements for a set of abstract interfaces enabling a VNF to leverage acceleration services from the infrastructure, regardless of their implementation. The present document also provides an acceleration architectural model to support its deployment model.
The goals of the present document are:
to identify common design patterns that enable an executable VNFC to leverage, at runtime, accelerators to meet their performance objectives;
to describe how a VNF Provider might leverage those accelerators in an implementation independent way; and
to define methods in which all aspects of the VNF (VNFC, VNFD, etc.) could be made independent from accelerator implementations.
VNF providers have to mitigate two goals:
VNFs might have constraints to perform their function within certain power consumption boundaries, CPU core count, PCI express slot usage and with good price/performance ratio; and
VNFs should accommodate most if not all deployment possibilities.
The present document specifies performance benchmarking metrics for virtual switching, with the goal that the metrics will adequately quantify performance gains achieved through virtual switch acceleration conforming to the associated requirements specified herein. The acceleration-related requirements will be applicable to common virtual switching functions across usage models such as packet delivery into VNFs, network overlay and tunnel termination, stateful Network Address Translators (NAT), service chaining, load balancing and, in general, match-action based policies/flows applied to traffic going to/from the VMs. The present document will also provide deployment scenarios with applicability to multiple vendor implementations and recommendations for follow-on proof of concept activities.
The present document specifies the interfaces supported over the Or-Vnfm reference point of the Network Functions Virtualisation Management and Orchestration (NFV-MANO) architectural framework ETSI GS NFV-MAN 001 as well as the information elements exchanged over those interfaces.
The present document specifies the interfaces supported over the Or-Vnfm reference point of the Network Functions Virtualisation Management and Orchestration (NFV-MANO) architectural framework ETSI GS NFV-MAN 001 as well as the information elements exchanged over those interfaces.
The present document specifies the interfaces supported over the Vi-Vnfm reference point of the NFV-MANO architectural framework as well as the information elements exchanged over those interfaces.
