![]() ![]() O From a Memory Management Unit(MMU) point of view, there are differences in how the paging process is conducted between two environments. ![]() Different CPU resource assignment methods may have different CPU utilization perspectives for performance benchmarking. On the other hand, C-VNFs use the host CPU without virtualization. O In the VM-based infrastructure, each VM manipulates packets in the kernel of the guest OS through its own CPU threads, virtualized and assigned by the hypervisor. O About configuration parameters, the containerized infrastructure needs a specified management system instead of a hypervisor(e.g. ![]() While the capabilities of servers and storage should meet the minimum requirements for testing, it is possible to deploy a test environment with fewer capabilities than in the VM-based infrastructure. O When we consider hardware configurations for the containerized infrastructure, all components described in can be part of the test setup. The absence of the guest OS and the hypervisor necessitates the following considerations that occur in the test environment: ¶ A major distinction between the containerized and the VM-based infrastructure is that with the former, all VNFs share the same host resources including but not limited to computing, storage and networking resources, as well as the host Operating System(OS), kernel and libraries. In Figure 1, we describe two different NFV architectures: VM-based and Containerized. (a) VM-Based Infrastructure (b) Containerized Infrastructure +-| physical network |-+ +-| physical network |-+ || | Host OS Kernel | || || | Host OS Kernel | || || Guest VM | | Guest VM || || Container | | Container || Note that, although the detailed configurations of both infrastructures differ, the new benchmarks and metrics defined in can be equally applied in containerized infrastructure from a generic-NFV point of view, and therefore defining additional metrics or methodologies is out of scope. In particular, we focus on differences in system configuration parameters and networking configurations of the containerized infrastructure compared with VM-based NFV infrastructure. In this draft, we describe differences and additional considerations for benchmarking containerized infrastructure based on and. Occasioned by these differences, deployment scenarios for testing network performance described in may be partially applied to the containerized infrastructure, but other scenarios may be required. In the, they describe differences in networking structure between the VM-based and the containerized infrastructure. For container networking, the host system may use a virtual switch(vSwitch), but other options exist. For example, the internal communication between VNFs in the same host uses the L2 bridge function, while communication with external node(s) uses the 元 router function. In the containerized infrastructure, a VNF network is implemented by running both switch and router functions in the host system. Accordingly, additional configuration parameters and testing strategies may be required. When we consider benchmarking for VNFs in the containerized infrastructure, it may have a different System Under Test(SUT) and Device Under Test(DUT) configuration compared with both black-box benchmarking and VM-based NFV infrastructure as described in. While previous NFV infrastructure uses a hypervisor to allocate resources for Virtual Machine(VMs) and instantiate VNFs on it, the containerized infrastructure virtualizes resources without a hypervisor, therefore making containers very lightweight and more efficient in infrastructure resource utilization compared to the VM-based NFV infrastructure. Recently NFV infrastructure has evolved to include a lightweight virtualized platform called the containerized infrastructure, where VNFs share the same host Operating System(OS) and they are logically isolated by using a different namespace. described considerations for configuring NFV infrastructure and benchmarking metrics, and gives guidelines for benchmarking virtual switch which connects VNFs in Open Platform for NFV(OPNFV). The Benchmarking Methodology Working Group(BMWG) has recently expanded its benchmarking scope from Physical Network Function(PNF) running on a dedicated hardware system to Network Function Virtualization(NFV) infrastructure and Virtualized Network Function(VNF). ![]()
0 Comments
Leave a Reply. |