Cool! Thanks!
On Mon, Jul 9, 2018 at 11:28 AM Ben Pfaff wrote:
> OK, that did it. I backported all three.
>
> On Mon, Jul 09, 2018 at 11:04:12AM -0700, aginwala wrote:
> > Hi Ben:
> >
> > I guess the cherry pick failed because of the dependency patch. Can you
> > port
OK, that did it. I backported all three.
On Mon, Jul 09, 2018 at 11:04:12AM -0700, aginwala wrote:
> Hi Ben:
>
> I guess the cherry pick failed because of the dependency patch. Can you
> port https://patchwork.ozlabs.org/patch/925566/ to branch-2.9 as its
> pre-req for these patches and apply
Hi Ben:
I guess the cherry pick failed because of the dependency patch. Can you
port https://patchwork.ozlabs.org/patch/925566/ to branch-2.9 as its
pre-req for these patches and apply above two on top of that. It would work
that way. Let me know further.
Regards,
On Thu, Jul 5, 2018 at
On Thu, Jun 21, 2018 at 01:29:52AM +0530, Numan Siddique wrote:
> On Sat, Jun 9, 2018 at 7:03 AM, aginwala wrote:
>
> > load balancer to manage ovndb clusters via pacemaker.
> >
> > This is will allow setting inactivity probe on the master node.
> > For pacemaker to manage ovndb resources via
It's better to replace "ovndb-servers" to "ovndb-servers.ocf" in the title.
Probably Ben will take care of that when applying the patch.
Acked-by: Han Zhou
On Fri, Jun 8, 2018 at 6:33 PM, aginwala wrote:
> load balancer to manage ovndb clusters via pacemaker.
>
> This is will allow setting
On Sat, Jun 9, 2018 at 7:03 AM, aginwala wrote:
> load balancer to manage ovndb clusters via pacemaker.
>
> This is will allow setting inactivity probe on the master node.
> For pacemaker to manage ovndb resources via LB, we skipped creating
> connection
> table and hence the inactivity probe
load balancer to manage ovndb clusters via pacemaker.
This is will allow setting inactivity probe on the master node.
For pacemaker to manage ovndb resources via LB, we skipped creating connection
table and hence the inactivity probe was getting set to 5000 by default.
In order to over-ride it we
