Comment 20 for bug 1586056

Reviewed: https://review.openstack.org/426946
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e2226fe373dfde74e8fc9e64ad65100e1c5de98b
Submitter: Jenkins
Branch: master

commit e2226fe373dfde74e8fc9e64ad65100e1c5de98b
Author: Sławek Kapłoński <email address hidden>
Date: Mon Jan 30 21:56:38 2017 +0000

    Improve validation of supported QoS rules

    New way of validation of QoS policy can be applied on port/network based on
    port_types. It can validate if port can support rule by rule_type and also by
    rule parameters or some values of parameters.

    For example bandwidth_limit_rule can have parameter "direction" with
    possible values "ingress" and "egress". Some of mechanism drivers can support
    only one of those directions.

    If user will try to apply policy with rule unsupported by port_type then it
    will get error message and policy will not be applied.
    Such validation is made during:
    * port create
    * port update
    * network update
    * QoS rule create
    * QoS rule update

    Co-Authored-By: Miguel Angel Ajo <email address hidden>

    Implements blueprint qos-rules-validation
    Closes-Bug: #1586056

    Change-Id: I75bd18b3a1875daa5639dd141fb7bbd6e1c54118