No abstract

A arquitetura de referência NFV-MANO (NFV - Management and Orchestration) consiste de um conjunto de especificações relacionadas ao gerenciamento do ciclo de vida e orquestração de VNFs (Virtualized Network Functions). Curiosamente, boa parte dos esforços de desenvolvimento em NFV (Network Function Virtualization) são focados na plataforma de nuvem OpenStack e, em especial, no projeto Tacker. O CloudStack, porém, uma das principais plataformas de nuvens, tem sido superficialmente explorado no contexto do NFV-MANO. Este trabalho propõe o Vines (Vines Is an NFV-MANO Extensible Solution), uma solução integrada à plataforma CloudStack para implantação e gerenciamento do ciclo de vida de VNFs, o que inclui desde a instanciação, atualização e remoção de VNFs, até a recuperação automática de falhas e escalabilidade vertical. Para isso, um VNF Manager (VNFM) foi desenvolvido, disponibilizando um conjunto completo de operações de ciclo de vida de VNFs. Além disso, o Vines tem uma vantagem sobre o Tacker, pois suporta a gerência interna de VNFs. Resultados de experimentos comparativos entre o CloudStack/Vines e o OpenStack/Tacker, ressaltam a viabilidade da proposta.

No abstract

No abstract

No abstract

No 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

No abstract