The document discusses Neutron and SDN (Software Defined Networking) as solutions to problems with managing complex and dynamic data center networks. Neutron is OpenStack's networking component, which uses SDN approaches like OpenFlow to provide logical network abstractions and flexible virtual network configuration. SDN allows network policies to be programmed centrally and automated, improving network provisioning, management, and response to failures or changes. When combined with Neutron and an SDN controller like OpenDaylight, this enables on-demand, software-defined network services for OpenStack clouds.

1. Neutron

2. and

3. SDN

4.
[

5. 따로

6. 똑같이...

7. 같이

8. 걸을까...

9. ]
Yongyoon.

10. SHIN

11.
SDN

12. Section,

13. ETRI

14.
http://uni2u.tistory.com

15.
Facebook:

16. uni2u

17. Let’s

18. Together
• Data Center Network
• OpenStack Neutron
• Software Defined Network

19. Data

20. Center

21. Network
• Provides a logical network abstraction on top of a
physical network
Hypervisor A Hypervisor B
VM VM VM
VM VM VM
Physical Network View
VM
VM VM
Logical
Switch
Logical
Switch
Logical
Switch
Logical
Router
Logical
Switch
VM
VM VM
Logical Network View

22. Network is
Complex

23. 변화무쌍한

24. 네트워크
• 사용자의 요구에 따라서
• 사용자 마음껏 생성
• 네트워크를 잘 모르는 사용자도 가상 네트워크를 생성
• 네트워크 구성은 구글링으로 생성
• 같은 네트워크 사용할 위험성
• 네트워크 관리자는
• 사용자가 요구한 네트워크를 즉각 만들어야 함
• 독립적 네트워크를 구성하여야 함

25. Network has a
Problem

26. 알아서

27. 문제를

28. 해결하는

29. 네트워크
• 네트워크에 문제가 발생하면
• 알아서 수정하고 적용하여야 함
• 네트워크 관리자에게 알림을 보내줘야 함
• 기계적으로 처리가 되어야 함
• 이미 완성된 네트워크를 수정한다는 것은
• 매우 어려운 일
• 매우 지루한 일
• 실수가 발생되기 쉬운 일

30. Change the Network
Dangerous

31. Data

32. Center

33. network

34. needs
• Easy
• Network management
• Speed
• Network create/update/delete
• Traffic
• Safety
• Total Network Management
• Virtual, Physical Network Management

35. Neutron
SDN

36. OpenStack

37. Neutron
“OpenStack이 대세... 그런데 네트워크 쪽은... 2% 아쉽기도...”
“왜 ERROR는 다 네트워크냐... 안되면 전부 Network...”

38. quantum neutronneutron

40. http://www.openstack.org

41. http://www.openstack.org

43. Currently

44. problems

45. in

46. Neutron
• All inter subnet traffic goes through the network
Node
• different subnet connected by vRouter
(NetworkNode)
• OpenStack use Network Agent
• Process based
• Network Scalability
• use so many solutions
• add on other opensource

48. OpenStack

49. DVR
• Distribute Virtual Router
• using L3 Agent on Compute Node

50. OpenStack

51. Network
• WE Traffic (West-East)

52. OpenStack

53. Network
• SN Traffic (South-North)

54. OpenFlow
“제어/데이터 평면이 어쩌구... 저쩌구...”

55. http://www.sdncentral.com
SDN Architecture
NB API
SB API OpenFlow

56. OpenFlow

57. Protocol
Classifier Action
Modify Field
Enqueue
Forward
NORMAL
FLOOD
Virtual Port
Physical Port
Forward
Mandatory Action
Optional Action
Statistics
Classifier Action Statistics
Classifier Action Statistics
Classifier Action Statistics
…
Flow Table
OF1.0 style
Ingress
Port
Ethernet
SA DA Type
IP
SA DA Proto
TCP/UDP
Src
VLAN
ID Priority TOS Dst
Virtual Port
ALL
CONTROLLER
LOCAL
TABLE
IN_PORT
Drop
Header Fields
Actions

58. SDN
“SDN이라고 여기저기서 이야기 하는데... 새롭지는 않고...”
“종류도 많고... 다 되는건가?”

59. ml2

60. mechanism

61. driver
Type Drivers Mechanism Drivers
GRE
VXLAN
VLAN
Arista
CISCONexus
OpenvSwitch
OpenDaylight
ONOS
LinuxBridge

62. King

63. of

64. SDN

65. Controller
“OpenDaylight is a highly available, modular, extensible,
scalable and multi-protocol controller infrastructure built
for SDN deployments on modern heterogeneous multi-
vendor networks. ”

66. Platinum : 8
Gold : 1
Silver : 41

68. OpenDaylight

69. case
OpenStack Control Node
OpenStack Compute Node
OpenStack Compute NodeOpenDaylight Controller
Neutron Interface
OF Network
OF Switch (OVS)
VM1 VM2
OF Switch (OVS)
VM1 VM2
OVSDB
OVSDB
OF Plugin
VTN Manager
OVSDB Plugin
ML2 Driver
port mapping
OF Message
Interface Creation Noti

70. Rising

71. Star
“ONOS stands for Open Network Operating System. ONOS provides the
control plane for a software-defined network (SDN), managing
network components such as switches and links, and running a variety
of applications which provide communication services to end hosts and
neighboring networks.”

75. When

76. sDN

77. met

78. Neutron
“Everything is same?”
+ = ?

79. Data

81. OpenStack Compute Node
VM1 VM2
OpenStack Compute Node
VM1 VM2
OpenStack Network Node
SDN Controller
OF NetworkOF Switch (OVS)
ex
ex
ex
OF Switch (OVS)
OF Switch (OVS)

82. {
networks: [
{
status: ACTIVE,
subnets: [
54d6f61d-db07-451c-9ab3-b9609b6b6f0b
],
name: private-network,
provider:physical_network: null,
admin_state_up: true,
tenant_id: 4fd44f30292945e481c7b8a0c8908869,
provider:network_type: local,
router:external: true,
shared: true,
id: d32019d3-bc6e-4319-9c1d-6722fc136a22,
provider:segmentation_id: null
},
{
status: ACTIVE,
subnets: [
08eae331-0402-425a-923c-34f7cfe39c1b
],
name: private,
provider:physical_network: null,
admin_state_up: true,
tenant_id: 26a7980765d0414dbc1fc1f88cdb7e6e,
provider:network_type: local,
router:external: true,
shared: true,
id: db193ab3-96e3-4cb3-8fc5-05f4296d0324,
provider:segmentation_id: null
}
]
}
create Network

83. {
subnets: [
{
name: private-subnet,
enable_dhcp: true,
network_id: db193ab3-96e3-4cb3-8fc5-05f4296d0324,
tenant_id: 26a7980765d0414dbc1fc1f88cdb7e6e,
dns_nameservers: [],
allocation_pools: [
{
start: 10.0.0.2,
end: 10.0.0.254
}
],
host_routes: [],
ip_version: 4,
gateway_ip: 10.0.0.1,
cidr: 10.0.0.0/24,
id: 08eae331-0402-425a-923c-34f7cfe39c1b
}
]
}
create Subnet

84. {
ports: [
{
status: ACTIVE,
binding:host_id: devstack,
name: ,
allowed_address_pairs: [],
admin_state_up: true,
network_id: 70c1db1f-b701-45bd-96e0-a313ee3430b3,
tenant_id: ,
extra_dhcp_opts: [],
binding:vif_details: {
port_filter: true,
ovs_hybrid_plug: true
},
binding:vif_type: ovs,
device_owner: network:router_gateway,
mac_address: fa:16:3e:58:42:ed,
binding:profile: {},
binding:vnic_type: normal,
fixed_ips: [
{
subnet_id: 008ba151-0b8c-4a67-98b5-0d2b87666062,
ip_address: 172.24.4.2
}
],
id: d80b1a3b-4fc1-49f3-952e-1e2ab7081d8b,
security_groups: [],
device_id: 9ae135f4-b6e0-4dad-9e91-3c223e385824
}
]
}
create Port

85. {
switchlist: [
{
dpid: 00:00:00:02:c2:f8:00:00
},
{
dpid: 00:00:10:6f:3f:e7:bb:aa
}
],
hostlist: [
{
host_ip: 10.0.10.31,
host_name: compute01,
mac: 00:0a:cd:25:c7:f3,
connected_sw: 00:00:00:02:c2:f8:e4:5a,
connected_port: 2
},
{
host_ip: 10.0.10.21,
host_name: networknode,
mac: 00:0a:cd:25:c6:69,
connected_sw: 00:00:10:6f:3f:e7:bb:aa,
connected_port: 1
}
],
Topology
linklist: [
{
src_sw: 00:00:10:6f:3f:e7:bb:aa,
src_port: 2,
dst_sw: 00:c0:34:64:a9:5a:d5:c0,
dst_port: 18
},
{
src_sw: 00:00:00:02:c2:f8:00:00,
src_port: 5,
dst_sw: 00:00:08:9e:01:a8:01:58,
dst_port: 13
}
],
vmlist: [
{
vm_id: 1e262d23-94b3-40ba-820e-6195559e1369,
connected_host: compute02,
connected_mac: 00:0a:cd:25:c7:e5,
vnics: [
{
mac: FA:16:3E:17:DD:18,
vm_ip: 70.0.0.7,
tenant_id: 34c0ae0cc37b43989a4ec654cfca5ccd,
network_id: 48951b0c-e2e8-4961-82af-8ea1ebb219dc,
subnet_id: c5cbb237-a803-46ca-b51e-ca6e04219f4d,
port_id: 3de9a799-0dee-4343-8e80-9cc9342c94a7
}
]
}
]
}

87. VM1
SDN Controller
Make Flow Rule
VM2

88. Make Flow Rule
VM2
VM1
SDN Controller
Added Host
VM3
Make Flow Rule

89. Make Flow Rule
VM2
VM1
SDN Controller
Move Host
VM2
Make Flow Rule
if not SDN

90. Make Flow Rule
VM2
VM1
SDN Controller
Move Host
VM2
Make Flow Rule
X
X
X
Link Fail
Make Flow Rule

91. DC A
VM VM
DC B
VM VM
DC C
VM VM
SDN
Controller
SDN
Controller
SDN
Controller
SDN Controller
OF Network
OF Network
OF Network
Hierarchy Controller
like a OF SW

92. VM
VM
SDN Controller
SDN Controller
SDN Controller
SDN Controller
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
VM
increase explosion VM
Scale-up Controller

94. Thank

95. You