Softening the Network: Virtualization s Final Frontier

Transcription

1 Softening the Network: Virtualization s Final Frontier Steve Riley Technical Director, Office of the CTO Riverbed Technology steve.riley@riverbed.com

2 Abstractions We ve Seen

3 virtual memory

4 virtual disk volumes

5 virtual machines

6 the illusion of a thing

7 abstraction

8 no re- programming

9 sometimes is disruptive

10 VM- 1 VM- 3 VM- 1 VM- 3 VM- 2 VM- 4 VM- 2 PM- 1 PM- 2

11 meets needs

12 provisioning

13 moving

14 snapshotting

15 roll back

16 New?

17 crude 1.A 1.B 1.C 2.A 2.B 2.C

18 less crude 1.A 1.B 1.C 2.A 2.B 2.C

19 less crude 1.A 1.B 1.C 2.A 2.B 2.C 1.D 2.D

20 limitations

21 n <

22 topology

23 static

24 interesting 1.A 1.B 1.C 10.M

25 interesting + 1.A 1.B 1.C 2.A 2.B 2.C 10.M

26 interesting +? 1.A 1.B 1.C 2.A 2.B 2.C 10.M

27 interesting +?? 1.A 1.B 1.C 2.A 2.B 2.C 1.D 2.D 10.M

28 interesting +!!! 1.A 1.B 1.C 1.E 1.F 2.A 2.B 2.C 2.E 2.F 2.G 1.D 2.D 1.G 2.H 2.I 10.M 10.N

29 insane ;) 1.A 1.B 1.C 1.E 1.F 2.A 2.B 2.C 2.E 2.F 2.G 1.D 2.D 1.G 2.H 2.I 10.M 10.N

30 limitations

31 as before

32 + not cloudable

33 operational abstractions aren t useful

34 VM- 1 VM- 3 VM- 1 VM- 3 VM- 2 VM- 4 VM- 2 MAC? IP? ACL? state? PM- 1 PM- 2

35 control f o r w a r d i n g

36 limitations

37 topology mandates/constraints

38 no overlapped addresses

39 sloooooow to change

40 + not cloudable

41 requirements

42 decouple V from P

43 V looks like P

44 V allows units of operation

45 Software Defined Networking (*) * One popular, but not necessarily universal, definition

46 control f o r w a r d i n g

47 control f o r w a r d i n g

48 application application application application application tier network network tier

49 application application application application application tier control platform control plane OpenFlow forwarding plane

50 forwarding plane

51 relatively dumb

52 does what it s told

53 R.I.P., RIP OSPF IS- IS &c.

54 control plane

55 centralized

56 end- t0- end view (not hop- by- hop)

57 programmable

58 naturally multitenant

59 maintains state

60 that s it?

61 virtual server virtual network

62 Virtual server Datapath CPU memory device I/O nanosecond operation Consistency self- contained Virtual network address contexts all- port knowledge N instances of N states consistency on all paths timely distribution

63 Virtual server Datapath CPU memory device I/O nanosecond operation = complexity at speed Consistency self- contained Virtual network address contexts all- port knowledge N instances of N states consistency on all paths timely distribution = complexity at scale

64 The Virtual Network

65 decoupled from h/w

66 independent from others

67 delegated control

68 ephemeral

69 SDN (*) is a useful tool * As defined previously

70 API API API API VXLAN NVGRE NVP OTV STT x86 x86 x86 x86 control plane OpenFlow forwarding plane

71 (

72 is SDN (*) a requirement? * As defined previously

73 API API VXLAN NVGRE x86 x86 x86 x86 control plane OpenFlow multicast forwarding plane

74 )

75 How does Alice talk to Bob? API x86 x86 x86 x86 vapi : I need a virtual L2- L3 network with these properties vswitches in x86 boxes determine optimal path OPENFLOW: Hardware, plumb the following

76 Alice VM PM- A Bob VM PM- B x86 x86 x86 x86

77 E V I L

78 one flow, two VMs, separate hypervisors Throughput Recv CPU Send CPU Linux bridge 9.3 Gbps 85% 75% OVS bridge 9.4 Gbps 82% 70% OVS- STT 9.5 Gbps 70% 70% OVS- GRE 2.3 Gbps 75% 97% aggregate, four VMs, two hypervisors Throughput CPU OVS bridge 18.4 Gbps 150% OVS- STT 18.5 Gbps 120% OVS- GRE 2.3 Gbps 150% overhead- of- software- tunneling/

79 possibilities

80 security application

81 QoS application

82 WAN op application (*) * hard: distributed cache and symbol vocabulary

83 on- demand VPN/C

84 infrastructure code

85 network code

86 decoupled and delegated

87 physical L2- L3

88 logical L2- L3 L4- L7 services x86

89 x86, really?

90 complex much CPU

91 FW/LB use CPU at flow start

92 optimized stacks performance

93 upgrade certainty

94 distinct security forwarding shaping priority

95 outcomes

96 working multitenancy

97 isolated addressing

98 programmable

99 independent and ephemeral

100 VM VM VM VM

101 virtual IP virtual MAC

102 route my packets/frames without collisions

103 move v- net without changes

104 tear down when finished

105 separately alter physical and virtual topologies

106 consider: on- demand HA/DR

107 consider: on- demand HA DR

108 SDN (*) manages state * As defined previously

109 VM VM VM VM

110 VM VM VM VM

111 VM VM VM VM

112 abstractional consistency

113 (mature orchestration?)

114 servers = disposable horsepower

115 networks = disposable pathways

116 Virtual server Datapath CPU memory device I/O nanosecond operation = complexity at speed Consistency self- contained Virtual network address contexts all- port knowledge N instances of N states consistency on all paths timely distribution = complexity at scale

117 Virtual server Datapath CPU memory device I/O nanosecond operation = complexity at speed Consistency self- contained Virtual network address contexts all- port knowledge N instances of N states consistency on all paths timely distribution = complexity at scale

118 easy familiar point solution ideas

119 Tagging Segmentation, not isolation Same address in both worlds Hardware has to understand No mobility

120 Tagging Address mapping Segmentation, not isolation Same address in both worlds Hardware has to understand No mobility Like NAT: update address in place Multiplex large space into small: how? Virtual- to- virtual: physical punch

121 Tagging Address mapping Segmentation, not isolation Same address in both worlds Hardware has to understand No mobility Like NAT: update address in place Multiplex large space into small: how? Virtual- to- virtual: physical punch Encapsulation Or tunnels, or overlays (sigh) Worlds can be totally distinct Different forwarding for V and P Strong isolation: no V on P w/o bridge PA demux VA payload

122 Virtual server Datapath CPU memory device I/O nanosecond operation = complexity at speed Consistency self- contained Virtual network address contexts all- port knowledge N instances of N states consistency on all paths timely distribution = complexity at scale programmability and cloudability

123 hard scary innovative advancements

124 Resources

125 networkheresy.com packetpushers.net blog.ioshints.con sdncentral.com

126 Thanks for coming! Steve Riley Technical Director, Office of the CTO Riverbed Technology