Re: [ovs-dev] Can we use ovs to implement load balancer by openflow?

On Mon, Feb 27, 2017 at 7:42 PM, Yang, Yi Y wrote: > > Hi, all > > Can we use ovs to implement load balancer? Our target is to let ovs distribute the traffic to different service VMs based on 5 tuple (src ip, dst ip, src port, dst port, transport protocol). Yes. Try: man

Re: [ovs-dev] Memory pool issue on delete and re-add of DPDK ports with jumbo MTU >1894

Hi Mark, Is there any patch I can expect for this issue? On Tue, Feb 21, 2017, 7:28 PM Kapil Adhikesavalu wrote: > Hi Mark, > > Thanks for the detailed analysis, i will wait for further updates. > > Btw on the mailing list, i seem to have clicked 'reply' instead of >

[ovs-dev] Can we use ovs to implement load balancer by openflow?

Hi, all Can we use ovs to implement load balancer? Our target is to let ovs distribute the traffic to different service VMs based on 5 tuple (src ip, dst ip, src port, dst port, transport protocol). ___ dev mailing list d...@openvswitch.org

Re: [ovs-dev] [PATCH] Support multiple logical routing port configuration "redirect-chassis" on a distributed router

Hi Mickey, Thanks for review. This is a quick preliminary review. I will review this in more detail tomorrow afternoon. On Mon, Feb 27, 2017 at 5:12 AM, Guoshuai Li > wrote: The main application scenario of this patch is that the user flow

Re: [ovs-dev] [PATCH] FAQ: Update kernel support info.

Forgot to add your ack to commit, sorry! Jarno > On Feb 27, 2017, at 5:49 PM, Justin Pettit wrote: > > >> On Feb 27, 2017, at 5:45 PM, Jarno Rajahalme wrote: >> >> OVS 2.7 works with Linux kernels 3.10-4.9. >> >> Signed-off-by: Jarno Rajahalme

Re: [ovs-dev] [PATCH] FAQ: Update kernel support info.

Thanks, Pushed to master and cherry-picked to branch-2.7. Jarno > On Feb 27, 2017, at 5:49 PM, Justin Pettit wrote: > > >> On Feb 27, 2017, at 5:45 PM, Jarno Rajahalme wrote: >> >> OVS 2.7 works with Linux kernels 3.10-4.9. >> >> Signed-off-by: Jarno

Re: [ovs-dev] [PATCH] FAQ: Update kernel support info.

> On Feb 27, 2017, at 5:45 PM, Jarno Rajahalme wrote: > > OVS 2.7 works with Linux kernels 3.10-4.9. > > Signed-off-by: Jarno Rajahalme Acked-by: Justin Pettit --Justin ___ dev mailing list

[ovs-dev] [PATCH] FAQ: Update kernel support info.

OVS 2.7 works with Linux kernels 3.10-4.9. Signed-off-by: Jarno Rajahalme --- Documentation/faq/releases.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/faq/releases.rst b/Documentation/faq/releases.rst index 319c2d7..118c88d 100644 ---

Re: [ovs-dev] [branch-2.7] Set release date for 2.7.0.

> On Feb 24, 2017, at 4:32 AM, Flavio Leitner wrote: > > > Hi, > > We pushed 2.7 through our testing and found no issues. Thank you for doing that! I hope to release today. Jarno is just checking the supported kernel versions, and then we'll send it out. --Justin

[ovs-dev] [PATCH 1/3] datapath-windows: Add support for NAT in conntrack

Add support for parsing netlink attributes related to NAT in conntrack. Signed-off-by: Yin Lin --- datapath-windows/ovsext/Conntrack.c | 73 +++-- datapath-windows/ovsext/Conntrack.h | 17 + datapath-windows/ovsext/Flow.c | 4 +- 3

Re: [ovs-dev] [PATCH 1/3] datapath-windows: Add support for NAT in conntrack

Not sure why author field is dropped during "git send-email". But the original author of this patch is "Anand Kumar". Kudos to Anand! Thanks, Yin On Mon, Feb 27, 2017 at 2:13 PM, Yin Lin wrote: > Add support for parsing netlink attributes related to NAT

[ovs-dev] [PATCH 3/3] datapath-windows: NAT integration with conntrack

Signed-off-by: Yin Lin --- datapath-windows/ovsext/Actions.c | 158 ++--- datapath-windows/ovsext/Actions.h | 77 ++ datapath-windows/ovsext/Conntrack.c| 178 -

[ovs-dev] [PATCH 2/3] datapath-windows: Add NAT module in conntrack

Signed-off-by: Yin Lin --- datapath-windows/automake.mk| 2 + datapath-windows/ovsext/Conntrack-nat.c | 436 datapath-windows/ovsext/Conntrack-nat.h | 39 +++ 3 files changed, 477 insertions(+) create mode 100644

Re: [ovs-dev] [PATCH 2/2] rhel-systemd: Document systemd behavior

On Mon, Feb 20, 2017 at 9:42 AM, Flavio Leitner wrote: > On Wed, Feb 08, 2017 at 05:28:22PM +0100, Eelco Chaudron wrote: > > This is a follow up patch to document the systemd behavior including > > the change introduced by the "rhel-systemd: Restart openvswitch > > service if

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

On Tue, Feb 7, 2017 at 7:38 AM, 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] ovn-controller: Assign ct_zone id to local datapaths instead of lports

On Fri, Feb 24, 2017 at 1:10 AM, Numan Siddique wrote: > ​​ > > > On Thu, Feb 23, 2017 at 11:06 PM, Mickey Spiegel > wrote: > > > > > On Thu, Feb 23, 2017 at 6:04 AM, wrote: > > > >> From: Numan Siddique >

Re: [ovs-dev] [PATCH] Support multiple logical routing port configuration "redirect-chassis" on a distributed router

This is a quick preliminary review. I will review this in more detail tomorrow afternoon. On Mon, Feb 27, 2017 at 5:12 AM, Guoshuai Li wrote: > The main application scenario of this patch is that the user flow wants to > different destination addresses through different

Re: [ovs-dev] [PATCH v2] msi: add ovs-vswitchd trigger info

Thanks! I created an issue for it under: https://github.com/openvswitch/ovs-issues/issues/127 so it can be tracked. I will try to send a patch for it soon. Alin. From: Guru Shetty [mailto:g...@ovn.org] Sent: Monday, February 27, 2017 8:43 PM To: Sairam Venugopal Cc: Alin

Re: [ovs-dev] [PATCH v2] msi: add ovs-vswitchd trigger info

On 27 February 2017 at 10:23, Sairam Venugopal wrote: > Thanks for sending this over. I was able to verify that ovs ports were > still retained after a reboot. > It will however be good to add the command to the documentation for folks > who don’t use the MSI. > Applied to

Re: [ovs-dev] [PATCH v2] msi: add ovs-vswitchd trigger info

Thanks for sending this over. I was able to verify that ovs ports were still retained after a reboot. It will however be good to add the command to the documentation for folks who don’t use the MSI. Acked-by: Sairam Venugopal On 2/21/17, 1:50 PM,

[ovs-dev] RV: OVS Installation problems on Windows

Hello everybody, I am Sergio, a Research Engineer at IMDEA Networks (http://www.networks.imdea.org/). Currently, we are working on SDN and Virtualization projects. I would need your help to solve an important issue that is blocking one of the projects. In particular, I am having some problems

Re: [ovs-dev] OVS Installation problems on Windows

Hi Sergio, Email attachments usually get dropped by the server. Looking at the output you sent, it seems that cccl can't see cl.exe (Visual Studio compiler). Can you make sure the `cl.exe` and `link.exe` are available via env variables and pointing to the right location? Thanks, Alin. >

[ovs-dev] OVS Installation problems on Windows

Hello everybody, I am Sergio, a Research Engineer at IMDEA Networks (http://www.networks.imdea.org/). Currently, we are working on SDN and Virtualization projects. I would need your help to solve an important issue that is blocking one of the projects. In particular, I am having some problems

[ovs-dev] Proposed OVN live migration workflow

This is a proposed update to the VM live migration workflow with OVN. Currently, when doing live migration, you must not add the iface-id to the port for the destination VM until migration is complete. Otherwise, while migration is in progress, ovn-controller on two different chassis will fight

[ovs-dev] -fomit-frame-pointer in OVS

Hi, Currently, OVS seems to disable frame pointer (-fomit-frame-pointer) in non-debug builds. While I do know this is a common optimization, it makes run-time profiling substantially less straightforward. So I wonder, if there are any benchmarks showing the effect of omitting frame pointer,

Re: [ovs-dev] [PATCH] netdev-dpdk: Fix mempool segfault.

>> > >> >The dpdk_mp_get() function can return a NULL pointer which leads to a >> >segfault when a mempool cannot be created. The lack of a return value >> >check for the function netdev_dpdk_mempool_configure() when called in >> >netdev_dpdk_reconfigure() can result in a segfault also as a NULL

Re: [ovs-dev] [PATCH] netdev-dpdk: Fix mempool segfault.

> > > >The dpdk_mp_get() function can return a NULL pointer which leads to a > >segfault when a mempool cannot be created. The lack of a return value > >check for the function netdev_dpdk_mempool_configure() when called in > >netdev_dpdk_reconfigure() can result in a segfault also as a NULL >

[ovs-dev] [PATCH] Support multiple logical routing port configuration "redirect-chassis" on a distributed router

The main application scenario of this patch is that the user flow wants to different destination addresses through different external networks. This scenario requires a distributed route to be associated with multiple external network logical switches. In a distributed router, the NAT logical

Re: [ovs-dev] [PATCH] netdev-dpdk: Fix mempool segfault.

> >The dpdk_mp_get() function can return a NULL pointer which leads to a >segfault when a mempool cannot be created. The lack of a return value >check for the function netdev_dpdk_mempool_configure() when called in >netdev_dpdk_reconfigure() can result in a segfault also as >a NULL pointer for the

[ovs-dev] inbox is bijna voorbij uw opslaglimiet

inbox is bijna voorbij uw opslaglimiet. Het zal niet in staat zijn om te verzenden en ontvangen van e-mail als de limiet en je e-mailaccount zal worden opgehangen aan onze server. Om dit probleem te voorkomen, moet u deze opnieuw valideren van de mailbox quota