Hello Erlon:

"OVN L3 plugin supports floating IP bandwidth limiting based on the OVN’s QoS rules". That means OVN L3 plugin supports FIP QoS. This feature is supported since Wallaby.

OVN L3 plugin still does not support QoS on router GW port.

Regards.

On Fri, Sep 24, 2021 at 1:50 PM Erlon Cruz <sombrafam@gmail.com> wrote:
Hi folks,

I'm confused now. I have recently read that [1]:

"Currently the Neutron L3-agent supports floating IP and gateway IP bandwidth limiting based on Linux TC. OVN L3 plugin supports floating IP bandwidth limiting based on the OVN’s QoS rules. Neutron OVN backend does not yet support bandwidth limiting for gateway IP"

So, QoS, especially FIP QoS is not present in OVN yet. I'm I missing something? If it supports, what versions that was added?

Erlon
________________
[1] https://docs.openstack.org/neutron/latest/ovn/gaps.html



Em qui., 23 de set. de 2021 às 08:37, Rodolfo Alonso Hernandez <ralonsoh@redhat.com> escreveu:
Hello Ammad:

This is not possible. You can create a default QoS policy that will apply to a network and thus to the internal ports created on this network.

When you create a FIP, a port on the external network is created and this port receives a QoS policy (the default policy). However, the FIP QoS driver reads the FIP QoS policy, not the associated FIP port QoS policy. That means, for now, what you need is not possible.

Regards.


On Thu, Sep 23, 2021 at 1:14 PM Slawek Kaplonski <skaplons@redhat.com> wrote:
Hi,

On czwartek, 23 września 2021 12:33:13 CEST Ammad Syed wrote:
> Hello,
>
> I am using Neutron wallaby with OVN backend. I am testing QoS FIP and it
> works fine.
>
> I have created a QoS policy and attached it with FIP, It works fine. Is it
> possible to set one of the QoS policy as default that each time I acquire a
> floating IP, the QoS should be attached to it by default ?
>
> Ammad

You can mark QoS policy as default for the project: https://
docs.openstack.org/api-ref/network/v2/index.html?expanded=create-qos-policy-
detail#qos-default-extension

But TBH I'm not sure if that will work with FIPs - You should test it and if
that will not work, probably You can open bug for Neutron about that :)

--
Slawek Kaplonski
Principal Software Engineer
Red Hat