yahoo-eng-team team mailing list archive

[Arkady Shtempler <1777627@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

 In order to create QoS rule we must provide policy name and that’s OK, because rule should be 
associated to specific QoS policy.
 Once user wants to manage the existing QoS rules, for example: SHOW, DELETE or SET commands, <qos-policy> and <rule-id> are mandatory parameters and this doesn’t make sense as <rule-id>  only should be enough. (Just like we have in other features, security groups for example)

The above is relevant for both: Rest APIs and CLI. 
Documentation change will be required on fix.


Usage example for: SET,DELETE and SHOW

1) SET
(openstack) network qos rule set
usage: network qos rule set [-h] [--max-kbps <max-kbps>]
                            [--max-burst-kbits <max-burst-kbits>]
                            [--dscp-mark <dscp-mark>] [--min-kbps <min-kbps>]
                            [--ingress | --egress]
                            <qos-policy> <rule-id>

2) DELETE
(openstack) network qos rule delete
usage: network qos rule delete [-h] <qos-policy> <rule-id>
network qos rule delete: error: too few arguments

3) SHOW
(openstack) network qos rule show
usage: network qos rule show [-h] [-f {json,shell,table,value,yaml}]
                             [-c COLUMN] [--max-width <integer>] [--fit-width]
                             [--print-empty] [--noindent] [--prefix PREFIX]
                             <qos-policy> <rule-id>
network qos rule show: error: too few arguments

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: qos

** Tags added: qos

** Summary changed:

- QoS – rule management (set,delete, show…) requires <qos-policy> parameter in addition to <Rule-ID> 
+ QoS – rule's management (set,delete, show…) requires <qos-policy> parameter in addition to <rule-id>

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

Title:
  QoS – rule's management (set,delete, show…) requires <qos-policy>
  parameter in addition to <rule-id>

Status in neutron:
  New

Bug description:
   In order to create QoS rule we must provide policy name and that’s OK, because rule should be 
  associated to specific QoS policy.
   Once user wants to manage the existing QoS rules, for example: SHOW, DELETE or SET commands, <qos-policy> and <rule-id> are mandatory parameters and this doesn’t make sense as <rule-id>  only should be enough. (Just like we have in other features, security groups for example)

  The above is relevant for both: Rest APIs and CLI. 
  Documentation change will be required on fix.

  
  Usage example for: SET,DELETE and SHOW

  1) SET
  (openstack) network qos rule set
  usage: network qos rule set [-h] [--max-kbps <max-kbps>]
                              [--max-burst-kbits <max-burst-kbits>]
                              [--dscp-mark <dscp-mark>] [--min-kbps <min-kbps>]
                              [--ingress | --egress]
                              <qos-policy> <rule-id>

  2) DELETE
  (openstack) network qos rule delete
  usage: network qos rule delete [-h] <qos-policy> <rule-id>
  network qos rule delete: error: too few arguments

  3) SHOW
  (openstack) network qos rule show
  usage: network qos rule show [-h] [-f {json,shell,table,value,yaml}]
                               [-c COLUMN] [--max-width <integer>] [--fit-width]
                               [--print-empty] [--noindent] [--prefix PREFIX]
                               <qos-policy> <rule-id>
  network qos rule show: error: too few arguments

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