This message was undeliverable due to the following reason(s):
Your message could not be delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.
Most lik
On Thu, Oct 27, 2016 at 11:51:42PM +, Bertrand Low wrote:
> Hi there,
>
> Has anyone noticed a "connection flapping" behaviour for the br-int bridge
> (used between openstack and opendaylight's netvirt module) when openvswitch
> is restarted? I've provided some details below.
>
> Scenario:
Hi there,
Has anyone noticed a "connection flapping" behaviour for the br-int bridge
(used between openstack and opendaylight's netvirt module) when openvswitch is
restarted? I've provided some details below.
Scenario:
- Opendaylight 3-node cluster running distribution-karaf-0.5.0-Bor
Switch too memmove(RtlMoveMemory) instead of copy and predefined allocated
buffer.
Currently if we receive a pop_vlan action, and the vlan tag is inside the
Ethernet frame(not in the net buffer list information) we change the frame
without checking if the it was a vlan tagged or not.
This patch c
This patch allows online compacting to be done under Windows.
To achieve the above we need to close all file handles before trying to
rename the file, switch from rename to MoveFileEx (because rename/MoveFile
fails if the destination exists), reopen the right type of log after the
rename.
If we c
Skip symlinks checks on Windows.
Signed-off-by: Alin Gabriel Serdean
---
tests/ovsdb-server.at | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/tests/ovsdb-server.at b/tests/ovsdb-server.at
index d04941b..df51f80 100644
--- a/tests/ovsdb-server.at
+++ b/tes
Add support for online compacting on Windows.
Also add a unit test for it
Alin Gabriel Serdean (2):
ovsdb windows: Allow online compacting
tests: windows ovsdb online compact
ovsdb/file.c | 56 +++
tests/ovsdb-server.at | 18 +
I thought we had set warnings to be treated as error. Appveyor didn¹t
catch this one either. Thanks for fixing this.
Acked-by: Sairam Venugopal
On 10/27/16, 12:20 PM, "Alin Serdean"
wrote:
>ofpbuf_const_initializer takes only two parameters see:
>
>https://urldefense.proofpoint.com/v2/url?u=h
Acked-by: Sairam Venugopal
On 10/27/16, 11:57 AM, "Alin Serdean"
wrote:
>'status' is of type 'NTSTATUS' and NlFillOvsMsgForNfGenMsg is of type
>bool.
>
>Signed-off-by: Alin Gabriel Serdean
>---
> datapath-windows/ovsext/Conntrack.c | 14 --
> 1 file changed, 8 insertions(+), 6 dele
Acked-by: Sairam Venugopal
On 10/27/16, 12:20 PM, "Alin Serdean"
wrote:
>Use bitwise comparison when checking flags set by the kernel for the
>device.
>
>Signed-off-by: Alin Gabriel Serdean
>---
> lib/netdev-windows.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/
This patch adds the offline compacting (ovsdb-tool compact) to be run on
Windows.
On Windows we are missing "--run" so in return we start ovsdb-server,
run the ovsdb-client dump command and after issue a command to the
ovsdb-server to close.
Also on Windows we do not check for symlinks, so skip t
ofpbuf_const_initializer takes only two parameters see:
https://github.com/openvswitch/ovs/blob/master/include/openvswitch/ofpbuf.h#L96
the compiler only gives the following warning:
lib/netdev-windows.c(229) : warning C4020: 'ofpbuf_const_initializer' :
too many actual parameters
which in resu
Use bitwise comparison when checking flags set by the kernel for the
device.
Signed-off-by: Alin Gabriel Serdean
---
lib/netdev-windows.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/netdev-windows.c b/lib/netdev-windows.c
index 423a00b..f5e809e 100644
--- a/lib/ne
'status' is of type 'NTSTATUS' and NlFillOvsMsgForNfGenMsg is of type bool.
Signed-off-by: Alin Gabriel Serdean
---
datapath-windows/ovsext/Conntrack.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/datapath-windows/ovsext/Conntrack.c
b/datapath-windows/ovsex
The purpose of this patch is to make the code more readable and
fix a static analyzer warning.
Signed-off-by: Alin Gabriel Serdean
---
datapath-windows/ovsext/Geneve.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/datapath-windows/ovsext/Geneve.c b/datapath-windows/ov
The purpose of this patch is to make the code more readable and
fix a static analyzer warning.
Signed-off-by: Alin Gabriel Serdean
---
datapath-windows/ovsext/Gre.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/datapath-windows/ovsext/Gre.c b/datapath-windows/ovsext/G
The purpose of this patch is to make the code more readable and
fix a static analyzer warning.
Signed-off-by: Alin Gabriel Serdean
---
datapath-windows/ovsext/Stt.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/datapath-windows/ovsext/Stt.c b/datapath-windows/ovsext/S
The purpose of this patch is to make the code more readable and
fix a static analyzer warning.
Signed-off-by: Alin Gabriel Serdean
---
datapath-windows/ovsext/Vxlan.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/datapath-windows/ovsext/Vxlan.c b/datapath-windows/ovse
OK I tried again - I think the tabs are OK, but not sure about the extra new
lines... if there's a problem I'll try one of the email clients.
Thnx :)
-Original Message-
From: Thadeu Lima de Souza Cascardo [mailto:casca...@redhat.com]
Sent: Thursday, October 27, 2016 5:21 PM
To: Waizel,
Fix adding a route with gateway failing
When adding a VXLAN tunnel that connects to a VTEP residing in a
different IP network, the tunnel source ip needs to be selected by
best fit (longest matching netmask), based on the destination VTEP
ip, and the specific route's gateway ip
From: itamarofek
This patch adds support for handeling a per-tunnel tunnel key in the
ovs-vtep and vtep-ctl.
The aim of this patch is to support the usage of hardware vtep switch as
an inter-cloud gateway, which is used to connect two separated l2 broadcast
domains
Requested-by: "Ofer Ben-Yacov
On Thu, Oct 27, 2016 at 02:08:13PM +, Waizel, Ariel wrote:
>
>
> When adding a VXLAN tunnel that connects to a VTEP residing in a
>
> different IP network, the tunnel source ip needs to be selected by
>
> best fit (longest matching netmask), based on the destination VTEP
>
> ip, and the sp
'dev->requested_{rxq,txq}_size' and 'dev->{rxq,txq}_size' are
relevant only for DPDK_DEV_ETH devices and should be skipped
in 'netdev_dpdk_get_config()' for other ports.
CC: Ciara Loftus
Fixes: b685696b8c81 ("netdev-dpdk: Allow configurable queue sizes for 'dpdk'
ports")
Signed-off-by: Ilya Max
When adding a VXLAN tunnel that connects to a VTEP residing in a
different IP network, the tunnel source ip needs to be selected by
best fit (longest matching netmask), based on the destination VTEP
ip, and the specific route's gateway ip.
A bug in ovs-router.c made the source ip to be decide
On Thu, Oct 27, 2016 at 01:33:35PM +, Waizel, Ariel wrote:
> No problem:
> > When adding a VXLAN tunnel that connects to a VTEP residing in a different
> > IP network, the tunnel source ip needs to be selected by best fit
> > (longest matching netmask), based on the destination VTEP ip,
> >
No problem:
> When adding a VXLAN tunnel that connects to a VTEP residing in a different
> IP network, the tunnel source ip needs to be selected by best fit
> (longest matching netmask), based on the destination VTEP ip,
> and the specific route's gateway ip.
>
> A bug in ovs-router.c made the
On Wed, Oct 26, 2016 at 02:05:22PM -0700, Pravin Shelar wrote:
> On Wed, Oct 26, 2016 at 2:55 AM, Thadeu Lima de Souza Cascardo
> wrote:
> > On Tue, Oct 25, 2016 at 08:21:55PM -0700, Pravin Shelar wrote:
> >> > The fallback option should already work, then. We can make sure during
> >> > testing
Bonjour Monsieur,madame
On m'appelle ADJOVI Gilles.je suis directeur du groupement d'orpailleurs
Busness metalor.
Ce groupement est créée en 1995 au BÉNIN en Afrique de l'Ouest. Elle a pour
objectif d'approvisionner les centre de bijouteries utilisateur du métal OR .Il
aide les bijoutiers da
The original message was received at Thu, 27 Oct 2016 13:04:40 +0530
from openvswitch.org [80.155.249.102]
- The following addresses had permanent fatal errors -
dev@openvswitch.org
___
dev mailing list
dev@openvswitch.org
http://openvswitch.o
29 matches
Mail list logo