Jump to: navigation, search

Difference between revisions of "Distributed Router for OVS"

Line 1: Line 1:
  
==  
+
== Brief Intro ==
 +
The goal of this blueprint is to implement distributed router in openvswitch plugin. Openvswitch plugin is the most popular plugin nowadays. However, lots of people found that under heavy east-west traffic, current l3-agent router becomes the bottle neck.
 +
 
 +
With the help of distributed router in ovs plugin, it's not necessary for east-west traffic to traverse network node to get routing decision anymore. Instead, those traffic will be delivered directly from the source hypervisor to the destination hypervisor.
 +
 
 +
The test result of our POC shows distinct performance imporvement on several aspects. Advantages we can get:
 +
1. East-west total throughput will increase distinctly when more hypervisors are involved.
 +
2. Under high concurrency of east-west traffic, on average, each VM will obtain a better bandwidth.
 +
3. North-south and east-west traffic don't impact each other anymore. North-south traffic enjoys all the bandwidth of router exclusively.
 +
4. No more unnecessary circuitous path, when east-west session happens between two VMs on the same hypervisor.
  
 
== Performance Comparison ==
 
== Performance Comparison ==

Revision as of 09:05, 22 October 2013

Brief Intro

The goal of this blueprint is to implement distributed router in openvswitch plugin. Openvswitch plugin is the most popular plugin nowadays. However, lots of people found that under heavy east-west traffic, current l3-agent router becomes the bottle neck.

With the help of distributed router in ovs plugin, it's not necessary for east-west traffic to traverse network node to get routing decision anymore. Instead, those traffic will be delivered directly from the source hypervisor to the destination hypervisor.

The test result of our POC shows distinct performance imporvement on several aspects. Advantages we can get: 1. East-west total throughput will increase distinctly when more hypervisors are involved. 2. Under high concurrency of east-west traffic, on average, each VM will obtain a better bandwidth. 3. North-south and east-west traffic don't impact each other anymore. North-south traffic enjoys all the bandwidth of router exclusively. 4. No more unnecessary circuitous path, when east-west session happens between two VMs on the same hypervisor.

Performance Comparison

Here is a comparison between original OpenStack and a OpenStack with distributed router.

Total East-West Bandwidth Comparison
Total East-West Bandwidth Comparison
Total East-West Bandwidth Comparison
Total East-West Bandwidth Comparison
Total East-West Bandwidth Comparison
Total East-West Bandwidth Comparison