Download Network Virtualization Basics

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Net neutrality law wikipedia , lookup

Distributed firewall wikipedia , lookup

TV Everywhere wikipedia , lookup

Zero-configuration networking wikipedia , lookup

Cracking of wireless networks wikipedia , lookup

Peering wikipedia , lookup

Asynchronous Transfer Mode wikipedia , lookup

Computer network wikipedia , lookup

Piggybacking (Internet access) wikipedia , lookup

Recursive InterNetwork Architecture (RINA) wikipedia , lookup

Network tap wikipedia , lookup

Airborne Networking wikipedia , lookup

List of wireless community networks by region wikipedia , lookup

Peer-to-peer wikipedia , lookup

Transcript
University of Waterloo - eNVy
INTRODUCTION TO
NETWORK VIRTUALIZATION
Wednesday, May
14, 2008
Mosharaf Chowdhury
Member, eNVy Project
1
What is Virtualization?
2

Transparent abstraction of computing platform and
resources


Multiple logical interpretations of the physical characteristics
Virtualized everything
Virtual machines: VMware, Xen
 Storage virtualization: SAN
 Data-center virtualization

University of Waterloo - eNVy
Wednesday, May 14, 2008
Network Virtualization for Dummies
3

Making a physical network appear as multiple
logical ones
Physical Network
Virtualized Network - 1
University of Waterloo - eNVy
Virtualized Network - 2
Wednesday, May 14, 2008
Why Virtualize ?
4

Internet is almost ossified



Hard to come up with a one-size-fits-all architecture


Almost impossible to predict what future might unleash
Why not create an all-sizes-fit-into-one instead!


Lots of band-aids and makeshift solutions (e.g. overlays)
A new architecture (aka clean-slate) is needed
Open and expandable architecture
Testbed for future networking architectures and protocols
University of Waterloo - eNVy
Wednesday, May 14, 2008
Related Concepts
5

Virtual Private Networks (VPN)



Active and Programmable Networks



Virtual network connecting distributed sites
Not customizable enough
Customized network functionalities
Programmable interfaces and active codes
Overlay Networks


Application layer virtual networks
Not flexible enough
University of Waterloo - eNVy
Wednesday, May 14, 2008
Network Virtualization Model
6




Business Model
Architecture
Design Principles
Design Goals
University of Waterloo - eNVy
Wednesday, May 14, 2008
Business Model
7
Players

Relationships
Infrastructure Providers (InPs)

Manage underlying physical networks
End User

Service Providers (SPs)



Broker
End Users


SLA
Create and manage virtual networks
Deploy customized end-to-end services
NPA
Buy and use services from different service
providers
Brokers

EIA
Service Provider
SIA
Infrastructure
Provider
IIA
Mediators/Arbiters
University of Waterloo - eNVy
Wednesday, May 14, 2008
Architecture
8
University of Waterloo - eNVy
Wednesday, May 14, 2008
Design Principles
9

Concurrence of multiple heterogeneous
virtual networks


Introduces diversity
Service Provider N
Opens the door for network virtualization
economics
…
Service Provider 1
Virtual Network 1

Inheritance of architectural attributes


Promotes value-addition
Revisitation of virtual nodes

Infrastructure
Provider N+1
Virtual Network N
Recursion of virtual networks

Hierarchy of Roles
Service Provider 0
Virtual Network 0
Simplifies network operation and
management
Infrastructure
Provider 2
Infrastructure
Provider 1
Infrastructure
Provider 0
University of Waterloo - eNVy
Wednesday, May 14, 2008
Design Goals (1)
10

Flexibility

Service providers can choose




No need for co-ordination with others


arbitrary network topology,
routing and forwarding functionalities,
customized control and data planes
IPv6 fiasco should never happen again
Manageability



Clear separation of policy from mechanism
Defined accountability of infrastructure and service providers
Modular management
University of Waterloo - eNVy
Wednesday, May 14, 2008
Design Goals (2)
11

Scalability
Maximize the number of co-existing virtual networks
 Increase resource utilization and amortize CAPEX and OPEX


Security, Privacy, and Isolation

Complete isolation between virtual networks


Logical and resource
Isolate faults, bugs, and misconfigurations

Secured and private
University of Waterloo - eNVy
Wednesday, May 14, 2008
Design Goals (3)
12

Programmability
Of network elements e.g. routers
 Answer “How much” and “how”
 Easy and effective without being vulnerable to threats


Heterogeneity

Networking technologies


Optical, sensor, wireless etc.
Virtual networks
University of Waterloo - eNVy
Wednesday, May 14, 2008
Design Goals (4)
13

Experimental and Deployment Facility
PlanetLab, GENI, VINI
 Directly deploy services in real world from the testing phase


Legacy Support
Consider the existing Internet as a member of the collection
of multiple virtual Internets
 Very important to keep all concerned parties satisfied

University of Waterloo - eNVy
Wednesday, May 14, 2008
Definition (Sort of)
14
Network virtualization is a networking environment that allows
multiple service providers to dynamically compose multiple
heterogeneous virtual networks that co-exist together in isolation
from each other, and to deploy customized end-to-end services
on-the-fly as well as manage them on those virtual networks for
the end-users by effectively sharing and utilizing underlying
network resources leased from multiple infrastructure providers.
University of Waterloo - eNVy
Wednesday, May 14, 2008
Existing Projects
15

Four general categories
1.
Networking technology

2.
Layer of virtualization

3.
Physical layer (UCLP), Application layer (VIOLIN)
Architectural domain

4.
IP (X-Bone), ATM (Tempest)
Network resource management (VNRMS), Spawning networks
(Genesis)
Level of virtualization

Node virtualization (PlanetLab), Full virtualization (Cabo)
University of Waterloo - eNVy
Wednesday, May 14, 2008
Future Works
16

Four general directions
1.
Instantiation

2.
Logistics

3.
Runs them
Management

4.
Creates virtual networks
Manages them
Interactions

Let them flourish
University of Waterloo - eNVy
Wednesday, May 14, 2008
Reference
17

N.M. Mosharaf Kabir Chowdhury, Raouf Boutaba,
“A Survey of Network Virtualization”, University of
Waterloo Technical Report CS-2008-25, Oct. 2008.
University of Waterloo - eNVy
Wednesday, May 14, 2008
18
Questions ? || // Comments
University of Waterloo - eNVy
Wednesday, May 14, 2008