Controller- based Path Selec2on for Distributed IaaS Cloud Environment arch B4 yummy 1
Outline of Presenta2on 1. Problems of Distributed IaaS Cloud Environment Higher latency to some des2na2ons Many unnecessary FDB crea2on/lookups 2. Proposal of Controller- based path selec2on Single FDB on Controller Forwarding via path with lowest latency Automa2c selec2on of nearest gateway 2
Internet Services Today and Future Demand for faster response 2me is gelng stronger and stronger Lower latency is required for beoer response 2me Future: Be responsive regardless of client loca2on Move the service as user moves Select the best path to the user User Gateway User Gateway Hypervisor Tokyo Seoul Hypervisor 3
Distributed IaaS Cloud Environment PlaSorm for running personal services For example, personal desktop service (thin client) WIDE Cloud Hypervisors located in both inside and outside Japan Possible to move services without stopping it Controller Internet Gateway Virtual L2 Network Hypervisor Hypervisor Hypervisor SFC Tokyo Seoul 4
Problems on Moving Services Controller without Stopping 1. Random Hypervisor selec2on Network 1. No forwarding path selec2on mechanism 2. No Gateway selec2on mechanism 3. Many unnecessary FDB crea2on/lookups Storage 1. Disk access is slow when mounted over high latency environment 5
Problems on Moving Services Controller without Stopping 1. Random Hypervisor selec2on Final Thesis Network 1. No forwarding path selec2on mechanism 2. No Gateway selec2on mechanism 3. Many unnecessary FDB crea2on/lookups Storage 1. Disk access is slow when mounted over high latency environment 6
Wide- area Layer 2 Network between Mul2ple Datacenters Term Project: Mul2point Layer 2 Network Tunneling To be able to use the same network configura2on Tunnel directly to destination for Ethernet frames Forwarding path problem, Gateway Selec2on and FDB Management problem exist! Point- to- Point Tunnel MulApoint Tunnel Home SFC Home SFC Seoul Dojima Seoul Dojima 7
Problem #1: Forwarding Path Need a way to select an available path with lowest latency IP Route is not always the path with lowest latency Source and Des2na2on End Point may not be able to communicate directly Home Seoul Home Seoul 3ms 3ms 33ms SFC 8ms Dojima SFC 8ms Dojima 8
Problem #2: Gateway Selec2on Need a way to select gateway Home Solve the problem with Single Gateway setups High latency in some cases Single point of failure Select gateway from mul2ple gateways Seoul Home Seoul <1ms 3ms SFC 15ms 8ms 8ms Dojima 3ms SFC 11ms 8ms Dojima 9
Problem #3: FDB Management Need a way to share FDB and manage it Many crea2on/lookups of FDB Incorrect FDB Informa2on 1. FDB Lookup aa:bb:cc:12:34:56 TUNNEL GW Hard to detect movement of Network connec2on may become unavailable 4. FDB Lookup aa:bb:cc:12:34:56 TUNNEL GW TUNNEL GW Hypervisor A br0 br0 2. FDB Lookup aa:bb:cc:12:34:56 Hypervisor B 3. FDB Lookup aa:bb:cc:12:34:56 br0 TUNNEL GW br0 Hypervisor C Hypervisor B 10 10
Requirements 1. Lowest latency path selec2on Forward ethernet frames via path with lowest path 2. Nearest gateway selec2on Select gateway with lowest latency automa2cally 3. BeOer FDB Management Prevent mul2ple FDB crea2on and lookups 11
Wide- area Virtual Switch Chassis All Hypervisors are a part of virtual chassis in Hypervisors are line cards of the chassis Forwarding path selected by controller Not the Linux Bridge or the Tunnel End Point Wide- area Virtual Switch Chassis FDB Latency Flow Controller Controller Flow Flow 1 2 Hypervisor A 3 4 Hypervisor C 5 6 Hypervisor B 12
Layer 2 Forwarding Forward according to the path selected by Controller Query controller on packet forwarding Path selected using FDB and Latency DB FDB 3 5: B/5 Path to B: A- >C- >B 4 Latency Flow Controller Controller Hypervisor C Flow 8ms 20ms Path to 5? 1 5 2 6 Hypervisor A Hypervisor B Wide- area Switch Chassis 13
FDB Single FDB on the Controller Prevent mul2ple crea2on/lookup of DB with same data Use Cloud Controller DB (=WCC) Cloud Controller (=WCC) has latest informa2on of Loca2on and MAC Address FDB 3 4 Latency Flow Controller Controller Hypervisor C Control 1 5 2 6 Hypervisor A Hypervisor B 14
Latency DB Collect latency informa2on on Controller Latency between each Hypervisors Use Dijkstra algorithm to figure out the best path to des2na2on Wide- area Virtual Switch Chassis FDB 3 4 Latency Flow Controller Controller Hypervisor C 8ms 20ms 1 5 2 6 Hypervisor A Hypervisor B 15
Nearest Gateway Selec2on Select gateway using Latency DB on Virtual Chassis Forward to a gateway with least latency Gateway: C/0 Path to C: A- >C FDB Flow Controller 3 4 Hypervisor C Gateway Latency Flow Controller Flow 8ms 20ms Internet 1 5 Rewrite Dst: Gateway - > Gateway C 2 6 Hypervisor A Hypervisor B Wide- area Switch Chassis 16 Gateway 16
Final Thesis Low Latency IaaS Cloud Environment Provide beoer route to des2na2on BeOer rou2ng over tunnels Select nearest Gateway available Wide- area Virtual Switch Chassis All es controlled by single Controller Single FDB and Latency DB Layer 2 Tunneling and Route Selec2on Gateway selec2on (Rewrite of Des2na2on) 17
Evalua2on Latency and Throughput Comparison Create topology similar to one below Compare with Implementa2on done on Term Project 8ms 1 2 Hypervisor A 3 4 Hypervisor C 20ms 5 6 Hypervisor B Gateway Internet Gateway 18
Current Status Made a development environment Two Servers running : SFC and Home Created Simple Layer 2 Switch Controller For learning Flow API Coding s2ll needed Controller FDB which queries WCC Latency DB crea2on Dijkstra based Path selec2on mechanism Nearest Gateway Selec2on Switch Bridging Feature 19
Coding Controller DB Layer 2 Tunnel Gateway Selec2on Experiment Latency Throughput Thesis Wri2ng Schedule 8 9 10 11 12 1 20
Conclusion Problem: High latency and FDB management problems in current Distributed IaaS Cloud Environment Un- op2mized Layer 2 Tunneling path Single gateway setup Many unnecessary FDB crea2on/lookups Proposal: Controller- based path selec2on Lowest latency path selec2on using data on Controller Single FDB Latency DB Automa2c nearest gateway selec2on 21