I think you will have to get help from someone else. I'm no longer
deeply involved in OVS.
On Mon, Oct 11, 2021 at 01:20:03PM +, Saurabh Deokate wrote:
> Hi Ben, do we have any update on this ?
>
> On 08/09/21, 9:31 PM, "Saurabh Deokate" wrote:
>
> Hi Ben, do we have any update on thi
Hi Ben, do we have any update on this ?
On 08/09/21, 9:31 PM, "Saurabh Deokate" wrote:
Hi Ben, do we have any update on this issue ?
~Saurabh.
On 24/08/21, 11:21 AM, "Saurabh Deokate"
wrote:
Hi Ben, can you please help us understand why are we seeing these
retrying e
Hi Ben, do we have any update on this issue ?
~Saurabh.
On 24/08/21, 11:21 AM, "Saurabh Deokate" wrote:
Hi Ben, can you please help us understand why are we seeing these retrying
even after setting inactivity_probe to 0. Are we missing on some configuration
?
~Saurabh.
On 18
Hi Ben, can you please help us understand why are we seeing these retrying even
after setting inactivity_probe to 0. Are we missing on some configuration ?
~Saurabh.
On 18/08/21, 11:50 AM, "Saurabh Deokate" wrote:
Hi Ben,
I tested with latest OVS 2.16, which has your fix, even after
Hi Ben,
I tested with latest OVS 2.16, which has your fix, even after setting
inactivity_probe to 0, we are still seeing ovs retrying after every 5 sec.
Can you please help us with this ?
Here are the details -
root@ip-10-192-20-160:/home/ubuntu# ovs-vsctl --version
ovs-vsctl (Open vSwitch)
I just pushed the fixes to the repo, so it'll be released as part of the
next regular OVS release.
Building from a patch isn't any different from building any other way.
On Thu, Jul 01, 2021 at 06:19:08AM +, Saurabh Deokate wrote:
> Hi Ben,
>
> I have two questions,
> 1. When is this patch
Hi Ben,
I have two questions,
1. When is this patch going to be released ?
2. Do we have any documentation for building modules from patch?
On 28/06/21, 10:25 PM, "Ben Pfaff" wrote:
I recommend trying the patches that I posted:
https://urldefense.proofpoint.com/v2/url?u=https-3A__ma
I recommend trying the patches that I posted:
https://mail.openvswitch.org/pipermail/ovs-dev/2021-June/383783.html
https://mail.openvswitch.org/pipermail/ovs-dev/2021-June/383784.html
On Tue, Jun 15, 2021 at 07:24:06AM +, Saurabh Deokate wrote:
> Hi Ben,
>
> Here is the output for ovs-vsctl l
Hi Ben,
Any update on this ? Do you need any other details ?
~Saurabh.
On 15/06/21, 12:54 PM, "Saurabh Deokate" wrote:
Hi Ben,
Here is the output for ovs-vsctl list controller
[root@172-31-64-26-aws-eu-central-1c ~]# ovs-vsctl list controller
_uuid : eb56176a-ad32-4eb0-9cd
Hi Ben,
Here is the output for ovs-vsctl list controller
[root@172-31-64-26-aws-eu-central-1c ~]# ovs-vsctl list controller
_uuid : eb56176a-ad32-4eb0-9cd8-7ab3bd448a68
connection_mode : out-of-band
controller_burst_limit: []
controller_queue_size: []
controller_rate_limit: []
enable_async_messa
On Mon, Jun 07, 2021 at 02:51:58PM +, Saurabh Deokate wrote:
> Hi Team,
>
> We are seeing an issue in OVS 2.14.0 after moving from 2.8.0. We first set
> the controller on the bridge and then set inactivity probe for our controller
> to 0 to disable new connection attempts by ovs. After this
Hi Team,
We are seeing an issue in OVS 2.14.0 after moving from 2.8.0. We first set the
controller on the bridge and then set inactivity probe for our controller to 0
to disable new connection attempts by ovs. After this we start our controller
to serve request. But in the new version of OVS so
Hi,
We are seeing an issue in OVS 2.14.0 after moving from 2.8.0. We first set the
controller on the bridge and then set inactivity probe for our controller to 0
to disable new connection attempts by ovs. After this we start our controller
to serve request. But in the new version of OVS somehow
Hi,
We are seeing an issue in OVS 2.14.0 after moving from 2.8.0. We first set the
controller on the bridge and then set inactivity probe for our controller to 0
to disable new connection attempts by ovs. After this we start our controller
to serve request. But in the new version of OVS somehow
14 matches
Mail list logo
