yahoo-eng-team team mailing list archive

["vikram.choudhary" <vikram.choudhary@xxxxxxxxxx>]

Public bug reported:

[Existing problem]
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 [1]_ but this will be a redundant effort.

[Proposal]
This proposal talks about 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 for better QoS [2]_.

Existing QoS framework is limited only to bandwidth rate limiting and be
extend for supporting explicit congestion notification (RFC 3168 [3]_).

[Benefits]
- Enhancement to the existing QoS functionality.

[What is the enhancement?]
- Add ECN support to the QoS extension.
- Add additional command lines for realizing ECN functionality.
- Add OVS support.

[Related information]
[1] ECN Wiki
   http://en.wikipedia.org/wiki/Explicit_Congestion_Notification
[2] QoS
   https://review.openstack.org/#/c/88599/
[3] RFC 3168
   https://tools.ietf.org/html/rfc3168
[4] Specification
    https://blueprints.launchpad.net/neutron/+spec/explicit-congestion-notification

** Affects: neutron
     Importance: Undecided
     Assignee: vikram.choudhary (vikschw)
         Status: New


** Tags: rfe

** Changed in: neutron
     Assignee: (unassigned) => vikram.choudhary (vikschw)

** Summary changed:

- qos-ecn-support
+ QoS ECN Support

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1505627

Title:
  QoS ECN Support

Status in neutron:
  New

Bug description:
  [Existing problem]
  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 [1]_ but this will be a redundant effort.

  [Proposal]
  This proposal talks about 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 for better QoS [2]_.

  Existing QoS framework is limited only to bandwidth rate limiting and
  be extend for supporting explicit congestion notification (RFC 3168
  [3]_).

  [Benefits]
  - Enhancement to the existing QoS functionality.

  [What is the enhancement?]
  - Add ECN support to the QoS extension.
  - Add additional command lines for realizing ECN functionality.
  - Add OVS support.

  [Related information]
  [1] ECN Wiki
     http://en.wikipedia.org/wiki/Explicit_Congestion_Notification
  [2] QoS
     https://review.openstack.org/#/c/88599/
  [3] RFC 3168
     https://tools.ietf.org/html/rfc3168
  [4] Specification
      https://blueprints.launchpad.net/neutron/+spec/explicit-congestion-notification

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1505627/+subscriptions