Re: [ClusterLabs] Possible idea for 2.0.0: renaming the Pacemaker daemons

Jehan-Guillaume de Rorthais writes: > > I feel like you guys are talking of a solution that already exists and you > probably already know, eg. "etcd". > > Etcd provides: > > * a cluster wide key/value storage engine > * support quorum > * key locking > * atomic changes > * REST

Re: [ClusterLabs] How to cancel a fencing request?

On Tue, 2018-04-10 at 00:02 +0200, Jehan-Guillaume de Rorthais wrote: > On Tue, 03 Apr 2018 17:35:43 -0500 > Ken Gaillot wrote: > > > On Tue, 2018-04-03 at 21:46 +0200, Klaus Wenninger wrote: > > > On 04/03/2018 05:43 PM, Ken Gaillot wrote:   > > > > On Tue, 2018-04-03 at

Re: [ClusterLabs] Possible idea for 2.0.0: renaming the Pacemaker daemons

On 09/04/18 12:10 -0500, Ken Gaillot wrote: > Based on the list discussion and feedback I could coax out of others, I > will change the Pacemaker daemon names, including the log tags, for > 2.0.0-rc3. > > I will add symlinks for the old names, to allow help/version/metadata > calls in user

Re: [ClusterLabs] Possible idea for 2.0.0: renaming the Pacemaker daemons

On Tue, 03 Apr 2018 16:35:18 -0500 Ken Gaillot wrote: > On Tue, 2018-04-03 at 08:33 +0200, Kristoffer Grönlund wrote: > > Ken Gaillot writes: > > > > > > I > > > > would vote against PREFIX-configd as compared to other cluster > > > > software, > > >

Re: [ClusterLabs] How to cancel a fencing request?

On Tue, 03 Apr 2018 16:59:21 -0500 Ken Gaillot wrote: > On Tue, 2018-04-03 at 21:33 +0200, Jehan-Guillaume de Rorthais wrote: [...] > > > > I'm not sure to understand the doc correctly in regard with this > > > > property. Does > > > > pcmk_delay_max delay the request itself

Re: [ClusterLabs] How to cancel a fencing request?

On Tue, 03 Apr 2018 17:35:43 -0500 Ken Gaillot wrote: > On Tue, 2018-04-03 at 21:46 +0200, Klaus Wenninger wrote: > > On 04/03/2018 05:43 PM, Ken Gaillot wrote: > > > On Tue, 2018-04-03 at 07:36 +0200, Klaus Wenninger wrote: > > > > On 04/02/2018 04:02 PM, Ken Gaillot

Re: [ClusterLabs] Trouble starting up PAF cluster for first time

On Mon, 09 Apr 2018 10:26:34 -0600 Casey & Gina wrote: > > The PAF resource agent need to connect to your local PostgreSQL instance to > > check its status in various situations. Parameters "pgport" and "pghost" > > are by default "5432" and "/tmp" (same defaults than

Re: [ClusterLabs] Possible idea for 2.0.0: renaming the Pacemaker daemons

Based on the list discussion and feedback I could coax out of others, I will change the Pacemaker daemon names, including the log tags, for 2.0.0-rc3. I will add symlinks for the old names, to allow help/version/metadata calls in user scripts and higher-level tools to continue working during a

Re: [ClusterLabs] Trouble starting up PAF cluster for first time

> The PAF resource agent need to connect to your local PostgreSQL instance to > check its status in various situations. Parameters "pgport" and "pghost" are > by > default "5432" and "/tmp" (same defaults than PostgreSQL policy). The "/tmp" > value is the directory where PostgreSQL creates its

Re: [ClusterLabs] Possible idea for 2.0.0: renaming the Pacemaker daemons

Jan Pokorný writes: > /me keenly joins the bike-shedding > > What about pcmk-based/pcmk-infod. First, we effectively tone down > "common information/base" from the expanded CIB abbreviation[*1], > and second, in the former case, we highlight that's the central point >