From: Jenkins Date: Fri, 7 Aug 2015 19:22:12 +0000 (+0000) Subject: Merge "Updated quality_of_service devref doc to reflect reality" into feature/qos X-Git-Url: https://review.fuel-infra.org/gitweb?a=commitdiff_plain;h=e56778b5cbfad930fad3894320d198f14b2a265e;p=openstack-build%2Fneutron-build.git Merge "Updated quality_of_service devref doc to reflect reality" into feature/qos --- e56778b5cbfad930fad3894320d198f14b2a265e diff --cc doc/source/devref/quality_of_service.rst index 9dd014368,023eb42f6..9a2062814 --- a/doc/source/devref/quality_of_service.rst +++ b/doc/source/devref/quality_of_service.rst @@@ -45,16 -64,11 +64,16 @@@ list defined on the class For Ml2 plugin, the list of supported QoS rule types is defined as a common subset of rules supported by all active mechanism drivers. +Note: the list of supported rule types reported by core plugin is not enforced +when accessing QoS rule resources. This is mostly because then we would not be +able to create any rules while at least one ml2 driver in gate lacks support +for QoS (at the moment of writing, linuxbridge is such a driver). + - QoS resources - ------------- + Database models + --------------- - QoS design defines the following two conceptual resources to define QoS rules + QoS design defines the following two conceptual resources to apply QoS rules for a port or a network: * QoS policy