Neutron's explicit congestion notification support

Registered by vikram.choudhary on 2015-03-19

Network congestion can be very common in large data centers generating huge traffic from multiple hosts. Though each hosts can use IP header TOS ECN bit functionality to implement explicit congestion notification (http://en.wikipedia.org/wiki/Explicit_Congestion_Notification) but this will be a redundant effort.

This proposal talks about exploring OVS capability of achieving ECN on behalf of each host. This will help in making the solution centralized and can be done per tenant level. In addition to this traffic classification for applying ECN functionality can also be achieved via specific filtering rules, if required. Almost all the leading vendors support this option to ensure QoS. Each vendor can update their plug-in's for using the proposed QoS API extension for their cloud service environment orchestrated via openstack.

Blueprint information

Status:
Complete
Approver:
Miguel Angel Ajo
Priority:
Undefined
Drafter:
vikram.choudhary
Direction:
Needs approval
Assignee:
Ramanjaneya Reddy Palleti
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Armando Migliaccio on 2015-12-08

Related branches

Sprints

Whiteboard

Dec-07-2015(armax): If someone is interested in pursuing it, this must be re-submitted according to guidelines defined in [1].

[1] http://docs.openstack.org/developer/neutron/policies/blueprints.html

---------------

This proposal adds ECN capability to the earlier proposed QoS idea.
    https://blueprints.launchpad.net/neutron/+spec/quantum-qos-api

RFE Bug.
    https://bugs.launchpad.net/neutron/+bug/1505627

(?)

Work Items