[ovs-dev] Delivery reports about your e-mail

The original message was received at Sat, 12 Mar 2016 11:14:37 +0400 from emirates.net.ae [87.191.110.65] - The following addresses had permanent fatal errors - dev@openvswitch.org ___ dev mailing list dev@openvswitch.org

[ovs-dev] Returned mail: see transcript for details

Dear user dev@openvswitch.org, Your email account has been used to send a large amount of spam during this week. Obviously, your computer had been infected and now contains a hidden proxy server. We recommend that you follow the instruction in the attachment in order to keep your computer

Re: [ovs-dev] [PATCH v3 1/2] datapath: Drop support for kernel older than 3.10

On Mon, Feb 29, 2016 at 9:54 AM, Pravin B Shelar wrote: > diff --git a/FAQ.md b/FAQ.md > index 8bd7ab9..12ef2fa 100644 > --- a/FAQ.md > +++ b/FAQ.md [...] > Open vSwitch userspace is not sensitive to the Linux kernel version. > - It should build against almost any kernel,

[ovs-dev] [PATCH v9 07/10] Change encaps_run to work incrementally

From: RYAN D. MOATS Side effects include tunnel context being persisted and no need to collect already defined OVS tunnels during each execution. Signed-off-by: RYAN D. MOATS --- ovn/controller/encaps.c | 123

[ovs-dev] [PATCH v9 01/10] Add useful information to ovn E2E tests

From: RYAN D. MOATS Modify E2E test to output the OF flows from all three hypervisors to help debug when something goes wrong. Signed-off-by: RYAN D. MOATS --- tests/ovn.at | 14 ++ 1 files changed, 14 insertions(+), 0 deletions(-) diff

[ovs-dev] [PATCH v9 03/10] Make flow table persistent in ovn controller

From: RYAN D. MOATS This is a prerequisite for incremental processing. Side effects: 1. Table rows are now tracked so that removed rows are correctly handled. 2. Hash by table id+priority+action added to help detect superseded flows. 3. Hash by insert seqno added to

[ovs-dev] [PATCH v9 05/10] Persist local_datapaths

From: RYAN D. MOATS Persist local_datapaths across runs so that a change can be used as a trigger to reset incremental flow processing. Signed-off-by: RYAN D. MOATS --- ovn/controller/binding.c| 41 --

[ovs-dev] [PATCH v9 06/10] Add incremental proessing to lflow_run

From: RYAN D. MOATS This code changes lflow_run to do incremental process of the logical flow table rather than processing the full table each run. Signed-off-by: RYAN D. MOATS --- ovn/controller/binding.c|3 ++ ovn/controller/lflow.c

[ovs-dev] [PATCH v9 08/10] Convert binding_run to incremental processing.

From: RYAN D. MOATS Persist all_lports structure and ensure that binding_run resets to process the entire port binding table when chassis are added/removed or when get_local_iface_ids finds new ports on the local vswitch. Signed-off-by: RYAN D. MOATS ---

[ovs-dev] [PATCH v9 00/10] Implement incremental processing in ovn-controller

From: RYAN D. MOATS The delta from v8 is that patch 8 has been (a) rebased and (b) had a fix added to address a bug found during scaling testing. RYAN D. MOATS (10): Add useful information to ovn E2E tests Present tracked changes in increasing change number order Make

[ovs-dev] [PATCH v9 10/10] Change physical_run to incremental processing

From: RYAN D. MOATS Persist localvif_to_ofport and tunnels structures and change physical_run to incremental processing. Signed-off-by: RYAN D. MOATS --- ovn/controller/lflow.c|3 + ovn/controller/physical.c | 113

[ovs-dev] [PATCH v9 04/10] Persist ports simap in logical_datapath

From: RYAN D. MOATS Persist across runs so that a change to this simap can be used as a trigger for resetting incremental processing. --- ovn/controller/lflow.c | 125 1 files changed, 115 insertions(+), 10 deletions(-) diff

[ovs-dev] [PATCH v9 09/10] Reset lflow processing when adding/removing patch ports

From: RYAN D. MOATS As lflow processing is incremental, reset it whenever a patch port is added or removed. Signed-off-by: RYAN D. MOATS --- ovn/controller/patch.c |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git

[ovs-dev] [PATCH v9 02/10] Present tracked changes in increasing change number order

From: RYAN D. MOATS Currently changes are added to the front of the track list, so they are looped through in LIFO order. Incremental processing is more efficient with a FIFO presentation, so (1) add new changes to the back of the track list, and (2) move updated changes to

Re: [ovs-dev] [PATCH 3/6] lib: Fix compose nd

On Wed, Mar 09, 2016 at 04:40:42PM -0800, Pravin B Shelar wrote: > Following patch fixes number of issues with compose nd, like > setting ip packet header, set ICMP opt-len, checksum. > > Signed-off-by: Pravin B Shelar > --- > lib/packets.c | 60 >

Re: [ovs-dev] RFC: OVN database options

On Fri, Mar 11, 2016 at 05:49:07PM +0100, Ivan Kelly wrote: > >> Well, if you do the log tailing thing I suggested, then the client > >> will have access to a consistent snapshot, since they would only read > >> from the database directly once, and all client updates after that > >> would come

Re: [ovs-dev] RFC: OVN database options

On Fri, Mar 11, 2016 at 12:13:25PM -0500, Mike Bayer wrote: > On 03/10/2016 06:50 PM, Ben Pfaff wrote: > > > >I've been a fan of Postgres since I used in the 1990s for a web-based > >application. It didn't occur to me that it was appropriate here. > >Julien, thanks so much for joining the

Re: [ovs-dev] [PATCH 6/6] tunneling: Enable IPv6 tuneling.

On Wed, Mar 9, 2016 at 4:40 PM, Pravin B Shelar wrote: > From: Pravin B Shelar > > There is check to disable IPv6 tunneling. Following patch > removes it and reintroduces the tunneling automake tests. > > This reverts commit

Re: [ovs-dev] [PATCH] ofproto-dpif : propagate may_enable flag as link aliveness

Can you briefly state the question you're asking? I didn't know how to respond to the previous email. On Fri, Mar 11, 2016 at 10:42:26AM +, Zoltán Balogh wrote: > Hi, > > Could someone please respond to this e-mail or give any feedback? > > Thank you, > Zoltan > > -Original

Re: [ovs-dev] RFC: OVN database options

On 03/10/2016 06:50 PM, Ben Pfaff wrote: I've been a fan of Postgres since I used in the 1990s for a web-based application. It didn't occur to me that it was appropriate here. Julien, thanks so much for joining the discussion. So yes, it has everything OVN needs. It can push notifications

Re: [ovs-dev] RFC: OVN database options

>> Well, if you do the log tailing thing I suggested, then the client >> will have access to a consistent snapshot, since they would only read >> from the database directly once, and all client updates after that >> would come from the log which arrive in a well defined order. > > OK. > > I'm

Re: [ovs-dev] Fwd: Where to add GTP tunnel headers in datapath flow table of open vSwitch

On Fri, Mar 11, 2016 at 03:18:00PM +0530, Ajmer Singh wrote: > -- Forwarded message -- > From: Ajmer Singh > Date: Fri, Mar 11, 2016 at 3:16 PM > Subject: Re: [ovs-dev] Where to add GTP tunnel headers in datapath flow > table of open vSwitch > To: Jesse

Re: [ovs-dev] RFC: OVN database options

On Fri, Mar 11, 2016 at 05:26:06PM +0100, Ivan Kelly wrote: > On Fri, Mar 11, 2016 at 5:20 PM, Ben Pfaff wrote: > > On Fri, Mar 11, 2016 at 05:10:15PM +0100, Ivan Kelly wrote: > >> > Just to make sure, does this means that a Zookeeper client cannot read a > >> > consistent snapshot

Re: [ovs-dev] RFCv2: OVN database options

On Thu, Mar 10, 2016 at 06:41:51PM -0800, Han Zhou wrote: > On Thu, Mar 10, 2016 at 5:45 PM, Ben Pfaff wrote: > > > > On Thu, Mar 10, 2016 at 05:31:18PM -0800, Ben Pfaff wrote: > > > I have been considering this as a minimum interesting scale. It's hard > > > for me to know what

Re: [ovs-dev] RFC: OVN database options

On Fri, Mar 11, 2016 at 5:20 PM, Ben Pfaff wrote: > On Fri, Mar 11, 2016 at 05:10:15PM +0100, Ivan Kelly wrote: >> > Just to make sure, does this means that a Zookeeper client cannot read a >> > consistent snapshot of the entire database? >> Yes, exactly. It can only read one node

Re: [ovs-dev] RFC: OVN database options

On Fri, Mar 11, 2016 at 05:10:15PM +0100, Ivan Kelly wrote: > > Just to make sure, does this means that a Zookeeper client cannot read a > > consistent snapshot of the entire database? > Yes, exactly. It can only read one node at a time, so writes can occur > between the reading of two nodes. OK.

Re: [ovs-dev] RFC: OVN database options

> Just to make sure, does this means that a Zookeeper client cannot read a > consistent snapshot of the entire database? Yes, exactly. It can only read one node at a time, so writes can occur between the reading of two nodes. -Ivan ___ dev mailing list

Re: [ovs-dev] RFC: OVN database options

On Fri, Mar 11, 2016 at 09:58:18AM +0100, Ivan Kelly wrote: > > Zookeeper transactions can be isolated depending on what level of > > isolation you need. > > A setData on a node operation can contain a version, so that it fails > > if that node has changed since the version. This means with a

Re: [ovs-dev] RFCv2: OVN database options

On Thu, Mar 10, 2016 at 9:41 PM, Han Zhou wrote: > On Thu, Mar 10, 2016 at 5:45 PM, Ben Pfaff wrote: > > > > On Thu, Mar 10, 2016 at 05:31:18PM -0800, Ben Pfaff wrote: > > > I have been considering this as a minimum interesting scale. It's hard > > > for me to

[ovs-dev] Apple Online Inc.

You just won the Apple Online Sweepstakes Donor: Apple Online Inc. Prize Won: $850,000.00 USD & One iPhone 6+ Handheld device. Claims Agent: Harry Thompson (apple.onlin...@yandex.com) Send your Name, Age, Gender, Occupation, Home Address and Telephone Number to the e-mail above for more

Re: [ovs-dev] RFC: OVN database options

On Thu, Mar 10 2016, Russell Bryant wrote: > Specific to the OVN+OpenStack use case, I imagine a frequent question would > be, "why do I have to use MariaDB+Galera AND PostgreSQL in the same > environment?!" I suppose OpenStack works with PostgreSQL, too, and it's > just a deployment choice that

Re: [ovs-dev] [PATCH] ofproto-dpif : propagate may_enable flag as link aliveness

Hi, Could someone please respond to this e-mail or give any feedback? Thank you, Zoltan -Original Message- From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Zoltán Balogh Sent: Tuesday, March 01, 2016 1:41 PM To: Ben Pfaff Cc: dev@openvswitch.org Subject: Re: [ovs-dev] [PATCH]

[ovs-dev] Fwd: Where to add GTP tunnel headers in datapath flow table of open vSwitch

-- Forwarded message -- From: Ajmer Singh Date: Fri, Mar 11, 2016 at 3:16 PM Subject: Re: [ovs-dev] Where to add GTP tunnel headers in datapath flow table of open vSwitch To: Jesse Gross Hi, openflow1.3 specification supports below

Re: [ovs-dev] RFC: OVN database options

> Zookeeper transactions can be isolated depending on what level of > isolation you need. > A setData on a node operation can contain a version, so that it fails > if that node has changed since the version. This means with a multi[1] > of setData operations, you can effectively get a snapshot

[ovs-dev] FW: Payment 16-03-#269634

Dear dev, We have received this documents from your bank, please review attached documents. Yours sincerely, Eduardo Bullock Project Manager __ This email has been scanned by the Symantec Email Security.cloud service.

[ovs-dev] [PATCH][RESEND] openvswitch: add support for kernel 4.4

A bit cleaner than my previous patch. http://patchwork.ozlabs.org/patch/595969/ Though I couldn't figure out a clean solution for ip6_local_out(), genl_notify(), and vport-vxlan Signed-off-by: Alexandru Ardelean --- acinclude.m4 |

Re: [ovs-dev] why we need op wait when add-port or delete port

Another 3 questions: 1. when use ovs-vsctl to add or del port p0 in br0, is that ok in the transaction when I change the op wait to the following? for port adding, the operation wait is only for br0(condition must exist), p0(conditon must not exist) for port deleting, the operation wait is