Network Virtualization
Network Virtualization
This section looks at the important area of network virtualization. One immediate difficulty is that this term is
defined differently in a number of academic and industry publications. So we begin by defining some terms,
based on definitions in ITU-T Y.3011 (Framework of Network Virtualization for Future Networks, January
2012):
Physical resource: In the context of networking, physical resources include the following: network devices,
such as routers, switches, and firewalls; and communication links, including wire and wireless. Hosts such as
cloud servers may also be considered as physical network resources.
Logical resource: An independently manageable partition of a physical resource, which inherits the same
characteristics as the physical resource and whose capability is bound to the capability of the physical resource.
An example is a named partition of disk memory.
Virtual resource: An abstraction of a physical or logical resource, which may have different characteristics
from the physical or logical resource and whose capability may be not bound to the capability of the physical or
logical resource. As examples, virtual machines (VMs) may be moved dynamically, VPN topologies can be
altered dynamically, and access control restrictions may be imposed on a resource.
Virtual network: A network composed of multiple virtual resources (that is, a collection of virtual nodes and
virtual links) that is logically isolated from other virtual networks. Y.3011 refers to a virtual network as a
logically isolated network partition (LINP).
Network virtualization (NV): A technology that enables the creation of logically isolated virtual networks
over shared physical networks so that heterogeneous collections of multiple virtual networks can
simultaneously coexist over the shared physical networks. This includes the aggregation of multiple resources
in a provider and appearing as a single resource.
NV is a far broader concept than VPNs, which only provide traffic isolation, or VLANs, which provide a basic
form of topology management. NV implies full administrative control for customizing virtual networks both in
terms of the physical resources used and the functionalities provided by the virtual networks.
The virtual network presents an abstracted network view whose virtual resources provide users with services
similar to those provided by physical networks. Because the virtual resources are software defined, the manager
or administrator of a virtual network potentially has a great deal of flexibility in altering topologies, moving
resources, and changing the properties and service of various resources. In addition, virtual network users can
include not only users of services or applications but also service providers. For example, a cloud service
provider can quickly add new services or expanded coverage by leasing virtual networks as needed.
A Simplified Example
To get some feel for the concepts involved in network virtualization, adapted from the ebook Software Defined
Networking—A Definitive Guide [KUMA13], shows a network consisting of three servers and five switches.
One server is a trusted platform with a secure operating system that hosts firewall software. All the servers run a
hypervisor (virtual machine monitor) enabling them to support multiple VMs. The resources for one enterprise
(Enterprise 1) are hosted across the servers and consist of three VMs (VM1a, VM1b, and VM1c) on physical
server 1, two VMs (VM1d and VM1e) on physical server 2, and firewall 1 on physical server 3. The virtual
switches are used to set up any desired connectivity between the VMs across the servers through the physical
switches. The physical switches provide the connectivity between the physical servers. Each enterprise network
is layered as a separate virtual network on top of the physical network. Thus, the virtual network for Enterprise
1 by a dashed circle and labeled VN1. The labeled circle VN2 indicates another virtual network.
Simple Network with Virtual Machines Assigned to Different Administrative Groups
At the bottom are the physical resources, managed across one or more administrative domains. The servers are
logically partitioned to support multiple VMs. This includes, at least, a partitioning of memory, but may also
include a partitioning of the pool of I/O and communications ports and even of the processors or cores of the
server. There is then an abstraction function that maps these physical and logical resources into virtual
resources. This type of abstraction could be enabled by SDN and NFV functionality, and is managed by
software at the virtual resource level.