Thanks Lucas for the patch:
It's good to update inactivity_probe via crm resource as we ideally use
ovn-nbtl/ovn-sbctl commands to do that since the value one chooses depends
on scale and can be different for everyone and we always tune it from
active node. Also what do you mean by multiple
On Thu, Jun 27, 2019 at 12:43 AM Numan Siddique wrote:
>
>
> On Thu, Jun 27, 2019 at 12:41 AM Ben Pfaff wrote:
>
>> On Wed, Jun 26, 2019 at 11:59:30AM +0100, lmart...@redhat.com wrote:
>> > From: Lucas Alvares Gomes
>> >
>> > This patch is enhacing the ovndb-servers.ocf script to handle
On Thu, Jun 27, 2019 at 12:41 AM Ben Pfaff wrote:
> On Wed, Jun 26, 2019 at 11:59:30AM +0100, lmart...@redhat.com wrote:
> > From: Lucas Alvares Gomes
> >
> > This patch is enhacing the ovndb-servers.ocf script to handle updates to
> > the inactive_probe_interval via pacemaker. For example, one
On Wed, Jun 26, 2019 at 11:59:30AM +0100, lmart...@redhat.com wrote:
> From: Lucas Alvares Gomes
>
> This patch is enhacing the ovndb-servers.ocf script to handle updates to
> the inactive_probe_interval via pacemaker. For example, one could run:
>
> $ sudo crm_resource --resource ovndb_servers
From: Lucas Alvares Gomes
This patch is enhacing the ovndb-servers.ocf script to handle updates to
the inactive_probe_interval via pacemaker. For example, one could run:
$ sudo crm_resource --resource ovndb_servers --set-parameter
inactive_probe_interval --parameter-value
To set a new
