Re: [ovs-discuss] Question to OVN DB pacemaker script

Thanks for the output. It appears to be more complex than I thought before. It is good that the new slave doesn't listen on 6641, although I am not sure how is it achieved. I guess a stop has been triggered instead of simply demote, but I need to spend some time on the pacemaker state machine. And

Re: [ovs-discuss] Using --ovs with ovn-sbctl lflow-list

Oh, you're looking for an OpenFlow server. Use "ovs-vsctl set-controller". (Also, "tcp://IP" is not correct syntax for anything in OVS. The documentation explains the syntax.) On Fri, May 11, 2018 at 11:13:57PM +, Ankur Sharma wrote: > Hi Ben, > > Thanks for pointers. > > ovsdb-server

Re: [ovs-discuss] Using --ovs with ovn-sbctl lflow-list

Hi Ben, Thanks for pointers. ovsdb-server understands openflow? We tried starting a server on ovsdb-server and now connection resets. i.e we executed following command: ovn-sbctl --ovs=tcp://SERVER_IP lflow_list And this time connection resets, packet capture show that as soon as sbctl sends

Re: [ovs-discuss] Question to OVN DB pacemaker script

Sure: *VIP_ip* = 10.149.4.252 *LB IP* = 10.149.0.40 *slave netstat where it syncs from master LB VIP IP * #netstat -an | grep 6641 tcp0 0 10.169.129.34:47426 10.149.4.252:6641 ESTABLISHED tcp0 0 10.169.129.34:47444 10.149.4.252:6641 ESTABLISHED *Slave OVS:, *

Re: [ovs-discuss] Question to OVN DB pacemaker script

Thanks Han for more suggestions: I did test failover by gracefully stopping pacemaker+corosync on master node along with crm move and it works as expected too as crm move is triggering promote of new master and hence the new master gets elected along with slave getting demoted as expected to

Re: [ovs-discuss] ovs-ofctl mod-port doesn't work with ports in network namespaces

> On May 11, 2018, at 3:00 AM, Jakub Libosvar wrote: > > Hi all, > it seems I hit a bug when trying to implement a fix in OpenStack Neutron > that uses heavily network namespaces with OVS internal ports in them. > > Ports attached to OVS bridge that are placed in network

Re: [ovs-discuss] Incremental perf results

On Fri, May 11, 2018 at 7:58 AM, Mark Michelson wrote: > On 05/10/2018 08:33 PM, Han Zhou wrote: > >> >> >> On Wed, May 9, 2018 at 12:21 PM, Mark Michelson > > wrote: >> >> On 05/07/2018 08:29 AM, Mark Michelson wrote: >>

Re: [ovs-discuss] Geneve and IPv6

On 5/10/2018 8:08 PM, Ben Pfaff wrote: On Thu, May 10, 2018 at 05:54:30PM -0700, Gregory Rose wrote: On 5/1/2018 6:53 PM, Ben Pfaff wrote: Hi Greg. We've had multiple reports now that Geneve kernel-based tunnels do not work in Open vSwitch if IPv6 is not enabled. Do you have an idea whether

Re: [ovs-discuss] Incremental perf results

On 05/10/2018 08:33 PM, Han Zhou wrote: On Wed, May 9, 2018 at 12:21 PM, Mark Michelson > wrote: On 05/07/2018 08:29 AM, Mark Michelson wrote: On 05/04/2018 04:15 PM, Han Zhou wrote: On Thu, May 3, 2018 at 10:49

[ovs-discuss] ovs-ofctl mod-port doesn't work with ports in network namespaces

Hi all, it seems I hit a bug when trying to implement a fix in OpenStack Neutron that uses heavily network namespaces with OVS internal ports in them. Ports attached to OVS bridge that are placed in network namespace can't have their status changed using 'ovs-ofctl mod-port' command. Steps to