Skip to content

Latest commit

 

History

History
43 lines (34 loc) · 1.82 KB

vdenfv.md

File metadata and controls

43 lines (34 loc) · 1.82 KB
Raw

network function virtualization squared

what

Once upon a time there were physical networking devices named switches, gateway, routers, ...

Then the Network Function Virtualization (NFV) arrived and network function were deployed on general purpose standadized hardware.

VDE allows one more layer of virtualization: network functions can run on namespaces (NoN.

why

Because in Local Area Cloud environments where virtual machines, namespaces, Internet of Thread processes can be deployed on any of the physical hosting computers, the network functions must be cloud-ized as well.

how

A VDE namespace (using --multi) can be connected to several VDE plugs: it this way it has several virtual interfaces connected to seveeral virtual (or real) networks.

e.g.

vdens --multi vxvde://239.1.2.3 vxvde://239.1.2.4 vde:///var/run/vde.ctl tap://tapx

Inside the new namespace there will be four virtual interfaces vde0, vde1, vde2, vde3 connected to the four plugs, vde0 to the vxvde whose IP multicast address is 239.1.2.3 and so on.

All the tools for NFV designed for Linux hosts can run in a VDE namespace. Some simple examples include the kernel bridge or routing daemons like Zebra or Quagga.

where

The support is provided by vdens. Actually, the VDE namespace provides just the support for several VDE plugs the same time. Network functions virtualization software runs in the namespace as it would run on the bare O.S. (except from the fact that root access or specific capabilities are not required to manage and run NFV in user namespaces).

references:

Renzo Davoli, NFV à la VDE way Presentation at FOSDEM 2018