Hey QoS on Floating IP will work with networking-ovn and there is no need to add anything to OVN.
Maciej On Mon, Mar 23, 2020 at 11:09 AM Numan Siddique <[email protected]> wrote: > On Mon, Mar 23, 2020 at 2:59 PM Maciej Jozefczyk <[email protected]> > wrote: > > > > Hello, > > > > Solution found and it is easy. It is just a matter of proper match. > > Example row in QoS table: > > > > _uuid : 85f400e9-f82f-47f0-ac93-b151ed843734 > > action : {} > > bandwidth : {burst=200, rate=200} > > direction : from-lport > > external_ids : {} > > match : "inport == > \"96242e8f-602f-4077-984a-5659e84a8c4f\" && ip4.src == 172.24.5.126 && > is_chassis_resident(\"cr-lrp-96242e8f-602f-4077-984a-5659e84a8c4f\")" > > priority : 20002 > > > > Where inport is a gateway Logical Port, and ipv4.src is Floating IP. > > Does this mean that it can be handled by networking-ovn and it works ? > Or does it require some work in OVN as well ? If so, you plan to > submit the patch ? > > Thanks > Numan > > > > > Thanks, > > Maciej > > > > > > > > On Fri, Mar 6, 2020 at 3:36 PM Maciej Jozefczyk <[email protected]> > wrote: > >> > >> Hey! > >> > >> In Openstack Neutron we can configure QoS in a few different places: > >> 1) QoS on port > >> 2) QoS on Gateway (gateway port) > >> 3) QoS on Floating IP > >> > >> For both 1) and 2) we can easily define a qos row in QoS table and > create proper match action, like: > >> > >> # ovn-nbctl list qos > >> _uuid : 42aa1074-ad2e-4d3c-abf8-c2dceb1169f9 > >> action : {} > >> bandwidth : {burst=3000, rate=3000} > >> direction : from-lport > >> external_ids : {} > >> match : "inport == > \"015aa2ca-6d18-4d0e-96e5-91d44dc1a398\"" > >> priority : 2002 > >> > >> That will be applied on OVS as a OpenFlow Meter. > >> > >> For 3) - Is it possible to apply meter action on Floating IP? > >> By Floating IP I mean NAT with dnat_and_snap type, like: > >> > >> # ovn-nbctl find NAT type=dnat_and_snat > >> _uuid : faf6cba8-d923-4a80-a262-4346232cba2d > >> external_ip : "10.74.167.211" > >> external_mac : "fa:16:3e:94:8e:89" > >> logical_ip : "192.168.1.6" > >> logical_port : "755413fa-fd8d-4e4f-bcdb-bd9e69b12268" > >> type : dnat_and_snat > >> > >> > >> There is use-case, when we want to shape traffic to/from > provider_network, but not in tenant network. We could define QoS for > Gateway Chassis Logical_Router_Port, but we want each VM to have his own > N/S traffic shaping. > >> > >> Can we somehow combine meters with NATs? > >> > >> Thanks, > >> Maciej > >> > >> > >> > >> > >> -- > >> Best regards, > >> Maciej Józefczyk > > > > > > > > -- > > Best regards, > > Maciej Józefczyk > > _______________________________________________ > > discuss mailing list > > [email protected] > > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > -- Best regards, Maciej Józefczyk
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
