network virtualization and application : a new look of networking

Copyright (C) 2012 Nippon Telegraph and Telephone Corp.

Network virtualization and application : A new look of networking

Atsushi Takahara

NTT Network Innovation Labs

2012/8/24

1


Introduction

Cloud technologies realize “everything on net”. In networking,

Various usage patterns are required by network applications.

A application/users specific networking is desired.

Year 2011 was the turning point. 3.11 Disaster in Japan (great east Japan earthquake)

Network Virtualization became common. ONF

Changes Software Defined Network

Name change? Broader meaning?

Resilient network Network should be flexible according to the availability of

resources.

2


What should we consider?

How can you use the network virtualization platform?

Properties

Structure

slicing

Function

Processing in node/network

Control plane/Data plane

Operation & Management

Application

How to map your requirements to NV platform?

3


Outline

1. Network Architecture for flexible network

Required functions

Operation and Management architecture in Vnode testbed

Cross layer control

Programmability in measurement tools

2. Case studies of using network virtualization

Collaborative workspace on net

Resilient networking with temporal resources

Redundancy in Data and Slicing

3. Summary

4


NETWORK VIRTUALIZATION PLATFORM

5


The benefit of “Network Virtualization”

The best solution for a customer specific network can be provided.

No extra resources or additional resources are used.

Networking is flexible to the demand of customers.

Still, a network is operational or manageable.

END-TO-END not Over-The-Top

6

Customer NWs NTT groups FNs Service Providers

NTT FN A

Sensor Mobile

NTT’s

Service

servers

Service

Providers

NTT FN B

Management Function Management

Function

Home

Management

Function

Management

Function

Enterprise


ICT resource management platform

Flexible network

High performance Packet processing Servers

Flexible optical Transport network

Programmable High-performance network

Distributed computing Network server Infrastructure

Cloud

Session Servers

Operation & Management

Virtual Nodes etc.

Link systems ＯＸＣ／ＰＴＳ

Carrier grade virtual network Access

Flexible network


NW Virtualization Project (VNode project)

8

vNode

Joint project with NEC, Fujitsu, Hitachi, U. of Tokyo and NICT

from 2008. Now is the second phase funded by NICT.

Mng. and Cntl. I/F

Programming Function

Redirection Function

Packet Redirection Table

EMS

Hardware Processing (FPGA)

Port

Policing Shaping

Resource Mng. Table

Hardware Cards

CPU, Memory etc.

Bandwidth, Queue

unused

unused

unused

Slice 1 2 3 … n

Software Processing (VM)

[A] [B]

11 VNodes are working on JGN-X testbed.


Operation & Management in NV

A specific network requires a specific operation.

A slice needs its specific operation and management system.

This could be the bottle neck if this is not efficient.

NTT is working on the designing management and operation architecture for Vnode platform.

9


The New Role in the management system of VN

Slice developer

Operator : an administrator of physical networks

Developer : an operator of Slices and provider of network services over Slices

User : a user who transmits data over Slices

10

Operator (NMS)

User

Network Virtualization Platform

(Physical Network)

Data Exchange

Provide Slice

Slice (Logical/Virtual

Service Network)

Developer

* Operator and Developer may be a same person/organization

Provide the Data Transmitting Service

Operation (Management and Control)

Create and Delete

Slices

Slice Operation

Dynamic Slice Creation


6-Plane model

11

M-plane for Developper

R R

Developer

D-Plane P

R

C-Plane EMS

EMS

M-Plane

Y-Plane

NMS

P

P

R

EMS EMS

P A A vN vN vN vN Slice

User

Developer

vL vL vL

User

Vnode platform Slice

Z-Plane Management IF Management IF

A: Access Gateway, P: Programmer, R: Redirector vN : virtual Node (仮想ノード), vL : virtual Link (仮想リンク)

• We define 6 (3+3) plane model for Vnode system. • D/C/M-Plane： Traditional 3 plane model for O&M • Y-Plane： Management plane for the developer • Z-Plane： Management plane for a slice handled by a developer • Slice： D-plane for a developer


Flexibility in Transport network

Transport network is shared by several different services. “path” is as a resource and “path” is provided by Transport

network. Virtualized network management and Transport network

management should be related.

In future, more flexible in Transport network will be available and more deeper relationship should be considered. Software defined network + Software defined Optical network Deep programmable network + Deep programmable elastic

network

12

Transport Network

Avilable “path” resources）

Cooperating between VN management and Transport NW management

Exiisting/Other networks

Virutaulized Network

TNC

DC

Available “path” resources

Juniper

Juniper

Juniper

Juniper

Juniper


Images of Mngt. Console (Portal)

7th/M

arch/2

012

13

Created Slice


Programmable measurement tools

Programmable network seeks a programmable measurement tool.

No fixed or pre-defined protocol are used.

Measurement method is depending on the network functoins.

14

PRESTA 10G NIC & general purpose PC Linux Kernel

PRESTA API library Provides raw software interface

Libpcap-compatible API

library

Advanced traffic

monitoring tools

• In-service QoS

monitoring

• Highly accurate traffic

playback

• perfSONAR-HRA

• Open-source

monitoring tools Timing source input (10 MHz, 1PPS)

Packet processing Engine

tcpdump softflowd


A NEW LOOK OF NETWORKING WITH SLICE

15


Current status

Phase 1 of VNode project (< 3 years) WE REALIZED and has been OPERTED THE DEEP

PROGRAMMABLE NETWORK platform.

WE also implemented the applications for evaluating our system architecture.

Next : exploiting the below things Applications

More than Look and Feel

Usability A domain and multi domains are considered.

Implementation of the VNode architecture Learning by doing in JGN-X VNode test bed

P-R-AGW Architecture concept

NICT designed the well organized projects for exploiting next phase R&D milestones.

16


光インフラ網

Exploting Network Virtualization System

Architecture

管理装置

クラウド

ネットワーク

スライス収容

アクセス

ゲートウェイ

アクセスポイント

仮想化

エッジ端末仮想化

スライス１スライス２

仮想化ノード

ネットワーク新機能１（課題ウ）ネットワーク新機能２（課題ウ）

Phase2 project map

17

3 projects are stimulating to others in positive manner!

Exploiting Applications by 8 sub projects

Exploiting more easy-to-use methods and tools


Important action

18

Real Problem

Network Virtualization platform

a new look of networking

with


COLLABORATIVE WORK FLOW ON NET

Network Virtualization Use case 1

19

A part of this work is supported by NICT.


A case study : Pre/Post production of Cinema

Digital processing in workflow

Previously, all the things was done in a studio.

Now, the works are spread over the world.

They need the virtual studio.

The dead line is so hard.

Several projects are run in parallel and the different companies are related.

20


Proposal 1 : Project & task based virtual NWs

Two-layer NW / connection management for video creation workflows.

Connection restriction defined by contract-based ‘Projects’

Virtual NWs (slices) related to each ‘task’ in a Project Multiple combinations of production companies (original contractors) and vendors

(subcontractors) can co-exist in a physical NW platform.

Projects and their task NWs are separated from each other in terms of performance and security.

Project-based connection restriction - Long-term - Separation is strictly needed →Service order based

Task-based virtual NWs - Short-term → User oriented operation

Project A

Project B

Production company # 1 Production company # 2

Vendor 1 Vendor 4 Vendor 3 Vendor 2

Task A1

Task A2

Task B1

Task B2

vNode


NTT’s new edge device

Virtual Network Gateway – Newly developed by NTT and Fujitsu.

– Enables on-demand task NW switching service

Features :

– Connects customers’ IP NWs to the NW virtualization PF (VNODE)

– Change mappings between customers’ IP subnets (vlans) to

slices swiftly

– High performance

– Uniqueness of user terminals’ IP addresses is guaranteed

in the virtual NW space (No need to negotiate, private addresses can be used)

Virtual NW #1 (Task A1)



IP subnet (vlan)

Virtual NW platform (VNODE NW)

192.168.1.10

192.168.1.10

192.168.1.10

Uniqueness of IP addresses is guaranteed

22


Benefit : On-demand task NW switching service

Production A

…

Studio A

TV

Conference

…

Cinema

Source

Studio B

Production B

…

Production C

…

Producer B

…

Production D

…

Producer A

…

TV

Conference

…

Cinema

Source

For each task, a ‘task network’ is configured in advance using a virtual network technology.

At each location, users can switch their project NWs swiftly on-demand basis (No need to contact NTT).

-> ‘Short-term’ NW configuration.

AM PM Night AM PM Night AM PM

Producer A

Producer B

Task 1: Std A,

Production A,B

Task 1: Std A,

Production A,B Task 2: Std B,

Production A,D

Task 3: Std B,

Production C,D

Task 3: Std B,

Production C,D Task 4: Std A,

Production B,C

Network Virtualization

Platform

(IP Network)


Study on Collaborative Space with UCSD

24


How are the requirements mapped on NV platform?

25

Project basis managing

Sharing own facilities

Critical to the deadline

Isolated by slicing

Adjusted by the processing in Network

Customer control capability

(developer concept)

Requirements

NV platform


RESILIENT NETWORK


26

This work is supported by MIC.


Movable ICT resource unit

Disaster Resilient network

How can we recover from the disaster? March 11th, 2011 the great east Japan earthquake experience

raised the serious question. This projects funded by MIC (Ministry of Internal Affairs and

Commmunication) is started in this year in order to provide the solution for this problem.

One of the projects is the research and development of the fast recovery method using the movable ICT resource unit


A recovering scenario

Resource

Unit

Normal

Disaster

Recovery phase Preparation for recovering scenario

Using available resources such as WiFi

Temporal connection to up-link

Policy/Strategy available resource

Earthquake! Bringing the set of ICT resources

Fastest recovery for local communication


Optimizing The recovery process

Basic strategy of the recovery process

Minimize the physical redundancy and re-using/re-programming of ICT resources for supporting the various requirements

Logical redundancy for resilient and flexible ICT resrouces

Networking movable/temporal resources and existing resource in order to expand the coverage, resiliency, and support the operation of the recovery

Optimizing the process of the recovery

minimizing Physical redundancy

Using Virtualized network

Newtworking

IU

R

R

R

R

R R

R R F1 F2

F3 F4

F5

IU

IU IU

IU IU

IU

movable Wide area flexibility Resilient extendability timely operational Using at any time

IU: ICTユニット

ライフサイクルプロセス群

Logical Design

Physical Resources


In future, movable resource units will be connected to Vnode platform.

横須賀R&Dセンタ

Existing

Service network

ゲートウエイ

Remote sites

IU

IU

Slices for the recovery

VNode platform

Movable Resource Unit

http://www.tohoku.ac.jp/japanese/

http://www.google.co.jp/imgres?imgurl=http://special.goo.ne.jp/10th/ntt/lab/img/building.jpg&imgrefurl=http://special.goo.ne.jp/10th/ntt/lab/&usg=__91foV3cl-qihl14uzQpYxWPT4xA=&h=200&w=300&sz=53&hl=ja&start=5&zoom=1&tbnid=GVMeYjlU-dzGuM:&tbnh=77&tbnw=116&ei=TCYMT-HvG4f_mAXF4NCoBg&prev=/search?q=NTT%E6%A8%AA%E9%A0%88%E8%B3%80%E7%A0%94%E7%A9%B6%E9%96%8B%E7%99%BA%E3%82%BB%E3%83%B3%E3%82%BF%E3%80%80%E5%86%99%E7%9C%9F&hl=ja&sa=X&gbv=2&tbm=isch&prmd=ivns&itbs=1


Redundancy and Virtualization

Real Redundancy

Multiple Resources

Stocks

Stand-by system

Too much

Virtual/Logical Redundancy

ICT based

Survival tools

Self Organizing

Virtual Network Design

Recovery Scenario

Temporally Networking

Adaptive rather than redundant

Same actions

as disaster

recovery

Cloud operatoin &

Network

Virtualization

operation

Usual Situation

Redundancy should be seriously considered. Physically redundancy is not acceptable due to the cost of ownership. Can Virtually redundant system be realistic or acceptable?

31



32

Timely supporting and Pre-defined but not implementing

Not everything is normal.

Physical resources might be varied.

Preparing the specific rescue network design as the slices

(not physical redundancy but software redundancy)

Adjusting by the resource allocation

Creating/destroying networks

easily

Requirements

NV platform

Requirements are varied.


REDUNDANCY IN DATA AND SLISES


33

A part of this work is supported by NICT.


Multi-hop shared R&E networks over EU/US/Japan

1. BBC-JANET-GEANT(IP)-Internet2(IP)-GEMnet2(L3)-NHK

2. BBC-JANET-GEANT(IP)- SINET4 -GEMnet2(L3)-NHK

On-demand networking by DCN (Dynamic Circuit network)

3. BBC-JANET-GEANT(BoD)-Internet2(ION)-GEMnet2(L2)-NHK

Commercial service network (NTT Communications’ V-Link)

4. BBC-VLink-GEMnet2-NHK

(In Japan, SHV streams are distributed by IP multicasting over NTT Communications’ dedicated

lines.)

Current redundant networking for reliability

34

Internet2

GÉANT JANET

GEMnet2

SINET4 Akihabara

Fukushima

Shibuya

PV locations in JPN：NHK(NTT)

NHKSTRL

Seattle

New York

Washington DC

PV locations in UK：BBC

London

Frankfurt

Glasgow

Bradford

BBC Broadcasting House

PV location in US：NBC

NW Monitoring Point

BBC Televison Center


Congestion control

35

Re-transimission Using the another network Priority control

To achieve the reliable transmission

Copyright (C) 2012 Nippon Telegraph and Telephone Corp. 36

Another look of the congestion control

Slice1

Slice 2

・

・

・

Slice n

AGW

Distributing the sources

with Error correcting

codes Various virtual networks/slices

Dynamically creating slices

Changing the connections or

the inter-slice exchanging

Recovering at the

receiver side

Collaboration of Application and Network

Static

Redundancy

In Data

Dynamic

Redundancy

In Network



37

The different networks for off-loading

Traffic control

Creating slices using different combination of resources

(isolated slices)

Forwarding to another slice (simplified)

Creating/destroying networks

easily

Requirements

NV platform

Requirements are varied.


Summary

Operation and management should be deeply considered.

Mapping your REAL problem to a slice/slices

Deep programmable slices are good tools for collaboration!

38

network virtualization and application : a new look of networking

Documents