19. セキュアチャンネルでコントローラとスイッチを接続
抜粋
The switch must be able to establish communication with a controller
at a user-con?gurable (but otherwise ?xed) IP address, using a user-
speci?ed port. If the switch knows the IP address of the controller,
the switch initiates a standard TLS or TCP connection to the
controller.
出典:OpenFlow Switch Speci?cation version 1.3.0
1 2 3
OpenFlow
コントローラ
tcp://192.168.2.102:6379
!19
20. セキュアチャンネルでコントローラとスイッチを接続
A typical OpenFlow controller manages multiple OpenFlow
channels, each one to a different OpenFlow switch. An OpenFlow
switch may have one OpenFlow channel to a single controller, or
multiple channels for reliability, each to a different controller.
1 2 3
OpenFlow
コントローラ2
OpenFlow
コントローラ1
1 2 3
出典:OpenFlow Switch Speci?cation version 1.3.0
複数コントローラ、スイッチの構成も可能
!20
21. OpenFlowバージョンの確認
When an OpenFlow connection is ?rst established, each side of the
connection must immediately send an OFPT_HELLO message with
the version ?eld set to the highest OpenFlow protocol version
supported by the sender.
出典:OpenFlow Switch Speci?cation version 1.3.0
1 2 3
OpenFlow
コントローラ
バージョン
1.3
バージョン
1.3
サポートしてる最新のバージョンを教えあう
!21
22. スイッチの情報の確認
Features: The controller may request the capabilities of a switch by
sending a features request; the switch must respond with a features
reply that speci?es the capabilities of the switch. This is commonly
performed upon establishment of the OpenFlow channel.
出典:OpenFlow Switch Speci?cation version 1.3.0
1 2 3
OpenFlow
コントローラ
FEATURE_REQUEST
FEATURE_REPLY
? Datapath ID
? ポートの一覧など
Datapath?
スイッチとかブリッジと同じと思ってください
!22
23. パケットの受信
When packets are received by the datapath and sent to the
controller, they use the OFPT_PACKET_IN message:
出典:OpenFlow Switch Speci?cation version 1.3.0
1 2 3
OpenFlow
コントローラ
PACKET_IN
? data?…?パケットの中身
? reason?…?なんでpacket_inしたか
? match?…?どのポートから入ったのかなど
? cookie?…?フロー毎につけられるIDのようなもの
!23
29. metadata=0x700000000000001/0xff0000007fffffff
value mask
64ビットのレジスタ
metadata & mask == value
Pipeline processing instructions allow packets to be sent to
subsequent tables for further processing and allow
information, in the form of metadata, to be communicated
between tables.
!29
metadata
出典:OpenFlow Switch Speci?cation version 1.3.0
35. What is OpenVNet?
? Spin-off project from Wakame-vdc
? 5 developers
? 2279 commits
? Written in Ruby
? 16512 LOCs (5257 LOCs test codes)
? Started March 2013
35
36. Why OpenVNet?
? There are many products offering network virtualization
but not free
? Is there any product to freely try out network
virtualization?
? Wakame-vdc offers network virtualization
? Extract virtual network functionality from Wakame-vdc to
make an independent package
36
37. Advantages of OpenVNet
? Users can create complex networks on top of OpenVNet
? Keep the physical networks simple
Reduce the maintaining cost of the physical networks
? Edge-overlay architecture enables creating complex multi-tenant
networks
No need expensive network switches
? e.g.) quickly preparing an isolated network for experiment
Freely and easily create/destroy networks
37
39. Network model of datacenter
Internet
Datacenter
network
Physical/Virtual server clusters
DNAT / LB
SNAT
DHCP
DNS
39
40. Deployment of agent program
Internet
Datacenter
network
Physical/Virtual server clusters
DNAT / LB
SNAT
DHCP
DNS
Deploy agents for
packet control
agent agent agent
agent agent agent
40
43. Components of OpenVNet
vna (virtual network agent)
vnmgr (virtual network manager)
vnapi (virtual network API)
Agent
other
components
? Con?gure OpenvSwitch (version 1.10.0)
? Include an OpenFlow controller implemented with Trema-edge
? Manage the datacenter network
? Provide database access back-ended by MySQL
? Command vna to do some speci?c actions e.g.) update ?ows
? WebAPI to talk to vnmgr
vnctl (virtual network controller)
? Command line interface to use vnapi
43
44. Network model of datacenter
Internet
Datacenter
network
External network
WAN edge network
Datacenter
physical network
LAN edge network
Physical/Virtual server clusters
General
servers
Appliance
servers
Storage
servers
Resources
DNAT / LB
SNAT
DHCP
DNS
44
45. Deployment
External network
WAN edge network
Datacenter
physical network
LAN edge network
General
servers
Appliance
servers
Storage
servers
Resources
Open
vSwitch
eth0 eth1
VM
vna
Open
vSwitch
eth0 eth1
VM
vna
public line
management line
A dedicated line for management
Packets for the service go through
the public line
45