Re: [ClusterLabs] Pacemaker 1.1.16 released

[Jehan-Guillaume de Rorthais]

On Fri, 2 Dec 2016 13:44:59 -0600
Ken Gaillot  wrote:

> On 12/01/2016 11:58 AM, Jehan-Guillaume de Rorthais wrote:
> > 
> > 
> > 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 Pacemaker
>  cluster resource manager, version 1.1.15.  
> >>>
> >>> 1.1.6 I guess ;)  
> >>
> >> Whoops!
> >>
> >> Well now I don't feel so bad since the correction is wrong too ;)  
> > 
> > Argh !! :-D 
> > 
> > What about my questions bellow BTW ? :-P 
> >   
> >>> But congrats anyway !
> >>>  
>  * Previously, the OCF_RESKEY_CRM_meta_notify_active_* variables were not
>  properly passed to multistate resources with notification enabled.
>  This has been fixed. To help resource agents detect when the fix is
>  available, the CRM feature set has been incremented. (Whenever the
>  feature set changes, mixed-version clusters are supported only during
>  rolling upgrades -- nodes with an older version will not be allowed to
>  rejoin once they shut down.)  
> >>>
> >>>   * how could we get the "CRM feature set" version from the RA?  
> 
> it's passed as an environment variable
> 
> >>>   * when this "CRM feature set" has been introduced in Pacemaker?  
> 
> always, see http://wiki.clusterlabs.org/wiki/ReleaseCalendar

Thank you for the answers!

Regards,

___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Pacemaker 1.1.16 released

[Ken Gaillot]

On 12/01/2016 11:58 AM, Jehan-Guillaume de Rorthais wrote:
> 
> 
> 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 Pacemaker
 cluster resource manager, version 1.1.15.
>>>
>>> 1.1.6 I guess ;)
>>
>> Whoops!
>>
>> Well now I don't feel so bad since the correction is wrong too ;)
> 
> Argh !! :-D 
> 
> What about my questions bellow BTW ? :-P 
> 
>>> But congrats anyway !
>>>
 * Previously, the OCF_RESKEY_CRM_meta_notify_active_* variables were not
 properly passed to multistate resources with notification enabled.
 This has been fixed. To help resource agents detect when the fix is
 available, the CRM feature set has been incremented. (Whenever the
 feature set changes, mixed-version clusters are supported only during
 rolling upgrades -- nodes with an older version will not be allowed to
 rejoin once they shut down.)
>>>
>>>   * how could we get the "CRM feature set" version from the RA?

it's passed as an environment variable

>>>   * when this "CRM feature set" has been introduced in Pacemaker?

always, see http://wiki.clusterlabs.org/wiki/ReleaseCalendar


___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] hawk - pacemaker remote

[Ken Gaillot]

On 12/02/2016 07:38 AM, philipp.achmuel...@arz.at wrote:
> Hi,
> 
> pacemaker remote nodes do not show up in hawk gui.
> regarding documentation, this should work - any hints to activate this?
> 
> thank you!
> 
> env: (SLES12.2)
> pacemaker-1.1.15-19.15.x86_64
> hawk2-2.0.0+git.1468428505.0135e38-24.32.x86_64

I'm not familiar with hawk but based on earlier conversations with
someone who uses it, it may only see nodes in the  CIB section,
so try setting any permanent node attribute on the remote nodes to make
them show up

___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] clone resource - pacemaker remote

[Ken Gaillot]

On 12/02/2016 07:08 AM, philipp.achmuel...@arz.at wrote:
> hi,
> 
> what is best way to prevent clone resource trying to run on remote/guest
> nodes?

location constraints with a negative score:

http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#_deciding_which_nodes_a_resource_can_run_on


you can even use a single constraint with a rule based on #kind ne
cluster, so you don't need a separate constraint for each node:

http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#_node_attribute_expressions


alternatively, you can set symmetric-cluster=false and use positive
constraints for cluster nodes only

> 
> ...
> node 167873318: lnx0223a \
> attributes maintenance=off
> node 167873319: lnx0223b \
> attributes maintenance=off
> ...
> /primitive vm-lnx0107a VirtualDomain \/
> /params hypervisor="qemu:///system"
> config="/etc/kvm/lnx0107a.xml" \/
> /meta remote-node=lnx0107a238 \/
> /utilization cpu=1 hv_memory=4096/
> /primitive remote-lnx0106a ocf:pacemaker:remote \/
> /params server=xx.xx.xx.xx \/
> /meta target-role=Started/
> /group base-group dlm clvm vg1/
> /clone base-clone base-group \/
> /meta interleave=true target-role=Started/
> /.../
> 
> /Dec  1 14:32:57 lnx0223a crmd[9826]:   notice: Initiating start
> operation dlm_start_0 on lnx0107a238/
> /Dec  1 14:32:58 lnx0107a pacemaker_remoted[1492]:   notice: executing -
> rsc:dlm action:start call_id:7/
> /Dec  1 14:32:58 lnx0107a pacemaker_remoted[1492]:   notice: finished -
> rsc:dlm action:start call_id:7  exit-code:5 exec-time:16ms queue-time:0ms/
> /Dec  1 14:32:58 lnx0223b crmd[9328]:error: Result of start
> operation for dlm on lnx0107a238: Not installed/
> /Dec  1 14:32:58 lnx0223a crmd[9826]:  warning: Action 31 (dlm_start_0)
> on lnx0107a238 failed (target: 0 vs. rc: 5): Error/
> /Dec  1 14:32:58 lnx0223a crmd[9826]:  warning: Action 31 (dlm_start_0)
> on lnx0107a238 failed (target: 0 vs. rc: 5): Error/
> /Dec  1 14:34:07 lnx0223a pengine[9824]:  warning: Processing failed op
> start for dlm:2 on lnx0107a238: not installed (5)/
> /Dec  1 14:34:07 lnx0223a pengine[9824]:  warning: Processing failed op
> start for dlm:2 on lnx0107a238: not installed (5)/
> /.../
> /Dec  1 14:32:49 lnx0223a pengine[9824]:   notice: Start  
> dlm:3#011(remote-lnx0106a)/
> /Dec  1 14:32:49 lnx0223a crmd[9826]:   notice: Initiating monitor
> operation dlm_monitor_0 locally on remote-lnx0106a/
> /Dec  1 14:32:50 lnx0223a crmd[9826]:error: Result of probe
> operation for dlm on remote-lnx0106a: Not installed/
> /Dec  1 14:32:50 lnx0223a crmd[9826]:  warning: Action 5 (dlm_monitor_0)
> on remote-lnx0106a failed (target: 7 vs. rc: 5): Error/
> /Dec  1 14:32:50 lnx0223a crmd[9826]:  warning: Action 5 (dlm_monitor_0)
> on remote-lnx0106a failed (target: 7 vs. rc: 5): Error/
> /.../
> 
> ---
> env: pacemaker-1.1.15-19.15.x86_64
> 
> thank you!

___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] hawk - pacemaker remote

[philipp . achmueller]

Hi,

pacemaker remote nodes do not show up in hawk gui.
regarding documentation, this should work - any hints to activate this? 

thank you!

env: (SLES12.2)
pacemaker-1.1.15-19.15.x86_64
hawk2-2.0.0+git.1468428505.0135e38-24.32.x86_64
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] clone resource - pacemaker remote

[philipp . achmueller]

hi,

what is best way to prevent clone resource trying to run on remote/guest 
nodes?

...
node 167873318: lnx0223a \
attributes maintenance=off
node 167873319: lnx0223b \
attributes maintenance=off
...
primitive vm-lnx0107a VirtualDomain \
params hypervisor="qemu:///system" config="/etc/kvm/lnx0107a.xml" 
\
meta remote-node=lnx0107a238 \
utilization cpu=1 hv_memory=4096
primitive remote-lnx0106a ocf:pacemaker:remote \
params server=xx.xx.xx.xx \
meta target-role=Started
group base-group dlm clvm vg1
clone base-clone base-group \
meta interleave=true target-role=Started
...

Dec  1 14:32:57 lnx0223a crmd[9826]:   notice: Initiating start operation 
dlm_start_0 on lnx0107a238
Dec  1 14:32:58 lnx0107a pacemaker_remoted[1492]:   notice: executing - 
rsc:dlm action:start call_id:7
Dec  1 14:32:58 lnx0107a pacemaker_remoted[1492]:   notice: finished - 
rsc:dlm action:start call_id:7  exit-code:5 exec-time:16ms queue-time:0ms
Dec  1 14:32:58 lnx0223b crmd[9328]:error: Result of start operation 
for dlm on lnx0107a238: Not installed
Dec  1 14:32:58 lnx0223a crmd[9826]:  warning: Action 31 (dlm_start_0) on 
lnx0107a238 failed (target: 0 vs. rc: 5): Error
Dec  1 14:32:58 lnx0223a crmd[9826]:  warning: Action 31 (dlm_start_0) on 
lnx0107a238 failed (target: 0 vs. rc: 5): Error
Dec  1 14:34:07 lnx0223a pengine[9824]:  warning: Processing failed op 
start for dlm:2 on lnx0107a238: not installed (5)
Dec  1 14:34:07 lnx0223a pengine[9824]:  warning: Processing failed op 
start for dlm:2 on lnx0107a238: not installed (5)
...
Dec  1 14:32:49 lnx0223a pengine[9824]:   notice: Start 
dlm:3#011(remote-lnx0106a)
Dec  1 14:32:49 lnx0223a crmd[9826]:   notice: Initiating monitor 
operation dlm_monitor_0 locally on remote-lnx0106a
Dec  1 14:32:50 lnx0223a crmd[9826]:error: Result of probe operation 
for dlm on remote-lnx0106a: Not installed
Dec  1 14:32:50 lnx0223a crmd[9826]:  warning: Action 5 (dlm_monitor_0) on 
remote-lnx0106a failed (target: 7 vs. rc: 5): Error
Dec  1 14:32:50 lnx0223a crmd[9826]:  warning: Action 5 (dlm_monitor_0) on 
remote-lnx0106a failed (target: 7 vs. rc: 5): Error
...

---
env: pacemaker-1.1.15-19.15.x86_64

thank you!
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org