Open stack with_openflowsdn-torii

OpenStack with OpenFlow/SDN

Takashi Torii
NEC
Aug. 11, 2012

Page 1 © NEC Corporation 2012

INTRO - QUANTUM


What is Quantum

Quantum is an incubated
OpenStack project to provide
"network connectivity
as a service" between
interface devices (e.g.,
vNICs) managed by other
Openstack services (e.g.,
nova).

“Intro to OpenStack Quantum for Cloud
Operators”, Dan Wendlandt


How Quantum works
1. Create Network
2. Create Port
3. Plug Interface Nova VM VM
NIC NIC

Port Port
Cloud User Quantum
Network
Plugin

Attach Port
and NIC
Create Ports
Create specify
you can create network on demand, only
logical network and virtual NIC.

Quantum Plugins

Nova VM VM
NIC NIC

Port Port
Inside OpenStack
Cloud User
• Cisco UCS/Nexus Plugin (cisco) Quantum
• Quantum L2 Linux Bridge Plugin Network
(linuxbridge) Plugin
• Quantum Plugin for NVP (nicira_nvp)
• Open vSwitch Plugin (openvswitch)
• Ryu Controller Plugin (ryu)

Blueprints
• NEC OpenFlow Plugin
• Quantum plugin for bigswitch
controller
• Layer 2 Network driver for Brocade’s
Ethernet Fabric Network OS
• A Plugin for Infiniband Infrastructure


INTRO - WHAT IS
OPENFLOW/SDN


Question: How old is the Internet?
▌Answer: 40 years old!
TCP/IP borned 1970@DARPA
World Wide Web borned 1989

▌TCP/IP is long life technology

▌But, usage of the Internet has chaged in this 40 years...
Telephone by the Internet
Watching TV by the Internet
Shopping, trading, chatting, xxing, xxxing, xxxxxing...

Current Internet
New application

Gap and Inconvinient

40 years old the Internet

Future Internet
▌What is the Internet can not do?
PC : new idea or application can do by written software. Innovation!
The Internet: new functions will be implemented next renewal. Please
wait 10 years... No Innovation!

▌How to make innovative technology in the Internet?
Several project have started about 2007.
GENE@USA, FP7@EU, ...
OpenFlow born in Stanford Univ.

Keywords
▌OpenFlow
New architecture of network switching
Network virtualization and programmability

▌Network virtualization
You can create “my network”

▌Programmability
You can control network by application program

“So, what you want to do?”

Page 10 Page 10

Background of OpenFlow/SDN
▌2007: Stanford started “Clean Slate Program”
▌2009: Stanford established “Clean Slate Laboratory”
Contributed to OpenFlow Consortium to specify OpenFlow spec(v0.8.9, v1.0)
and campus trial
http://www.openflow.org

▌Mar.2011: Open Networking Foundation Founded

Industry NEC active from day #1
standard

▌May.2012: Open Networking Research Center (ONRC) established

Industry Open
Source activity
NEC Proprietary and Confidential

Open Networking Foundation
▌Established for promotion of Software Defined Networking
▌Definition of OpenFlow protocol

http://www.opennetworkingfoundation.org/

Page 12

OpenFlow Protocol Standard
▌OpenFlow Switch Specification
1.0 (2010/3)
•Mostly used version
1.1 (2011/2)
•MPLS shim header, multiple table, etc
1.2 (2011/12)
•IPv6, etc
1.3 (2012/4)
•PBB, etc
▌OF-Config
1.0 (2012/1)
1.1 (2012?)
▌OF-Test
1.0 (2012?)
http://www.openflow.org/documents/openflow-spec-v1.1.0.pdf

OPENFLOW BASICS


OpenFlow Basics: Architecture

 Separate Data Plane and Control Plane
 OpenFlow is the protocol between switch and controller
 L1-L4 field are used for switching

OpenFlow
Controller
OpenFlow Switch OpenFlow
Protocol
Secure Server
Channel
Rule Action Statistics
Rule Action Statistics
Flow Table Packet Traffic management
transfer

Page 15

OpenFlow Basics: Flow Switching

Transfer packet based on “Flow”

Current Network
Transfer packet based on L2/L3 address
L2 Switching(MAC) L3 Routing(IP) Firewall etc.

Ingress Dst Src Ether VLAN VLAN Dst Src IP IP TCP/UDP TCP/UDP
Port MAC MAC Type ID Priority IP IP Proto ToS Src Port Dst Port Data

L1 L2 L3 L4

Flow Switching

Flow is distinguished by rule of combination through L1(port), L2(MAC), L3(IP), L4(port).
Transferring method that use flow is called flow switching.

Page 16

How OpenFlow works

(1) Packet driven type [Reactive] OpenFlow
3. Route search Controller
PC
OpenFlow
Rule Switch
Action
OpenFlow
Switch 4. Set flow table

5. Packet transfer

2. Inquiry to controller

OpenFlow OpenFlow
Rule Action
Switch Rule Action
Switch 1. Pakcet receive

packet

Page 17

How OpenFlow works

(2) Flow table push type [Proactive] OpenFlow
1. Route calculate Controller
PC
OpenFlow
Rule Switch
Action
OpenFlow
Switch 2. Set flow table

4. Packet transfer

OpenFlow OpenFlow
Rule Action Rule Action
Switch Switch 3. Packet receive
packet

Page 18

Flow examples
Unicast

1.

Multicast
2.

Multipath
 Load-balancing
3.  Redundancy

Waypoints
 Middleware
 Intrusion detection
4.  …

Page 19

OpenFlow Protocol detail
▌Protocol between OpenFlow Switch and OpenFlow Controller

▌Messages
▌Flow table
▌Match
▌Action

Page 20

OpenFlow Messages
▌Packet
Packet in : switch to controller
Packet out : controller to switch

▌Flow entry
Flow mod : controller to switch
Flow removed : switch to controller (expire)

▌Management
Port status : switch to controller (port status change notify)
Echo request/reply
Features request/reply
…

Flow Table Difinition

Flow 1. Match Fields
Counters Instructions
(exact & wildcard)

Match Fields
Flow N. (exact & wildcard)
Counters Instructions

flow filter Statistics of each flow Instruction to flow
(example) (example) (example)
Port, VLAN ID, L2, L3, L4, … Packet count, byte count, Unicast, multicast, QoS, Shaping, Load
session time... Balance, Fault Recovery, tunneling ...

Page 22

Matching Filter
▌Ingress port
▌Ethernet source/destination address
▌Ethernet type
▌VLAN ID
▌VLAN priority
▌IPv4 source/destination address
▌IPv4 protocol number
▌IPv4 type of service
▌TCP/UDP source/destination port
▌ICMP type/code

12 tuple through L1 to L4 header field can be used

23

Action
▌Forward Various type of transfering rules
Physical ports (Required)
Virtual ports : All, Controller, Local, Table, IN_PORT (Required)
Virtual ports : Normal, Flood (Required)
▌Enqueue (Optional)
▌Drop (Required)
▌Modify Field (Optional)
Possible to modify header
Set/Add VLAN ID
Set VLAN priority Possible to set multi actions
Strip VLAN Header
Modify Ethernet source/destination address
Modify IPv4 source/destionation address
Modify IPv4 type of service bits
Modify IPv4 TCP/UDP source/destination port

Example of flow table

Flow switching

Key Input Port = 2 MAC SA
MAC SA = 00:00:4c:11:11:11
MAC DA = 00:00:4c:22:22:22 Flow table

MAC DA VLAN ID = 100 OpenFlow switch

TYPE = 0x0800 Proto = 6 0
IP SA = 10.20.30.40
IP DA = 10.50.60.70
Src Port = 32000 Dest Port = 80
Action 1 OUTPUT = 3 incoming output
Packet Packet


L2 switching

Key Input Port = * MAC SA
MAC SA = *
MAC DA = 00:00:4c:22:22:22 Flow table

MAC DA VLAN ID = * OpenFlow switch

TYPE = * Proto = * 0
IP SA = *
IP DA = *
Src Port = * Dest Port = *
Action 1 OUTPUT = 3 incoming output
Packet Packet


Broadcast

MAC SA = *
MAC DA = FF:FF:FF:FF:FF:FF Flow table


IP SA = *
IP DA = *
output output
Src Port = * Dest Port = * Packet
output
output
Packet Packet
OUTPUT = FLOOD output
Packet
Action 1 output
Packet
Packet
incoming
Packet


multicast

Key Input Port = 1 MAC SA
MAC SA = *
MAC DA = * Flow table


TYPE = 0x0800 Proto = * 0
IP SA = *
IP DA = 224.10.10.1
Action 1 SET_DL_SRC = 02:00:4c:00:00:01 Incoming Output Output
Packet Packet packet
Action 2 OUTPUT = 3
Action 3 SET_DL_SRC = 02:00:4c:00:00:02
Action 4 OUTPUT = 5


IP Routing

MAC SA = *
MAC DA = * Flow table


IP SA = *
IP DA = 10.20.30.40
Action 1 OUTPUT = 3 Incoming Output
Packet Packet

Network virtualization in Data Center

1. Interconnect VM and virtual network 2. Traffic isolation between virtual network
VM VM
Software Software
Switch Virtual Network A Switch

VM VM

Physical
Virtual Network B
Network

VM VM
Software Software
Switch
Virtual Network C Switch

VM VM

3. Physical resource management

VLAN
Current technology: VLAN

VM VLAN A VLAN A VM
2. Max VLAN
Software 4K Problem Software
Switch Switch

VLAN B VLAN B
VM VM
VLAN A
Physical
VLAN B
1. Configuration frequently Network
VLAN C
VM VLAN B VLAN B VM
Software Software
Switch Switch

VLAN C 3. Limit of STP C
VLAN
VM VM

OpenFlow with Overlay type

VM VM
OpenFlow 2. Traffic isolation by tunneling
OpenFlow
Switch Switch

VM VM

Physical
Network
1. OpenFlow set relation between VM
VM and tunnel VM
OpenFlow OpenFlow
Switch Switch

VM VM

OpenFlow with Hop-by-Hop type

VM 2. Flow based switching and VM
traffic management
OpenFlow OpenFlow
Switch Switch

VM VM

OpenFlow
Switches
1. OpenFlow set relation between VM
VM and flow VM
OpenFlow OpenFlow
Switch Switch

VM VM
3. Shortest path by each flow

Hop-by-Hop implement example – Trema/SliceableSwitch

3. Check the ingress and egress belong to same slice.

slice
2. Search flow table by
4. Calculate the shortest path
DMAC to get egress switch
and port Sliceable Switch
fdb Trema
topology

1. packet_in 6. packet_out
5. flow_mod

Controller dicide the shortest path by each flow and construct the total path.

Variation of OpenFlow switch implementation
▌L2 switch base
Firmware update with commodity L2 switch
Instruct L2 through L4 header
NEC, HP, Juniper, Quanta, Arista ...

▌Software switch
Implement OpenFlow switch inside host
Open vSwitch, Stanford Reference Switch ...

▌Transport node base
Path can be configured by OpenFlow protocol
Cienna, Fujitsu America ...

▌Wireless
WiFi-AP or WiMAX-BS/ASNGW that can handle OpenFlow

OpenFlow Controller (1/2)
▌OSS
NOX
POX
SNAC
Trema
Beacon,
Floodlight
Ryu, Node Flow, Flow ER, Nettle, Mirage, ovs-controller,
Maestro

https://events.linuxfoundation.org/images/stories/pdf/lcjp2012_yamahata_openflow.pdf

Page 36

OpenFlow Controller (2/2)
▌Products available
Nicira: NVP Network Virtualization Platform
BigSwitch: Floodlight based?
Midokura: Midonet
NTT Data:
Travelping: FlowER based
NEC: ProgrammableFlow

Page 37

WHY OPENFLOW/SDN?


Network is complicated!
“To support a cloud infrastructure, in reality all aspects of the IT
infrastructure must be cloud-enabled, including storage, software, and –
importantly – networking. Legacy network architectures are designed to
support static network configurations and often do not provide the
flexibility required to support cloud and data center deployments.”

Rohit Mehra, IDC
January 2012


Challenges of Managing a Data Center Network

Has your organization experienced any of the following network
operations problems?
Too many manual processes 40%

Difficulties/delays associated with change and/or configuration
management 36%

Integration and cooperation between network operations and 34%
other IT domains
Inability to implement new technology in a timely manner due to 29%
lack of maintenance windows
▌ Automation
Difficulties and/or delays in provisioning network devices such as 28%
▌ Agility
servers, switches, and security appliances
26% ▌ Integration
Inability to implement new technology due to poor coordination
between IT administration teams ▌ Maintainable
26%
Manual IP address management using tools like spreadsheets
We have a heterogeneous network where different technical 23%
elements need their own network operations
20%
Limited skills in the networking team
Too many tools 17%
We have not experienced any network operations problems
7% Percent of respondents (N=280,
multiple responses accepted)
© 2011 Enterprise Strategy Group

Network Not Keeping Pace with Server Virtualization

▌Many protocols to solve Distributed Complexity
performance and scalability • BGP • OSPF
requirements • IGMP • Trill
▌Vendor-specific configurations • ICMP • IP

▌Software rollouts frequent
Manually
Experts Configure

▌Switch-by-switch configuration
management Distributed Vendor
Control Proprietary
• RIP • IS-IS
• VLANs • IPsec
• UDP • TCP

Server virtualization needs an open, agile network

FAQ: Why OpenFlow?
▌Benefit ?
▌Risk?
▌New technology?
▌Applications?
▌Potential?
▌Open?

▌Let’s see the history of IT system.


Before Virtualization: BV
▌Management of servers and networks are fully separated.
▌There are some difficult problem, for example virtual IP address management

SV SV SV SV SV SV SV SV

L2 Switch L2 Switch

Router

Page 43

BV: Firewall, LoadBalance
▌Switch and routers are redundant
▌Firewall or loadbalancer are specialized hardware and clusterd


L2 Switch
L2 Switch L2 Switch
L2 Switch

LB LB LB LB

L2 Switch L2 Switch L2 Switch L2 Switch

FW FW FW FW

Router(L3 Switch)
Page 44

VLAN appears
▌VLAN can separate subnet
▌number of switch port grows, resouce utilization is improved
▌Multiple subnets can consolidate on same switch.
▌But routing is interchanged by router.


VLAN VLAN
L2 Switch
L2 Switch L2 Switch
L2 Switch

LB LB LB LB


FW FW FW FW

Router(L3 Switch)
Page 45

Extension of VLAN
▌VLAN can be created crossing router.
▌Because subnet can cross router, consistent configurations are necessary


L2 Switch
L2 Switch L2 Switch
L2 Switch

LB LB LB LB


FW FW FW FW

Router(L3 Switch)
Page 46

Hypervisor appears
▌Virtual machine appears
▌It is impossible to manage by human!
▌LB or FW can be Virtual Appliance

VM VM VM VM VM VM LB LB FW VM VM VM VM VM VM VM VM VM VM VM VM VM

HyperVisor HyperVisor HV HV HyperVisor HyperVisor HV HV


L2 Switch
L2 Switch L2 Switch
L2 Switch

LB LB LB LB


FW FW FW FW

Router(L3 Switch)
Page 47

vswitch appears
▌trafic inside server can not manageable and complicated
▌separation between server and network become cloudy


VLAN
Virtual Switch Virtual Switch VS VS Virtual Switch Virtual Switch VS VS



Switch Switch

R

Live Migration
▌Live Migration appears, VM can migrate between servers without stop or suspend.
▌VLAN must follow VM migration
▌Resource management became on-demand, VLAN configuration change is more
frequently, inventory control of resources is more important.
▌Automation of resource management is desired, not only server resources, but also
network resources.


VLAN


Switch Switch
VLAN

R

Page 49

Virtual appliances
▌Virtual appliance appears, traffic route is more complicated.
▌In past days, Firewall and Load Balancer are managed by network side, but virtual appliances
belong to server side.

In virtualization era, data center operators face various problems
not only server/storage side but also network side.


VLAN


Switch Switch
VLAN

R

Page 50

Now: Server and Network integrated management

Border of Server and Network is not clear.
OpenFlow/SDN can be lead of Server and Network integrated management.

Server Server
AP AP Server Management
Before
Virtualization
Border

L2/L3 SW L2/L3 SW Network Management

Overlap of Server and
Server Server Network Management

AP AP AP AP AP AP
Integrated
Virtualized VM VM VM VM VM VM Server Management
vSwitch vSwitch
Network OpenFlow
Management
L2/L3 SW L2/L3 SW

Page 51

OpenFlow Controller Framework

TREMA


OpenFlow Programmability
▌OpenFlow Controller software can manage networks
▌There are various control methods
HPC
•Like traditional interconnect
Distributed computing
•Try to use real network instead of overlay
IT and Network integrated management
•Authentication, security, operation..

“OpenFlow is just one of the tools” -
Ivan Pepelnjak

Trema: Full-Stack OpenFlow Framework for Ruby/C
▌A software platform for OpenFlow Trema @http://trema.github.com/trema/
Controller developers

▌EASY
All-in-one package
Integrated developing environment
Sophisticated APIs for Ruby and C
▌Many sample controllers/parts
Useful samples @/src/examples/
Practical samples @TremaApps
TremaApps
▌Fully tested and supported @https://github.com/trema/apps

▌Open community
Free software (GPLv2)
Community participation (even for commercial product)

Page 54

Scope of Trema
▌Trema = OpenFlow framework
= controller platform + integrated network emulator +
debugger + etc…
▌Why framework? - Tight loop of "coding, testing, and debugging“
results high productivity
Routing control, topology discovery,
Authentication-driven application

OpenFlow TremaApps
User module User module User module Controller
Core modules Trema
Basic libraries OpenFlow protocol stack Interactive
Shell

Debugger
OpenFlow Integrated
Switch Controller and
network network
Host emulator configuration

Real network
Page 55

Lessons learned

OpenFlow iceberg

Controller development
Scope

Debug Debug
Debug Debug

Network setup

Traffic generation
Seamless integration of
operations and state
Diagnose monitoring among
controller applications,
switches, hosts, etc.

What is Trema

User application OpenFlow
Your OpenFlow controller (in Ruby or C)
controller
Abstraction mechanisms, and
high-level APIs

Core:
OpenFlow controller libraries and modules

Trema Developing environment:
Network/host emulator, debugging tool, etc

Operation environment:
trema commands
Trema is “OpenFlow programming framework”
for Ruby and C (GPL2)

Feature 1: easy coding

Repeater hub written by Ruby
class RepeaterHub < Controller
def packet_in datapath_id, message
send_flow_mod_add(
datapath_id, Send flow entry add
:match => ExactMatch.from( message ),
:actions => ActionOutput.new( OFPP_FLOOD )
)
send_packet_out(
datapath_id,
:packet_in => message, Packet out
:actions => ActionOutput.new( OFPP_FLOOD )
)
end
end

Page 58

Feature 2: network emulator

▌“code, test, debug” in one machine

Emulation script Development machine
vswitch("sw1") {
datapath_id "0x1"
} My Controller
vswitch("sw2") { Trema
datapath_id "0x2"
} Secure Channel

vhost ("host1") vswitch(sw1) vswitch(sw2)
vhost ("host2")
vhost(host1) vhost(host2)
link "host1", "sw1"
link "sw1", "sw2"
link "host2", "sw2"

Feature 3: many sample applications
▌Trema source tree
Repeater hub
Learning switch
Traffic monitor

▌Trema application repository https://github.com/trema/apps
Topology discovery/management
Routing switch
Sliceable Switch

▌Documents published
http://gihyo.jp/dev/serial/01/openflow_sd/0010

Page 60

SOLUTIONS


Our activities around OpenFlow/SDN and OpenStack

Distributed
Controller Data Center
Framework Telecom
[Trema] System

OpenStack
OpenFlow/SDN
Cloud Platform
OpenFlow
Product
[Programmable
Flow] Storage Orchestration
BigData PDCA Lifecycle


Award-winning ProgrammableFlow
Simple, scalable, secure, open networking
▌First OpenFlow-enabled fabric
▌Secure network-wide virtualization
▌Drag and drop, programmable networking
ProgrammableFlow ProgrammableFlow
Controller Switch Family

Quantum OpenFlow Plugin

▌ OpenStack Quantum
OpenStack sub-project Nova
Managing virtual network
Quantum
OSS Released
▌ OpenFlow Plugin
OpenFlow Plugin
The plugin to use OpenFlow from Quantum
Download from https://github.com/nec-
openstack/quantum-openflow-plugin
OpenFlow
Controller
▌ Supported OpenFlow Controller platform （PFC/Trema）

Trema http://trema.github.com/trema/ Flow setting
ProgrammableFlow PF6800
VTN1 OpenFlow
VTN2 Switches
VTN3
VTN4

Page 64

Isolation of networks
▌SliceableSwitch (trema application)
Create virtual L2 slice on OpenFlow NW
L1-L4 filter function enabled

OpenFlow Switch

OpenFlow based Firewall / Load Balancer

Not OpenFlow OpenFlow based
The Internet The Internet
Router OFS
Firewall OFC

FW LB OFC

OFS
LB

FW or LB appliance is high Without appliance equipment
cost

Page 66

Integrated resource management

▌IT and network resource integrated management
OpenFlow for network resource virtualization
OpenStack for computing resource virtualization
Management user portal:
-Create multiple VMs and virtual networks
Original Portal -Attach VM to network
100% Open Source Software!

OpenStack

System management Quantum Plug-in

Row: virtual machines
Column: virtual networks
OpenFlow Controller SliceableSwitch
Trema

VM
VM VM VM
KVM
Check box on a intersection:
KVM Binding of VM and network
Open vSwitch

Enabling flexible service provisioning
OpenFlow switch and agile service deployment


Virtualization of mobile core and dynamic SDN control
New project with NTT DoCoMo to make a mobile core network flexible
and scalable against network congestions due to disaster
Virtualization of mobile core network services and dynamic server resource
re-allocation for high priority service (Voice/Mail).
Central Office Central office
High priority Low priority High priority Rich
Voice/Mail Rich content Voice/Mail Content

Dynamic SDN Control OpenFlow Dynamic SDN Control OpenFlow
network network
Change Failure
resource
allocation
Failure

According to network resource re-allocation for high priority service (Voice/Mail), mobile
access network path can be dynamically adjusted.

Issues in Mobile Networks
▌Voice traffic congestion during 3.11 disaster
▌Congestion due to popularity of smart phones
▌Now, control plane signaling will also increase

Smart phones cause spike Design to allocate fixed resources
in network traffic each peak is a waste of money

High-load states
Traffic rate
occur periodically

Time
13:00 20:00 13:00 20:00


Solution
▐ Dynamic allocation of mobile network resources to solve
various network congestions due to
 bursty traffic patterns of smart phones
 immediate increase of traffic patterns due to disaster
Allocating resources to prioritized services
Voice Email Music Video File
Normal
Rich media
Allocation is changed Emergency communication
from normal to communications
emergency

Emergency


Resource Allocation Control for Inter Central Office
Dynamic resource allocation of virtualized software within Inter central office

before after
Site2

SIP email M2M Movie
Site4 Site3
SIP email Packet Packet
VMVM VM
VM VMVM VMVM SIP email M2M Movie SIP email M2M Movie
Real resource Packet Paket SIP SIP SIP SIP Packet Packet
VMVM VM
VM VMVM VMVM VM VM VM VM
VM VM VM VM
Network Real resource Real resource
Site1
Resource sharing among
Congestion SIP email M2M Movie Network distributed sites
SIP email M2M Packet
VM VM VM VM Site2
VM VM VM VM Site1
Real resource SIP SIP SIP Packet SIP email M2M Movie

Site1 SIP SIP SIP Packet SIP SIP Packet Packet
VM VM VM VM VMVM VMVM VMVM VMVM
Congestion VM VM VM VM
SIP email M2M Movie
Real resource Real resource
SIP SIP SIP Packet
VMVM VMVM VMVM VMVM

Real resource
Resources shortage cannot be compensated Resources shortage can be dynamically
from remote central office compensated from remote central office


Hybrid Cloud

Demonstration at the Interop TOKYO, June 2012

SDN for private clouds SDN for public clouds
WebSAM and ProgrammableFlow OpenStack and ProgrammableFlow

Cloud Manager Cloud Manager

Enterprise/ IaaS
Service users IaaS operator Operator
Centralized Centralized
Virtual server Virtual server
controller controller
／Trema

Network pool Server pool Network pool Server pool

Resource
IaaS Programmable Load Programmable
Firewall Server Storage Server Storage
Manager Flow switch Balancer Flow switch

NEC original solutions for sophisticated IaaS operators with their customizations
Enterprise users and IaaS operators
Page 72

Security
▌Quantum extension for network filtering
▌Filtering and detecting packet between VMs

Internet Internet

NAT / Gateway NAT / Gateway

Firewall Firewall

Virtualized Network Virtualized Network

VM VM VM VM VM VM

Bare metal support
▌OpenStack bare metal with network isolation
OpenFlow switch can isolate network
security function by OpenFlow
open vSwitch
OpenStack
provisioning
VM
Nova hv
VM OpenFlow
Network

Physical Server

• Network Isolation
Quantum plugin
OpenFlow • Firewall
Controller • Avoid MAC arrogation

Contribution to OpenStack community
OpenFlow Plugin target Folsom-3
Quantum other features


Why OSS?

▌Vender’s products are like “Tower”

▌OSS is like “City”

Tokyo SkyTree, 634m


How to make Innovations?
▌Use potentially technology/platform

▌Open

▌Collaboration

OpenStack and OpenFlow

Thank you!
Contact : t-torii@ce.jp.nec.com


Open stack with_openflowsdn-torii

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (9)

Semelhante a Open stack with_openflowsdn-torii

Semelhante a Open stack with_openflowsdn-torii (20)

Mais de Hui Cheng

Mais de Hui Cheng (20)

Último

Último (20)

Open stack with_openflowsdn-torii