yahoo-eng-team team mailing list archive

[Na Zhu <juno.zhu@xxxxxxxxxx>]

Public bug reported:

The N-S bandwidth is alwawys limited of data center, so it is common use case to limit N-S bandwidth of tenant.
For ipv4, there is floatingip, we can limit N-S bandwidth by floatingip qos, but for ipv6, the address is enough so no need NAT any more. In this way, we can not do N-S bandwidth for ipv6, I think we should find a way to fix it.

PS, the port qos limit both E-W and N-S bandwidth, not a good chice.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: qos

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

Title:
  Does not support ipv6 N-S qos

Status in neutron:
  New

Bug description:
  The N-S bandwidth is alwawys limited of data center, so it is common use case to limit N-S bandwidth of tenant.
  For ipv4, there is floatingip, we can limit N-S bandwidth by floatingip qos, but for ipv6, the address is enough so no need NAT any more. In this way, we can not do N-S bandwidth for ipv6, I think we should find a way to fix it.

  PS, the port qos limit both E-W and N-S bandwidth, not a good chice.

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