e2226fe373
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 <majopela@redhat.com> Implements blueprint qos-rules-validation Closes-Bug: #1586056 Change-Id: I75bd18b3a1875daa5639dd141fb7bbd6e1c54118 |
||
---|---|---|
.. | ||
__init__.py | ||
_deprecate.py | ||
cache_utils.py | ||
config.py | ||
constants.py | ||
eventlet_utils.py | ||
exceptions.py | ||
ipv6_utils.py | ||
profiler.py | ||
rpc.py | ||
test_lib.py | ||
topics.py | ||
utils.py |