Re: [ovs-discuss] ovs pypi package
On Fri, Jul 21, 2023 at 3:45 AM Ilya Maximets wrote: > > On 7/19/23 09:52, Felix Huettner via discuss wrote: > > Hi everyone, > > > > i noticed that the latest release of the ovs library on pypi is for > > 2.17.1 [1]. Would it be possible to pushlish newer versions of the ovs > > python lib there as well, or are there reasons speaking against that? > > The pypi package is maintained by OpenStack folks mostly > for their own use. But, I guess, it should be possible > to update to some newer stable release. > > Terry, what do you think? > > Best regards, Ilya Maximets. > > > > > [1] https://pypi.org/project/ovs/#history > > > > Thanks > > Felix I'll go ahead and make a release today. It would be worth discussing having ownership of the pypi ovs package include people responsible for OVS releases and making releasing there part of the release process. One could argue that me owning the package upstream is a little...weird. :) Terry ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Marking packet is tunneling packet
On 7/23/23 05:30, PHAM THANH HAI 20191817 via discuss wrote: > Hi, > > I’m working with tunneling traffic (GENEVE and Vxlan). I have some VMs > connect with a OVS bridge. Traffic from VMs is both tunnel and non-tunnel. > Beside that, I have a Ryu controller to config qos for ports in bridge. I > want matching only tunnel traffic in OVS by flow. I know that OVS has > metadata fields like: tun_id, tun_src, tun_dst,… for tunnel traffic, but that > fields is only for tunnel port. I tried set ports which connect with VMs to > tunnel port with remote_ip is flow. But by that way, Ryu controller can’t > find and config this port. > > So i want to ask: Does have any way to OVS matching tunnel traffic in > non-tunnel port or have any way to Ryu controller can find and config to > tunnel port? Hi. I'm not sure why your controller is not able to see tunnel ports, they should be visible like any other ports. But encapsulated packets usually have specific UDP destination port numbers, so you should be able to create OpenFlow rules that match on them, in case you just need to forward these packets without decapsulation. Best regards, Ilya Maximets. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] Marking packet is tunneling packet
Hi,I’m working with tunneling traffic (GENEVE and Vxlan). I have some VMs connect with a OVS bridge. Traffic from VMs is both tunnel and non-tunnel. Beside that, I have a Ryu controller to config qos for ports in bridge. I want matching only tunnel traffic in OVS by flow. I know that OVS has metadata fields like: tun_id, tun_src, tun_dst,… for tunnel traffic, but that fields is only for tunnel port. I tried set ports which connect with VMs to tunnel port with remote_ip is flow. But by that way, Ryu controller can’t find and config this port.So i want to ask: Does have any way to OVS matching tunnel traffic in non-tunnel port or have any way to Ryu controller can find and config to tunnel port? Sent from Mail for Windows ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
