ETSI Blog

What happened at the NFV Evolution virtual event?

2021-05-12 Posted by Bruno Chatras, ETSI NFV Chair 15508 Hits

NFV blog052021

A virtual event on NFV Evolution organized by ETSI in partnership with Telecom TV and sponsored by Huawei was held from 19 to 21 April 2021.  The objective of the event was for the ETSI NFV Industry Specification Group (ISG) to get feedback from the industry on implementation experience with the ISG’s specifications and on future topics to be addressed in next specification releases. The event was also an opportunity for the participants to get updated on ETSI NFV’s activities, deliverables and future plans, as well as on the progress made in open source communities with regards to the convergence with the ISG’s standards. The event was held in parallel with the 34th meeting of the ISG. The choice was not accidental as this was the meeting where the ISG launched the process for collecting proposals from its members and participants on the features to be addressed within the scope of its next specification release (NFV Release 5).

The event programme featured six original presentations selected from the responses received to an open call, addressing deployment experience, new use cases and technical requirements:

  • Mr. Yuya Kuno, NTT DOCOMO, presented DOCOMO’s experience in developing and operating NFV and future expansion.
  • Mr. Pierre Lynch, Keysight Technologies and Ms. Silvia Almagia, ETSI CTI Technical Expert jointly presented “Measuring NFV Evolution: ETSI NFV Plugtests”.
  • Mr. Borja Nogales, Universidad Carlos III de Madrid, presented “An NFV system to support service provisioning on UAV platforms: a walkthrough on implementation experience and standardization challenges”.
  • Dr. Lingli Deng, China Mobile, presented “From Orchestration Towards Automation”
  • Dr. Haopeng Zhu, Huawei Technologies Co., presented “Towards the future of NFV: Edge-native, Containerization, Networking-NFV convergence”.
  • Mr. Gianpietro Lavado, Whitestack, presented about the advances in deployment of standardized NFV Orchestration through ETSI OSM.

ETSI NFV Release 3: update on protocols and data model specification outcomes

2021-01-21 Posted by Joan Triay, ETSI NFV Technical Manager and Zarrar Yousaf, ETSI NFV SOL working group Chair 18279 Hits

2020 turned out to be an unexpected year, with the COVID19 pandemic adversely impacting the “normal” day-to-day lives of humans across the globe. However, even during this turn of events and unforeseen testing times, communication networks demonstrated their efficacy in keeping people and businesses connected. More concretely, Network Functions Virtualisation (NFV) proved its feasibility by enabling the operators to gracefully manage high demand for network connectivity.

NFV blog evolution new vision imageUndaunted by this situation, the technical experts at the ETSI ISG NFV continued to work tirelessly developing and delivering specifications that help get and keep “everyone/everything connected”. And the hard work paid off as ETSI ISG NFV delivered during the second half of 2020 new and updated "protocols and data model" (stage 3) specifications incorporating NFV Release 3 features.

The experts in the Solutions (SOL) working group completed stage 3 work on a subset of the NFV Release 3 features. One of the first features that was already finalised in 2019 was "Management of NFV-MANO" (FEAT11) with the release of ETSI GS NFV-SOL 009 V3.3.1. This document specifies a set of RESTful protocols and APIs that can be used to manage different aspects regarding configuration, performance, fault and logging of entities implementing specified NFV-MANO functional blocks. The defined APIs leveraged the same RESTful principles used for NFV-MANO APIs in Release 2, i.e., the ones used for managing VNF instances, NS instances and on-boarding VNF Packages, NSDs and other artefacts.

New outcomes on the development of NFV-MANO APIs continued in 2020 with the release of ETSI GS NFV-SOL 011 V3.3.1, which specifies NFV-MANO APIs related to management across "NFV-MANO administrative domains" (FEAT08). These APIs are produced by the NFVO and allow different administrative domains to communicate over the Or-Or reference point to help coordinate the management of NS instances deployed on their respective administrative domains. The Or-Or reference point is set in between NFVO instances placed on different administrative domains, as specified in ETSI GS NFV-IFA 030. For instance, the APIs of ETSI GS NFV-SOL 011 enable reusing an NS instance deployed on a domain A and nest it into another NS instance deployed on a domain B. Due to the functional similarities with existing capabilities offered by the NFVO to other systems such as OSS/BSS, most of the APIs are identical or based on those specified in ETSI GS NFV-SOL 005.

OS container object model and management interfaces: The first set of Cloud-Native VNF orchestration specifications

2020-11-10 Posted by Jörg Aelken, Rapporteur of ETSI GS NFV-IFA 040 21555 Hits

The ETSI Industry Specification Group (ISG) NFV has published the initial release of ETSI GS NFV-IFA 040 titled "Requirements for service interfaces and object model for OS container management and orchestration specification". This document is the first normative specification delivered for the NFV Release 4 feature on “Cloud-native VNFs and Container Infrastructure management”. The specification propagates the recommendations from the study in ETSI GR NFV-IFA 029 and formally specifies the new functions required for the management and orchestration of OS containers, the Container Infrastructure Service Management (CISM) and the Container Image Registry (CIR). The CISM is responsible for maintaining the containerized workloads while the CIR is responsible for storing and maintaining information of OS container software images.NFV release 4 FEAT 17 blogpost

To enable a consistent and generic system for the management of containerized VNFs, ETSI GS NFV-IFA 040 specifies an abstract NFV object model for OS container management and orchestration, including their relationship to the core information models of NFV-MANO. The abstract NFV objects are also expected to be used in specifications profiling APIs of de-facto standard solutions, to map the abstract NFV objects to objects of the specific de-facto standard solution. One of the introduced abstract NFV objects is the Managed Container Infrastructure Object (MCIO), an object managed and exposed by the CISM, characterized by the desired and actual state of a containerized workload. Managed objects from Kubernetes® such as Deployment or Service are examples which map to an MCIO. Another new NFV object is the Managed Container Infrastructure Object Package (MCIOP), a hierarchical aggregate of information objects including declarative descriptors and configuration files for one or multiple MCIOs. Helm charts as specified by CNCF® are an example which maps to an MCIOP.