yahoo-eng-team team mailing list archive

[LiuYong <liu.yong8@xxxxxxxxxx>]

Public bug reported:

For a certain tenant, there is not a implementation used for limiting
the egrees bandwidth of floating ips.

Use cases
=========
In certain commercial scenery with neutron, such as some VNF cases using TECS of ZTE, the max egrees bandwidth of a floating ip should be limited because of its expensive cost and its flexibility with different fixed ips at different envirenments. As for the bandwidth limiting for one floating ip, it should be the implementation by means of the parameter '--max-kbps' described in . But for now, it is not allowed to executing 'floating-ip-create' with '--qos-policy'.

Now like below:
============
[root@localhost devstack]# neutron floatingip-create public  --qos-policy qos-policy
Unrecognized attribute(s) 'qos_policy'
Neutron server returns request_ids: ['req-b7ff870c-3f43-424b-a694-703726090d69']


I think it should be:
=====================
When a floating ip, created with a 'qos-policy', is associated with a fixed ip, the 'qos-policy' is applied on the fixed port accordingly. This implementation will bring more convenience when tenant destroy the fixed port and deploy another re-associating.

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  Create floating-ips with qos

Status in neutron:
  New

Bug description:
  For a certain tenant, there is not a implementation used for limiting
  the egrees bandwidth of floating ips.

  Use cases
  =========
  In certain commercial scenery with neutron, such as some VNF cases using TECS of ZTE, the max egrees bandwidth of a floating ip should be limited because of its expensive cost and its flexibility with different fixed ips at different envirenments. As for the bandwidth limiting for one floating ip, it should be the implementation by means of the parameter '--max-kbps' described in . But for now, it is not allowed to executing 'floating-ip-create' with '--qos-policy'.

  Now like below:
  ============
  [root@localhost devstack]# neutron floatingip-create public  --qos-policy qos-policy
  Unrecognized attribute(s) 'qos_policy'
  Neutron server returns request_ids: ['req-b7ff870c-3f43-424b-a694-703726090d69']

  
  I think it should be:
  =====================
  When a floating ip, created with a 'qos-policy', is associated with a fixed ip, the 'qos-policy' is applied on the fixed port accordingly. This implementation will bring more convenience when tenant destroy the fixed port and deploy another re-associating.

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