Re: [ovs-dev] [PATCH ovn] controller: disable OpenFlow inactivity probing

Thanks Numan! > On 2 Nov 2023, at 23:44, Numan Siddique wrote: > > On Fri, Sep 22, 2023 at 2:40 PM Han Zhou > wrote: >> >> On Mon, Sep 11, 2023 at 7:31 AM Vladislav Odintsov >> wrote: >>> >>> Hi Dumitru, >>> >>> if eventually this patch got merged, please remove next

Re: [ovs-dev] [PATCH ovn] controller: disable OpenFlow inactivity probing

On Fri, Sep 22, 2023 at 2:40 PM Han Zhou wrote: > > On Mon, Sep 11, 2023 at 7:31 AM Vladislav Odintsov > wrote: > > > > Hi Dumitru, > > > > if eventually this patch got merged, please remove next lines from its > commit message: > > > > "Disablement for ovs-vswitchd -> ovn-controller OF

Re: [ovs-dev] [PATCH ovn] controller: disable OpenFlow inactivity probing

On Mon, Sep 11, 2023 at 7:31 AM Vladislav Odintsov wrote: > > Hi Dumitru, > > if eventually this patch got merged, please remove next lines from its commit message: > > "Disablement for ovs-vswitchd -> ovn-controller OF inacivity probing will > be done in the next patch." > > Unfortunately I was

Re: [ovs-dev] [PATCH ovn] controller: disable OpenFlow inactivity probing

Hi Dumitru, if eventually this patch got merged, please remove next lines from its commit message: "Disablement for ovs-vswitchd -> ovn-controller OF inacivity probing will be done in the next patch." Unfortunately I was unsuccessful in removing these probing direction (default 60s). Maybe

Re: [ovs-dev] [PATCH ovn] controller: disable OpenFlow inactivity probing

On 9/11/23 14:54, Dumitru Ceara wrote: > On 6/14/23 20:02, Vladislav Odintsov wrote: >> Hi Mark, >> >> thanks for taking time to look on this! >> >> Your point with a hung OVS is really an interesting case. >> >> From one hand it’s a possible situation, and from another I guess it’s much >>

Re: [ovs-dev] [PATCH ovn] controller: disable OpenFlow inactivity probing

On 6/14/23 20:02, Vladislav Odintsov wrote: > Hi Mark, > > thanks for taking time to look on this! > > Your point with a hung OVS is really an interesting case. > > From one hand it’s a possible situation, and from another I guess it’s much > higher probability for OVS to be busy by some other

Re: [ovs-dev] [PATCH ovn] controller: disable OpenFlow inactivity probing

Hi Mark, thanks for taking time to look on this! Your point with a hung OVS is really an interesting case. From one hand it’s a possible situation, and from another I guess it’s much higher probability for OVS to be busy by some other work rather than to hang in a loop. In my installation the

Re: [ovs-dev] [PATCH ovn] controller: disable OpenFlow inactivity probing

Hi, Thanks for linking the email thread, since I had the exact same concern that Numan did about detecting if ovs-vswitchd goes down. It sounds like because of the nature of unix sockets, this disconnection is still detected by OVN and failover can occur as expected. But what about if

[ovs-dev] [PATCH ovn] controller: disable OpenFlow inactivity probing

OpenFlow connection is established over unix socket, which is a reliable connection and doesn't require additional probing. With this patch openflow probing in ovn-controller -> ovs-vswitchd direction is disabled for all three connections: - OF flows management connection, - OF features