Goal:

Now, since [1][2], all QoS policies that apply to a port (1) in a physical network (VLAN, flat) and (2) with egress direction, are defined in the `Logical_Switch_Port.options` dictionary. Thus, OVN creates the OVS QoS registers and OVS applies the QoS rules on the physical interface.

This is a problem (and a regression) for max-bw only environments using ML2/OVN, physical networks and bond interfaces. The TC rules cannot be applied on multiple interfaces.

Acceptance Criteria:

This feature needs to partially revert the implementation of [1][2] but only for QoS policies with max-bw only rules; of course, that won't apply if we also have min-bw rules. In the related cases (max-bw only rules), it is needed to use the OVN policer and apply the max-bw cap inside OVN, skipping applying the TC rules on the bond interface, because is not possible.

If the max-bw is correctly applied on a VM located in a compute node that has a bond interface for the physical network that has the VM port, this implementation will be validated.

Other actions.

It is needed to document the current regression. Once the feature is implemented, it is needed to correctly document how the feature works (max-bw only, min-bw, etc) and what are the limitations for each one.

[1]https://issues.redhat.com/browse/OSPRH-11045

[2]https://gitlab.cee.redhat.com/eng/openstack/neutron/-/merge_requests/11