yahoo-eng-team team mailing list archive

[Miguel Angel Ajo <majopela@xxxxxxxxxx>]

** Changed in: neutron
       Status: Incomplete => Won't Fix

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

Title:
  [RFE] Rename API options related to QoS bandwidth limit rule

Status in neutron:
  Won't Fix

Bug description:
  Currently in QoS there is rule:
  bandwidth_limit

  and API options to manipulate with it are:
  qos-bandwidth-limit-rule-create
  qos-bandwidth-limit-rule-delete
  qos-bandwidth-limit-rule-list  
  qos-bandwidth-limit-rule-show  
  qos-bandwidth-limit-rule-update

  Those rules are only used for egress bandwidth limit. 
  As we want to introduce ingress bandwidth limit rule (named: ingress_bandwidth_limit) (see https://launchpad.net/bugs/1560961) and API options for it will be:

  qos-ingress-bandwidth-limit-rule-create
  qos-ingress-bandwidth-limit-rule-delete
  qos-ingress-bandwidth-limit-rule-list  
  qos-ingress-bandwidth-limit-rule-show  
  qos-ingress-bandwidth-limit-rule-update

  We should consider to rename existing rule to:
  egress_bandwidth_limit

  and API options to something like:
  qos-egress-bandwidth-limit-rule-create
  qos-egress-bandwidth-limit-rule-delete
  qos-egress-bandwidth-limit-rule-list  
  qos-egress-bandwidth-limit-rule-show  
  qos-egress-bandwidth-limit-rule-update

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