Beyond VNFM: Filling the gaps of the ETSI VNF manager to fully support VNF life cycle operations

Abstract

One of the main challenges to use network functions virtualization (NFV) is to properly manage the life cycle of the virtualized network functions (VNFs).Current solutions based on the ETSI standard NFV architectural framework are complex and require the knowledge of a myriad of details of the underlying infrastructure. This work proposes a VNF manager (VNFM) specification that supports different platforms and VNF utilization scenarios. The proposed VNFM specification defines a set of APIs, modules, and components, for both the end user and the back-end that provide the fundamental set of operations required to fully manage the VNF life cycle. Our primary goal is to simplify the operations, in particular reducing the need for the network operator to know the details of the virtualized infrastructure. Note that the proposed solution fills a gap and complements the ETSI VNFM module. A prototype was implemented, and experimental results show the effectiveness and low overhead of the proposed solution. INTRODUCTIONNetwork functions virtualization (NFV) is a paradigm that presents several advantages in comparison with traditional middle boxes, including the flexibility for service provisioning and the reduction of both operational (OPEX) and capital (CAPEX) expenditures. 1,2 NFV uses virtualization techniques to provide network services through virtual devices running on generic hardware (eg, x86 architecture). Thus, it is much simpler to make new services available as well as to modify and update existing services. There is no need for a proprietary or specialized hardware equipment, resulting in cost reduction and flexible service provisioning. 3 Nevertheless, there are several challenges to the practical use of NFV technology, including the effective management and performance assurance of virtualized network functions (VNFs). The European Telecommunications Standards Institute (ETSI) has been working on an NFV architectural framework. One of the main components of that architecture is the VNF manager (VNFM), an entity responsible for managing the life cycle of VNFs. Management operations allow for example instantiate, delete, and update virtualized functions, but there are also other important operations, such as automatically scaling up/down resource usage and VNF recovery in case of failure. 4 Several platforms have attempted to provide a suitable implementation for the ETSI VNFM component. [5][6][7][8][9] In general, these platforms require laborious work to execute tasks related to the life cycle management of VNFs, from the creation

Customizable Mapping of Virtualized Network Services in Multi-datacenter Environments Based on Genetic Metaheuristics

“…The Network Functions Virtualization (NFV) [19] paradigm allows the implementation of network functions using virtualization technologies. In comparison with hardware alternatives, NFV technology reduces costs and increases flexibility [20]. A Virtualized Network Function (VNF) is the basic NFV unit which processes network traffic applying some specific functionality.…”

Dynamic Network Slice Scaling Assisted by Prediction in 5G Network

“…Each stage involves network costs and energy consumption. The cost of maintaining redundant VNFs is much smaller than that associated with newly added VNFs [32]- [33]. Therefore, we use redundant VNFs to reduce unnecessary stages of creating VNFs.…”

Além do OpenStack: Disponibilizando o Suporte para Funções Virtualizadas de Rede NFV-MANO no CloudStack

“…O ciclo de vida envolve ações como a instanciação, atualização e remoção de VNFs. Outras atividades importantes incluem o ajuste automático de recursos computacionais e a detecção e recuperação de VNFs falhas [Venâncio et al 2019]. A arquitetura do NFV-MANO, e em especial o VNFM,é normalmente implementada sobre plataformas de computação em nuvem.…”