> even if linuxbridge is fixed, the issue with mixed mech drivers still exists when one of them
> doesn't support a rule type, right?
Yes, that's correct. But this list should provide (and the idea was accepted) the whole list of rules accepted by all loaded drivers. This list can't be only a set of common accepted rules, because it's incomplete. So, you can create a rule which could be not supported by any of the loaded backends.
But QoS plugin is aware of this and gives you a warning message in case you try to link a backend with an incompatible rule. Also there is a patch https://review.openstack.org/#/c/466500/ which will provide more information about the supported rule types and the loaded drivers.
If you are experiencing a problem with a test, please give us the reference to this problem (logs) and we can help you migrating you out-of-tree plugin test to this new feature.
Hello Yamamoto:
> even if linuxbridge is fixed, the issue with mixed mech drivers still exists when one of them
> doesn't support a rule type, right?
Yes, that's correct. But this list should provide (and the idea was accepted) the whole list of rules accepted by all loaded drivers. This list can't be only a set of common accepted rules, because it's incomplete. So, you can create a rule which could be not supported by any of the loaded backends.
But QoS plugin is aware of this and gives you a warning message in case you try to link a backend with an incompatible rule. Also there is a patch https:/ /review. openstack. org/#/c/ 466500/ which will provide more information about the supported rule types and the loaded drivers.
If you are experiencing a problem with a test, please give us the reference to this problem (logs) and we can help you migrating you out-of-tree plugin test to this new feature.
Reverting the commit https:/ /review. openstack. org/#q, 3299cdffae5cd71 96a1676da103da5 e2e413ec21, n,z just because some tests are failing shouldn't be the solution. Instead of that, we should try to solve the problems in the test.