yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1599381@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

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

Title:
  [RFE] Add bandwidth quota of certain tenant's floating-ips

Status in neutron:
  Expired

Bug description:
  For a certain scenery, a tenant's max available bandwidth of
  floatingips should be added to quota list.

  Use cases
  =========
  In certain commercial scenery with neutron, such as some VNF cases using TECS of ZTE, admininstrator need to have previlege to limit the total egrees bandwidth of all floatingips belongs to a tenant, because of the physical network's expensive cost.  But for now, it is not allowed to limit bandwidth resource for certain tenant.

  Now like below:
  ============
  [root@localhost devstack]# neutron quota-update --tenant-id d9cc08fe87ee49f08020baa95893e2ef --floatingips-bandwidth 100000
  Unrecognized attribute(s) 'floatingips_bandwidth'
  Neutron server returns request_ids: ['req-2b534556-5c97-4c40-9f0e-5e488403cd1b']

  I think it should be:
  =====================
  While the bandwidth quota is set, firstly this tenant's floatingip should be limited by QoS policy with qos-bandwidth-limit-rule referring to https://bugs.launchpad.net/neutron/+bug/1596611. Secondly, the sum of all floatingips bandwidth should not be greater than the quota configuration. This implementation will bring more usablity in commertail scenery for openstack.

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