On 10/29/22 18:42, Alex Weasel via discuss wrote:
> Additionally i seeing such messages in ovs log when new port is attached
> 2022-10-29T16:39:41.844Z|20936|netdev_linux|DBG|unknown qdisc "noqueue"
> 2022-10-29T16:39:41.990Z|20988|jsonrpc|DBG|unix:/run/openvswitch/db.sock:
> received notification,
Additionally i seeing such messages in ovs log when new port is attached
2022-10-29T16:39:41.844Z|20936|netdev_linux|DBG|unknown qdisc "noqueue"
2022-10-29T16:39:41.990Z|20988|jsonrpc|DBG|unix:/run/openvswitch/db.sock:
received notification, method="update3",
params=[["monid","Open_vSwitch"],"0
Hello mates
This is another day i'm trying to resolve this issue related to ingress QoS.
What you did that make the problem appear.
We using OpenStack Neutron + OVS to add connectivity for our instances
and we have to add QoS which handled by OVS. Our actions are to create
QoS policy with ingress/
Hello matesThis is another day i'm trying to resolve this issue related to ingress QoS.What you did that make the problem appear.We using OpenStack Neutron + OVS to add connectivity for our instances and we have to add QoS which handled by OVS. Our actions are to create QoS policy with ingress/egre
