[ClusterLabs] Deleting a variable

2016-11-30 Thread Ulrich Windl
>>> 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 effect with --update if the attribute > already

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

2016-11-30 Thread Ken Gaillot
On 11/30/2016 11:31 AM, Kostiantyn Ponomarenko wrote: > Hi Ken, > > I didn't look into the logs, but I experimented with it for a while. > Here is what I found. > > It worked for you because this attribute - "my-attr" - has not ever been > set before in that cluster. > > So if you set an

[ClusterLabs] Pacemaker 1.1.16 released

2016-11-30 Thread Ken Gaillot
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 The most significant enhancements in this release are: * rsc-pattern may now be

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

2016-11-30 Thread Dimitri Maziuk
PS you could probably use iptables to block/log outgoing traffic from the wrong ip (different on each node) to be really really sure. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature

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

2016-11-30 Thread Dimitri Maziuk
On 11/30/2016 09:10 AM, Ronny Machado C. wrote: ...any advice on how to > use ocf:heartbeat:IPaddr2 ip=x.x.x.x but in different segments, maybe is > super easy, but right now I can't find out how. ICBW but if you bring up an ip in the wrong segment, it'll just be unroutable/unreachable. As long

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

2016-11-30 Thread Kostiantyn Ponomarenko
>> Moreover, when you delete this attribute the actual remove will be delayed by that "--delay" which was used when the attribute was set. I wasn't clear here. The behavior described in this line happens only when "dampening" has worked out during the attribute set-up. Thank you, Kostia On Wed,

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

2016-11-30 Thread Kostiantyn Ponomarenko
Hi Ken, I didn't look into the logs, but I experimented with it for a while. Here is what I found. It worked for you because this attribute - "my-attr" - has not ever been set before in that cluster. So if you set an attribute, then remove it, and then set it with "--delay", like: #

Re: [ClusterLabs] Get rid of reload altogether

2016-11-30 Thread Jan Pokorný
On 28/11/16 09:44 +0530, Nikhil Utane wrote: > I understand the whole concept of reload and how to define parameters with > unique=0 so that pacemaker can call the reload operation of the OCF script > instead of stopping and starting the resource. > Now my problem is that I have 100s of parameters

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

2016-11-30 Thread Ronny Machado C.
Hi gurus, 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 ip=x.x.x.x but in different segments, maybe is super