Sławek Kapłoński e2226fe373 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 <majopela@redhat.com> Implements blueprint qos-rules-validation Closes-Bug: #1586056 Change-Id: I75bd18b3a1875daa5639dd141fb7bbd6e1c54118		2017-04-02 16:33:11 +00:00
..
auto_allocate	OVO External Networks	2017-03-07 20:03:30 +00:00
l3_router	Spin off context module	2017-03-06 16:25:29 +00:00
metering	Merge "Update metering agent to use stevedore alias for driver"	2017-04-02 03:50:09 +00:00
qos	Improve validation of supported QoS rules	2017-04-02 16:33:11 +00:00
revisions	Add precommit notifications for create/update port/network in ML2	2017-03-20 20:41:38 +00:00
trunk	use neutron_lib's portbindings api-def	2017-03-31 09:16:22 -06:00
__init__.py	Empty files should not contain copyright or license	2014-10-20 00:50:32 +00:00
test_provider_configuration.py	Use more specific asserts in tests	2016-08-23 07:36:49 +02:00