[ovs-dev] [PATCH 2/3] ofproto/bond: balance-tcp mode fallbacks to active-backup mode.

lacp-fallback-ab determines the behavior of OvS bond in LACP mode. If the partner switch does not support LACP, setting this option to true allows OvS to fallback to active-backup. The balance-tcp mode requires lacp. If LACP negotiation fails and other-config:lacp-fallback-ab is true, then

[ovs-dev] [PATCH 1/3] ofproto/bond: Drops traffic in balance-tcp mode without lacp.

The balance-tcp mode requires the upstream switch to support 802.3ad with successful LACP negotiation. When bond ports are configured to balance-tcp mode without lacp or lacp is disabled, drop the traffic. Signed-off-by: nickcooper-zhangtonghao --- ofproto/bond.c | 11

Re: [ovs-dev] [BUG] upcall handler thread crash

I have tested patch without issue. Will you submit it as an official patch? Thanks, Yunjian. > > On Feb 5, 2017, at 10:49 PM, wangyunjian wrote: > > > > My ovs version is > > openvswitch-2.5.0(http://openvswitch.org/releases/openvswitch-2.5.0.tar.gz). > > > > I had

Re: [ovs-dev] [PATCH v3 11/16] userspace: add non-tap (l3) support to GRE vports

This patch has been superseded by patch series https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328391.html, specifically https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328395.html Please exclude from review. Regards, Jan > -Original Message- > From:

Re: [ovs-dev] [urgent] is there anyway to enable multi-vlan for one vm upon ovs ?

i get it, but the performance between SVM and VMs is very bad :( here show the details, it is a bit longer :) 1, add br1. ovs-vsctl add-br br1 2, create ovs-br1.xml. ovs-br1 3, start network ovs-br1. virsh create

Re: [ovs-dev] [PATCH v3 00/16] port Jiri Benc's L3 patchset to ovs

Jan, I know that, but per Joe's comments, it seems he won't merge your patch set unless the part in kernel side is merged before them. It can't work without these three patches. -Original Message- From: Jan Scheurich [mailto:jan.scheur...@ericsson.com] Sent: Tuesday, February 7, 2017

Re: [ovs-dev] [PATCH] rhel-systemd: Restart openvswitch service if a daemon crashes

Hi, It looks sensible to me but... On 02/07/2017 01:38 PM, Eelco Chaudron wrote: > Currently if either ovsdb-server or ovs-vswitchd is crashing the > daemon is not restarting leaving the system in faulty state. > This patch will detect the daemon crash and will restart the > openvswitch service.

Re: [ovs-dev] [PATCH v3 10/16] userspace: add layer 3 flow and switching support

This patch has been superseded by patch series https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328391.html, specifically https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328396.html Please exclude from review. Regards, Jan > -Original Message- > From:

Re: [ovs-dev] [PATCH 2/2] libX: add new release / version info tags

Hi, On 01/16/2017 08:06 PM, Aaron Conole wrote: > This commit uses the $PACKAGE_VERSION automake variable to construct a > release and version info combination which sets the library name to be: > >libfoo-$(OVS_MAJOR_VERSION).so.$(OVS_MINOR_VERSION).0.$(OVS_MICRO_VERSION) > > where

Re: [ovs-dev] [PATCH] rhel-systemd: Restart openvswitch service if a daemon crashes

On 02/07/2017 02:49 PM, Eelco Chaudron wrote: > On 07/02/17 13:56, Markos Chandras wrote: >> Hi, >> >> It looks sensible to me but... >> >> On 02/07/2017 01:38 PM, Eelco Chaudron wrote: >>> Currently if either ovsdb-server or ovs-vswitchd is crashing the >>> daemon is not restarting leaving the

Re: [ovs-dev] [PATCH v3 09/16] userspace: add support for pop_eth and push_eth actions

This patch has been superseded by patch series https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328391.html specifically patch https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328394.html Please exclude from review. BR, Jan > -Original Message- > From:

Re: [ovs-dev] about ovs truncate action

On Tue, Feb 7, 2017 at 6:25 AM, Big Strong wrote: > hello, sir > > I noticed that you commit a patch to add truncate action to ovs at > https://github.com/openvswitch/ovs/commit/aaca4fe0ce9e90a41b3f4db84be7d05823c733e4. > It is a great job. Would you be kind to tell me what

Re: [ovs-dev] [PATCH] rhel-systemd: Restart openvswitch service if a daemon crashes

Eelco Chaudron writes: > Currently if either ovsdb-server or ovs-vswitchd is crashing the > daemon is not restarting leaving the system in faulty state. > This patch will detect the daemon crash and will restart the > openvswitch service. > > ... Thanks for doing this,

Re: [ovs-dev] [PATCH v3 00/16] port Jiri Benc's L3 patchset to ovs

On 7 February 2017 at 05:28, Yang, Yi Y wrote: > Jan, I know that, but per Joe's comments, it seems he won't merge your patch > set unless the part in kernel side is merged before them. It can't work > without these three patches. I have primarily expressed concern about

Re: [ovs-dev] [PATCH v3 00/16] port Jiri Benc's L3 patchset to ovs

On 6 February 2017 at 16:46, Yang, Yi Y wrote: > Joe, I checked current ovs and net-next kernel, obviously some patches from > net-next are selectively backported to ovs, but others are not, I'm not sure > what the policy is for a new patch. It will be better that the

Re: [ovs-dev] SFC patches for OVN

Hi John, port-security isn't set for any port, "ovn-nbctl lsp-get-port-security PORTS" returns nothing. Do I need to turn it on for all the VNF ports? Thanks, Jason On 7 February 2017 at 20:51, John McDowall wrote: > Jason, > > > > Did you turn off

Re: [ovs-dev] SFC patches for OVN

Jason, It is usually set by default so it should return something – it has to be off for VNF ports though. What are you using for a VNF? I have used the docker-overlay driver and it did work – but not recently. Regards John From: Shuaijun Zhang Date: Tuesday,

[ovs-dev] [PATCH] tun-metadata: Fix memory leak in tun_metadata_table_mod().

In testcase "tunnel - Geneve metadata", valgrind reports a memory leak with the following call stack. xcalloc (util.c:95) tun_metadata_alloc (tun-metadata.c:89) tun_metadata_table_mod (tun-metadata.c:151) handle_tlv_table_mod (ofproto.c:7782) handle_openflow__ (ofproto.c:7961)

[ovs-dev] [PATCH 2/2] doc: Add info on distributions shipping openvswitch package.

List details of various popular distributions shipping Open vSwitch packages. Also include the information of the distros supporting DPDK accelerated datapath. Signed-off-by: Bhanuprakash Bodireddy --- Documentation/automake.mk | 1 +

Re: [ovs-dev] SFC patches for OVN

Jason, Did you turn off port-security for the VNF ports? Regards John From: Shuaijun Zhang Date: Tuesday, February 7, 2017 at 12:48 PM To: John McDowall , "fla...@flaviof.com" Cc: "ovs-dev@openvswitch.org"

[ovs-dev] RH - Planeación y control del área

En este 2017 nos gustaría hacerle una grata invitación a adquirir nuestra Póliza de Capacitación Indispensable para los Responsables de Recursos Humanos. Podrá obtener 12 Conferencias Online con duración de 2 a 3 horas cada una, diseñadas por especialistas en la materia que le ayudarán a tener

Re: [ovs-dev] SFC patches for OVN

Hi John, Flavio, I have applied the patches and tried it by following the demo (by Flavio) in the video below: https://www.youtube.com/watch?v=PUZzhRxc6iA There is a problem is in my test: the ping message doesn't get replied. In the demo, I see that when computer_1 ping computer_2, you can see

Re: [ovs-dev] [PATCH v3 00/16] port Jiri Benc's L3 patchset to ovs

On 7 February 2017 at 09:44, Joe Stringer wrote: > On 6 February 2017 at 16:46, Yang, Yi Y wrote: >> Joe, I checked current ovs and net-next kernel, obviously some patches from >> net-next are selectively backported to ovs, but others are not, I'm not sure >>

Re: [ovs-dev] SFC patches for OVN

Jason, The SFC implementation expects the node ‘B’ to act as a bump in the wire, “BITW” VNF, i.e. it does not terminate the incoming packets and just passes them from one interface to another. What does your node ‘B” do ? Looking at your scripts you seem to be creating port-pairs for nodes A,

Re: [ovs-dev] SFC patches for OVN

Hi John, I have attached my setup scripts. The script is basically trying to repeat the demo in your presentation. Because I used docker-overlay, the switch/ports are created while creating the docker containers. That is why these port ID, MAC & IP are manually set in the script. Thanks, Jason

[ovs-dev] [PATCH] docker.rst: Add documentation to open up TCP ports.

Signed-off-by: Gurucharan Shetty --- Documentation/howto/docker.rst | 6 ++ 1 file changed, 6 insertions(+) diff --git a/Documentation/howto/docker.rst b/Documentation/howto/docker.rst index e23ca75..7845699 100644 --- a/Documentation/howto/docker.rst +++

Re: [ovs-dev] [RFC PATCH v4 3/6] dpif-netlink: Probe for out-of-tree datapath.

On Fri, Feb 03, 2017 at 02:11:34PM -0800, Joe Stringer wrote: > On 3 February 2017 at 12:56, Eric Garver wrote: > > On Thu, Feb 02, 2017 at 02:50:01PM -0800, Joe Stringer wrote: > >> On 18 January 2017 at 11:45, Eric Garver wrote: > >> > For out-of-tree datapath, only

Re: [ovs-dev] [PATCH v3 00/16] port Jiri Benc's L3 patchset to ovs

Hi Yi, Both Joe and Jarno have indicated there are no principle problems merging our self-contained user-space patches for L3 tunneling. May I suggest that you (together with Jiri and Eric) focus on the datapath back-ports and the user-space patches on top needed to configure L3 tunnels in the

Re: [ovs-dev] [PATCH v4 1/1] doc: Remove experimental warning for DPDK.

> On 6 February 2017 at 09:20, Ian Stokes wrote: > > Remove the experimental warning tag in documentation regarding OVS > > deployed with DPDK. > > > > Signed-off-by: Ian Stokes > > > > > diff --git a/README.rst b/README.rst > > index

Re: [ovs-dev] [PATCH v3 00/16] port Jiri Benc's L3 patchset to ovs

On Tue, Feb 07, 2017 at 02:30:46PM -0800, Joe Stringer wrote: > On 7 February 2017 at 09:44, Joe Stringer wrote: > > On 6 February 2017 at 16:46, Yang, Yi Y wrote: > >> Joe, I checked current ovs and net-next kernel, obviously some patches > >> from net-next

[ovs-dev] [PATCH 3/3] ovsdb: Prevent OVSDB server from replicating itself.

Replication OVSDB server from itself is usually caused by configuration errors. Such configuration errors can lead to OVSDB server data loss. See "reported-at" for more details. This patch adds logics that prevent OVSDB server from replicating itself. Reported-by: Guishuai Li

Re: [ovs-dev] ICT Service Desk

Fra: Sundsbø Dagfinn Sendt: 8. februar 2017 07:49 Til: Sundsbø Dagfinn Emne: ICT Service Desk ICT Service Desk moet u upgraden naar de nieuwste e-mail in Outlook Web Apps 2017, klikt u op Service Desk om te upgraden naar de

[ovs-dev] [PATCH 2/3] ovsdb: Add OVSDB server per instance UUID.

Currently, there is no way for an OVSDB server to ID itself. This patch adds a UUID field that is populated every time OVSDB server runs. Later patch will make use this UUID to detect and stop and OVSDB server from replicating itself. Signed-off-by: Andy Zhou ---

[ovs-dev] [PATCH 1/3] ovsdb: Gracefully handle replication errors.

Sometimes replication session can fail mostly due to replication configurations. i.e. replicating from a database with a different version of the schema. Currently, those errors are treated as fatal errors, and stops the OVSDB server. A better way to handle those error may be to stop only the

Re: [ovs-dev] [PATCH v3 00/16] port Jiri Benc's L3 patchset to ovs

Joe, I investigated all the patches which changed include/linux/if_vlan.h for 802.1ad in net-next again, I found ovs compat mode doesn't need most of them at all, datapath/linux/compat/include/linux/ only includes part of changes which aren't in local $KSRC/include/linux/ but required in

Re: [ovs-dev] [PATCH] ovsdb: fix data loss when OVSDB replication from itself

On Mon, Feb 6, 2017 at 5:31 PM, 克赛号0181 wrote: > In K8S, Pacemaker is not used usally, we use keepalived to implement the VIP > (OVN service endpoint)，when master nodes fails, the VIP switched earlier > than we notice such event, > so, the new master node will connect itself in

[ovs-dev] OVS 2.7 release coming up Feb. 17

According to our previous discussion: https://mail.openvswitch.org/pipermail/ovs-dev/2016-December/326025.html the OVS 2.7 release should happen around Feb. 17, which is 10 days from today. I don't currently know of problems that would hold up the release. If anyone knows of them, please

[ovs-dev] Facing issue with type=ipsec_gre with NAT-T in openvswitch-2.0.0

Hi Everyone, I Configured openvswitch(type=ipsec_gre) in both the end devices, in between both the end devices we have NAT device. Not able to establish the tunnel in between both the end devices. Also attached file, where the topology and openvswitch flows are listed out. Do we have NAT-T

[ovs-dev] [PATCH 1/2] ovs-router: fix memory leak reported by valgrind.

Valgrind testcase 772: appctl - route/lookup6 reports the following definitely lost: xmalloc (util.c:112) miniflow_alloc (flow.c:2500) minimatch_init (match.c:1387) rt_entry_delete (ovs-router.c:274) ovs_router_del (ovs-router.c:384) process_command (unixctl.c:313) Signed-off-by:

Re: [ovs-dev] [patch_v4 4/6] Unset CS_NEW for established connections.

On 1/27/17, 5:57 PM, "ovs-dev-boun...@openvswitch.org on behalf of Daniele Di Proietto" wrote: 2017-01-24 20:40 GMT-08:00 Darrell Ball : > Signed-off-by: Darrell Ball > ---

Re: [ovs-dev] [patch_v4 1/6] Export packet_set_ipv6_addr()fordpdkdatapath.

On 1/27/17, 5:57 PM, "ovs-dev-boun...@openvswitch.org on behalf of Daniele Di Proietto" wrote: 2017-01-24 20:40 GMT-08:00 Darrell Ball : > Signed-off-by: Darrell Ball LGTM,

Re: [ovs-dev] [PATCH v4 1/1] doc: Remove experimental warning for DPDK.

On 6 February 2017 at 09:20, Ian Stokes wrote: > Remove the experimental warning tag in documentation regarding OVS deployed > with DPDK. > > Signed-off-by: Ian Stokes > diff --git a/README.rst b/README.rst > index f5cdaa5..afdd9bc 100644 > ---