Re: [ovs-discuss] OVS/OVN docker image for each stable release

2019-11-12 Thread Numan Siddique
On Wed, Nov 13, 2019 at 12:02 AM Shivaram Mysore wrote: > > No need to indicate "built on Ubuntu" for docker image tags. > Alpine tag is specifically used as it used different libraries and image size > is small. Ideally, for Docker images, we should use Alpine Linux. If OVS > for Alpine is

Re: [ovs-discuss] skipping output to input port

2019-11-12 Thread Nicolas Bouliane via discuss
> Sometimes, icmpv6 neighbor advertisement packets are being sent out of the > hypervisor without their VLAN tag. It seems to only happens when the icmpv6 > is sent to a multicast address. That doesn't happen to every VMs, and not > all the > I meant Neighbor Solicitation

[ovs-discuss] skipping output to input port

2019-11-12 Thread Nicolas Bouliane via discuss
Sometimes, icmpv6 neighbor advertisement packets are being sent out of the hypervisor without their VLAN tag. It seems to only happens when the icmpv6 is sent to a multicast address. That doesn't happen to every VMs, and not all the time. Can't reproduce the problem on demand yet. I'm trying to

[ovs-discuss] Custom template fields with IPFIX

2019-11-12 Thread Nick
Hi, I'm trying to setup custom IPFIX export field that include a custom metadata field loaded from the ovs flow register. I have successfully setup ipfix sampling with a flow sample action but I can't get a custom field to be exported. Looking at the docs there is an `external_ids` field, which

Re: [ovs-discuss] OVS/OVN docker image for each stable release

2019-11-12 Thread Shivaram Mysore
No need to indicate "built on Ubuntu" for docker image tags. Alpine tag is specifically used as it used different libraries and image size is small. Ideally, for Docker images, we should use Alpine Linux. If OVS for Alpine is latest, then image size will be further reduced. Note thAt at the

Re: [ovs-discuss] OVS/OVN docker image for each stable release

2019-11-12 Thread aginwala
Thanks Shivaram: On Tue, Nov 12, 2019 at 9:28 AM Shivaram Mysore wrote: > I am not sure why "*_debian" is used. The image should work across OS. > I have not seen use of "*_linux" as most docker images use some form of > shell scripts. > > Because the container image published is ubuntu and

Re: [ovs-discuss] OVS/OVN docker image for each stable release

2019-11-12 Thread Shivaram Mysore
I am not sure why "*_debian" is used. The image should work across OS. I have not seen use of "*_linux" as most docker images use some form of shell scripts. Also, in my opinion, the docker image should not build OVS. If it can add appropriate OVS packages like

Re: [ovs-discuss] ovs-vswitchd.service crashes

2019-11-12 Thread Koukal Petr
Hello, I installed the linux-generic-hwe-18.04-edge kernel. apt list --installed | grep linux-image linux-image-generic-hwe-18.04-edge/bionic,now 4.18.0.16.65 amd64 [installed] hwe-support-status - verbose Your Hardware Enablement Stack (HWE) is supported until April 2023. Previously reported

Re: [ovs-discuss] OVS/OVN docker image for each stable release

2019-11-12 Thread aginwala
Thanks Guru. On Mon, Nov 11, 2019 at 1:03 PM Guru Shetty wrote: > > > On Mon, 11 Nov 2019 at 10:08, aginwala wrote: > >> >> >> On Mon, Nov 11, 2019 at 9:00 AM Guru Shetty wrote: >> >>> >>> >>> On Fri, 8 Nov 2019 at 14:41, aginwala wrote: >>> openvswitch.ko ships default with newer

[ovs-discuss] regarding trunc feature changes for OVS_ACTION_ATTR_USERSPACE

2019-11-12 Thread bindiya Kurle
Hi , i am not getting reason,why highlighted code is added for OVS_ACTION_ATTR_USERSPACE. What purpose it serves. This code got added as part of feature "ofp-actions: Add truncate action. The patch adds a new action to support packet truncation. " Can somebody please help in understanding