On the Fly Orchestration of Unikernels: Tuning and Performance Evaluation of Virtual Infrastructure Managers
📜 Abstract
Network operators are facing significant challenges meeting the demand for more bandwidth, agile infrastructures, innovative services, while keeping costs low. Network Functions Virtualization (NFV) and Cloud Computing are emerging as key trends of 5G network architectures, providing flexibility, fast instantiation times, support of Commercial Off The Shelf hardware and significant cost savings. NFV leverages Cloud Computing principles to move the data-plane network functions from expensive, closed and proprietary hardware to the so-called Virtual Network Functions (VNFs). In this paper we deal with the management of virtual computing resources (Unikernels) for the execution of VNFs. This functionality is performed by the Virtual Infrastructure Manager (VIM) in the NFV MANagement and Orchestration (MANO) reference architecture. We discuss the instantiation process of virtual resources and propose a generic reference model, starting from the analysis of three open source VIMs, namely OpenStack, Nomad and OpenVIM. We improve the aforementioned VIMs introducing the support for special-purpose Unikernels and aiming at reducing the duration of the instantiation process. We evaluate some performance aspects of the VIMs, considering both stock and tuned versions. The VIM extensions and performance evaluation tools are available under a liberal open source licence.
✨ Summary
Summary
The paper investigates whether general-purpose virtual infrastructure managers can support the rapid deployment of ClickOS-based Micro-VNFs for highly dynamic NFV scenarios. It develops a reference model separating VIM core functions, local components, and the compute resource or hypervisor, then maps the model onto OpenStack, Nomad, and OpenVIM using Xen.
The authors modify all three systems to boot diskless ClickOS Unikernels and create tuned variants that remove operations unnecessary for specialized, diskless workloads. The main optimizations include bypassing block-device handling, simplifying guest configuration, avoiding unnecessary image copying and interface resets, reducing communication overhead, and improving work-queue polling behavior.
Under the paper’s experimental setup, stock OpenStack required approximately 2.1 seconds to instantiate a ClickOS VM; tuning reduced this to approximately 1.5 seconds. Nomad required approximately 0.3 seconds, or approximately 0.2 seconds when notification delay was excluded, and local artifact storage reduced driver overhead by about 30 milliseconds. OpenVIM required approximately 1 second in its stock configuration, approximately 0.4 seconds after software tuning, and approximately 0.15 seconds after moving its database-related components to a ramdisk. However, OpenVIM’s latency increased substantially under load, primarily because of libvirt and Xen xenstore overhead; with 300 background VMs, the measured libvirt component reached approximately 0.4 seconds.
The central conclusion is that Unikernel-specific orchestration can substantially reduce deployment latency, but existing VIMs still fall short of the millisecond-scale requirements associated with the most demanding Superfluid NFV scenarios. The authors identify modularity, selective workflow execution, integration with Unikernel build toolchains, optimized Xen toolstacks, and pre-instantiation as important directions for further work.
Influence and subsequent use
A web search found the paper cited as related work in later research on benchmarking open-source NFV MANO systems, indicating that its VIM-performance methodology and NFV orchestration analysis were used as background for subsequent MANO evaluations. (sciencedirect.com) The paper is also listed among the publications associated with the European Commission’s 5G EVE validation project, providing evidence of connection to an applied 5G experimentation program, although the available record does not establish that the specific implementations were deployed operationally. (cordis.europa.eu) The authors’ VIM modifications and evaluation tools were released as open-source artifacts, supporting reproducibility and reuse. (arxiv.org)