Re: [ClusterLabs] standby and unstandby commands

2016-12-01 Thread Jan Pokorný
On 29/11/16 08:24 +0100, Ulrich Windl wrote: > Some servers first fork and exit, virtually being successful > immediately, while the child (the "server loop") could die a moment > later. Finding the perfect time to wait for the server dying is kind > of black magic ;-) That's exactly why I thing

[ClusterLabs] @ClusterLabs/devel COPR with new pacemaker (Was: Pacemaker 1.1.16 released)

2016-12-01 Thread Jan Pokorný
On 30/11/16 14:05 -0600, Ken Gaillot wrote: > ClusterLabs is proud to announce the latest release of the Pacemaker > cluster resource manager, version 1.1.15. The source code is available at: > > https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.16 In the same vein as recent

Re: [ClusterLabs] Pacemaker 1.1.16 released

2016-12-01 Thread Jehan-Guillaume de Rorthais
Le 1 décembre 2016 17:39:45 GMT+01:00, Ken Gaillot a écrit : >On 12/01/2016 10:13 AM, Jehan-Guillaume de Rorthais wrote: >> On Wed, 30 Nov 2016 14:05:19 -0600 >> Ken Gaillot wrote: >> >>> ClusterLabs is proud to announce the latest release of the

Re: [ClusterLabs] Pacemaker 1.1.16 released

2016-12-01 Thread Ken Gaillot
On 12/01/2016 10:13 AM, Jehan-Guillaume de Rorthais wrote: > On Wed, 30 Nov 2016 14:05:19 -0600 > Ken Gaillot wrote: > >> ClusterLabs is proud to announce the latest release of the Pacemaker >> cluster resource manager, version 1.1.15. > > 1.1.6 I guess ;) Whoops! Well

Re: [ClusterLabs] Pacemaker 1.1.16 released

2016-12-01 Thread Jehan-Guillaume de Rorthais
On Wed, 30 Nov 2016 14:05:19 -0600 Ken Gaillot wrote: > ClusterLabs is proud to announce the latest release of the Pacemaker > cluster resource manager, version 1.1.15. 1.1.6 I guess ;) But congrats anyway ! > * Previously, the OCF_RESKEY_CRM_meta_notify_active_*

Re: [ClusterLabs] Antw: Re: Set a node attribute for multiple nodes with one command

2016-12-01 Thread Ken Gaillot
On 12/01/2016 06:04 AM, Kostiantyn Ponomarenko wrote: > OK, now I see. I still have a few questions. > 1. Is there a good reason to not remove the attribute totally if it > is "deleted"? We do this for two reasons: 1. You can "delete" an attribute for just one node, while leaving it on other

Re: [ClusterLabs] ocf:heartbeat:IPaddr2 - Different network segment

2016-12-01 Thread Jan Pokorný
On 30/11/16 12:10 -0300, Ronny Machado C. wrote: > soon I'll have to configure an Apache web server cluster which publish a > VIP via ofc:hearbeat:IPaddr2, thing is, the two nodes live in different > sites and with a different ip segments...any advice on how to > use ocf:heartbeat:IPaddr2

Re: [ClusterLabs] Deleting a variable

2016-12-01 Thread Ken Gaillot
On 12/01/2016 01:15 AM, Ulrich Windl wrote: Ken Gaillot schrieb am 30.11.2016 um 21:39 in Nachricht > <62cb811f-4396-ff36-ec03-67000b4ed...@redhat.com>: > > [...] >> Once set, attributes are not truly deleted -- only their values are >> cleared. And --delay has no

Re: [ClusterLabs] Antw: Re: Set a node attribute for multiple nodes with one command

2016-12-01 Thread Kostiantyn Ponomarenko
OK, now I see. I still have a few questions. 1. Is there a good reason to not remove the attribute totally if it is "deleted"? 2. Does "attrd_updater" sets attributes to "status" configuration section only? 3. Do I need to modify/set "--delay" to 0 before removing or changing the