<div dir="ltr">Chris,<div><br><div>Here is the required information</div><div><br></div><div><div><div>[root@vsanqa11 ~]# rpm -qa | grep pcs ; rpm -qa | grep pacemaker ; uname -a ; cat /etc/redhat-release</div><div>pcs-0.9.90-2.el6.centos.2.noarch</div>
<div>pacemaker-cli-1.1.10-14.el6_5.3.x86_64</div><div>pacemaker-libs-1.1.10-14.el6_5.3.x86_64</div><div>pacemaker-1.1.10-14.el6_5.3.x86_64</div><div>pacemaker-cluster-libs-1.1.10-14.el6_5.3.x86_64</div><div>Linux vsanqa11 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux</div>
<div>CentOS release 6.3 (Final)</div></div></div><div><br></div><div><br></div><div>Regards,</div><div> Kiran</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 28, 2014 at 2:47 AM, Chris Feist <span dir="ltr"><<a href="mailto:cfeist@redhat.com" target="_blank">cfeist@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 05/27/14 05:38, K Mehta wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
One more question.<br>
With crmsh, it was easy to add constraint to avoid a resource from running only<br>
a subset(say vsanqa11 and vsanqa12) of nodes using the following command<br>
<br>
crm configure location ms-${uuid}-nodes ms-$uuid rule -inf: \#uname ne vsanqa11<br>
and \#uname ne vsanqa12<br>
[root@vsanqa11 ~]# pcs constraint show --full<br>
Location Constraints:<br>
Resource: ms-c6933988-9e5c-419e-8fdf-<u></u>744100d76ad6<br>
Constraint: ms-c6933988-9e5c-419e-8fdf-<u></u>744100d76ad6-nodes<br>
Rule: score=-INFINITY<br>
(id:ms-c6933988-9e5c-419e-<u></u>8fdf-744100d76ad6-nodes-rule)<br>
Expression: #uname ne vsanqa11<br>
(id:ms-c6933988-9e5c-419e-<u></u>8fdf-744100d76ad6-nodes-<u></u>expression)<br>
Expression: #uname ne vsanqa12<br>
(id:ms-c6933988-9e5c-419e-<u></u>8fdf-744100d76ad6-nodes-<u></u>expression-0)<br>
Ordering Constraints:<br>
Colocation Constraints:<br>
<br>
So, both expression are part of the same rule as expected.<br>
<br>
<br>
<br>
With pcs, I am not sure how to use avoid constraints if I need a resource to run<br>
on vsanqa11 and vsanqa12 and not on any other node.<br>
So I tried adding location constraint as follows:<br>
pcs -f $CLUSTER_CREATE_LOG constraint location vha-$uuid rule score=-INFINITY<br>
\#uname ne vsanqa11 and \#uname ne vsanqa12<br>
Even though no error is thrown, the condition after "and" is silently dropped as<br>
shown below<br>
<br>
[root@vsanqa11 ~]# pcs constraint show --full<br>
Location Constraints:<br>
Resource: ms-c6933988-9e5c-419e-8fdf-<u></u>744100d76ad6<br>
Constraint: location-vha-c6933988-9e5c-<u></u>419e-8fdf-744100d76ad6<br>
Rule: score=-INFINITY<br>
(id:location-vha-c6933988-<u></u>9e5c-419e-8fdf-744100d76ad6-<u></u>rule)<br>
Expression: #uname ne vsanqa11<br>
(id:location-vha-c6933988-<u></u>9e5c-419e-8fdf-744100d76ad6-<u></u>rule-expr)<br>
Ordering Constraints:<br>
Colocation Constraints:<br>
<br>
<br>
Then I tried the following<br>
pcs -f $CLUSTER_CREATE_LOG constraint location vha-$uuid rule score=-INFINITY<br>
\#uname ne vsanqa11<br>
pcs -f $CLUSTER_CREATE_LOG constraint location vha-$uuid rule score=-INFINITY<br>
\#uname ne vsanqa12<br>
<br>
but running these two commands did not help either. Expressions were added to<br>
separate rules.<br>
<br>
[root@vsanqa11 ~]# pcs constraint show --full<br>
Location Constraints:<br>
Resource: ms-c6933988-9e5c-419e-8fdf-<u></u>744100d76ad6<br>
Constraint: location-vha-c6933988-9e5c-<u></u>419e-8fdf-744100d76ad6-1<br>
Rule: score=-INFINITY<br>
(id:location-vha-c6933988-<u></u>9e5c-419e-8fdf-744100d76ad6-1-<u></u>rule)<br>
Expression: #uname ne vsanqa12<br>
(id:location-vha-c6933988-<u></u>9e5c-419e-8fdf-744100d76ad6-1-<u></u>rule-expr)<br>
Constraint: location-vha-c6933988-9e5c-<u></u>419e-8fdf-744100d76ad6<br>
Rule: score=-INFINITY<br>
(id:location-vha-c6933988-<u></u>9e5c-419e-8fdf-744100d76ad6-<u></u>rule)<br>
Expression: #uname ne vsanqa11<br>
(id:location-vha-c6933988-<u></u>9e5c-419e-8fdf-744100d76ad6-<u></u>rule-expr)<br>
Ordering Constraints:<br>
Colocation Constraints:<br>
<br>
<br>
Also, tried using multistate resource name<br>
[root@vsanqa11 ~]# pcs constraint location<br>
ms-c6933988-9e5c-419e-8fdf-<u></u>744100d76ad6 rule score=-INFINITY \#uname ne vsanqa11<br>
Error: 'ms-c6933988-9e5c-419e-8fdf-<u></u>744100d76ad6' is not a resource<br>
<br>
<br>
Can anyone let me correct command for this ?<br>
</blockquote>
<br></div></div>
Which version of pcs are you using (and what distribution)? This has been fixed upstream. (Below is a test from my system using the upstream pcs).<br>
<br>
[root@rh7-1 pcs]# pcs constraint location D1 rule score=-INFINITY \#uname ne vsanqa11 and \#uname ne vsanqa12<br>
[root@rh7-1 pcs]# pcs constraint<br>
Location Constraints:<br>
Resource: D1<br>
Constraint: location-D1<br>
Rule: score=-INFINITY boolean-op=and<br>
Expression: #uname ne vsanqa11<br>
Expression: #uname ne vsanqa12<br>
<br>
Thanks,<br>
Chris<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
<br>
<br>
<br>
<br>
On Tue, May 27, 2014 at 11:01 AM, Andrew Beekhof <<a href="mailto:andrew@beekhof.net" target="_blank">andrew@beekhof.net</a><br></div><div class="">
<mailto:<a href="mailto:andrew@beekhof.net" target="_blank">andrew@beekhof.net</a>>> wrote:<br>
<br>
<br>
On 27 May 2014, at 2:37 pm, K Mehta <<a href="mailto:kiranmehta1981@gmail.com" target="_blank">kiranmehta1981@gmail.com</a><br></div><div class="">
<mailto:<a href="mailto:kiranmehta1981@gmail.com" target="_blank">kiranmehta1981@gmail.<u></u>com</a>>> wrote:<br>
<br>
> So is globally-unique=false correct in my case ?<br>
<br>
yes<br>
<br>
><br>
><br>
> On Tue, May 27, 2014 at 5:30 AM, Andrew Beekhof <<a href="mailto:andrew@beekhof.net" target="_blank">andrew@beekhof.net</a><br></div><div class="">
<mailto:<a href="mailto:andrew@beekhof.net" target="_blank">andrew@beekhof.net</a>>> wrote:<br>
><br>
> On 26 May 2014, at 9:56 pm, K Mehta <<a href="mailto:kiranmehta1981@gmail.com" target="_blank">kiranmehta1981@gmail.com</a><br></div><div><div class="h5">
<mailto:<a href="mailto:kiranmehta1981@gmail.com" target="_blank">kiranmehta1981@gmail.<u></u>com</a>>> wrote:<br>
><br>
> > What I understand from "globally-unique=false" is as follows<br>
> > Agent handling the resource does exactly same processing on all nodes.<br>
For processing this resource, agent on all nodes will use exactly same<br>
resources (files, processes, same parameters to agent entry points, etc).<br>
> ><br>
> > In case of my resource, agent on all nodes execute same "command" to<br>
find score.<br>
> > Driver present on all nodes will make sure that the node that is to be<br>
promoted is the one that reports highest score as output of the "command".<br>
Score is reported to CM using ( /usr/sbin/crm_master -Q -l reboot -v $score)<br>
in monitor entry point. Until this score<br>
> > is reported, agent on other node will just delete the score using<br>
/usr/sbin/crm_master -Q -l reboot -D in monitor entry point<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > I want to make sure that the resource does not run on nodes other than<br>
$node1 and $node2. To achieve this i use the following commands.<br>
> ><br>
> > pcs -f $CLUSTER_CREATE_LOG constraint location vha-${uuid}<br>
prefers $node1<br>
> > pcs -f $CLUSTER_CREATE_LOG constraint location vha-${uuid}<br>
prefers $node2<br>
> > pcs -f $CLUSTER_CREATE_LOG constraint location ms-${uuid}<br>
prefers $node1<br>
> > pcs -f $CLUSTER_CREATE_LOG constraint location ms-${uuid}<br>
prefers $node2<br>
> ><br>
> > Any issue here ?<br>
><br>
> Perhaps this is not intuitive but you'd need to specify 'avoids'<br>
constraints for the nodes it must not run on.<br>
> 'prefers' only says that of all the available nodes, this one is the best.<br>
><br>
> ><br>
> > Regards,<br>
> > Kiran<br>
> ><br>
> ><br>
> ><br>
> > On Mon, May 26, 2014 at 8:54 AM, Andrew Beekhof <<a href="mailto:andrew@beekhof.net" target="_blank">andrew@beekhof.net</a><br></div></div><div class="">
<mailto:<a href="mailto:andrew@beekhof.net" target="_blank">andrew@beekhof.net</a>>> wrote:<br>
> ><br>
> > On 22 May 2014, at 11:20 pm, K Mehta <<a href="mailto:kiranmehta1981@gmail.com" target="_blank">kiranmehta1981@gmail.com</a><br></div><div class="">
<mailto:<a href="mailto:kiranmehta1981@gmail.com" target="_blank">kiranmehta1981@gmail.<u></u>com</a>>> wrote:<br>
> ><br>
> > > > May 13 01:38:36 vsanqa28 pengine[4310]: notice: LogActions:<br>
Promote vha-924bf029-93a2-41a0-adcf-<u></u>f1c1a42956e5:0#011(Slave -> Master vsanqa28)<br>
> > > > May 13 01:38:36 vsanqa28 pengine[4310]: notice: LogActions:<br>
Demote vha-924bf029-93a2-41a0-adcf-<u></u>f1c1a42956e5:1#011(Master -> Slave<br>
vsanqa27) <<<<< Why did this happen ?<br>
> > ><br>
> > > attach the file mentioned on the next line and we might be able to<br>
find out<br>
> > ><br>
> ><br>
> > Quick question, do you understand what globally-unique=false means and<br>
are you sure you want it?<br>
> > If the answer is 'yes and yes', are you sure that your agent is using<br>
crm_master correctly?<br>
> ><br>
> > If I run, 'tools/crm_simulate -Sx ~/Downloads/pe-input-818.bz2 -s |<br>
grep vha-924bf029-93a2-41a0-adcf-<u></u>f1c1a42956e5', I see:<br>
> ><br>
> > vha-924bf029-93a2-41a0-adcf-<u></u>f1c1a42956e5:0 promotion score on vsanqa28:<br>
INFINITY<br>
> > vha-924bf029-93a2-41a0-adcf-<u></u>f1c1a42956e5:1 promotion score on vsanqa27: 2<br>
> ><br>
> ><br>
> > Although much of the 'INFINITY' is probably from:<br>
> ><br>
> > <rsc_location<br>
id="location-ms-924bf029-93a2-<u></u>41a0-adcf-f1c1a42956e5-<u></u>vsanqa28-INFINITY"<br>
node="vsanqa28" rsc="ms-924bf029-93a2-41a0-<u></u>adcf-f1c1a42956e5" score="INFINITY"/><br>
> ><br>
> > This is somewhat odd to include for a clone/master resource.<br>
> ><br>
> > ______________________________<u></u>_________________<br>
> > Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br></div>
<mailto:<a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.<u></u>clusterlabs.org</a>><div class=""><br>
> > <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/<u></u>mailman/listinfo/pacemaker</a><br>
> ><br>
> > Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> > Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/<u></u>doc/Cluster_from_Scratch.pdf</a><br>
> > Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
> ><br>
> ><br>
> > ______________________________<u></u>_________________<br>
> > Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br></div>
<mailto:<a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.<u></u>clusterlabs.org</a>><div class=""><br>
> > <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/<u></u>mailman/listinfo/pacemaker</a><br>
> ><br>
> > Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> > Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/<u></u>doc/Cluster_from_Scratch.pdf</a><br>
> > Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
><br>
><br>
> ______________________________<u></u>_________________<br>
> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br></div>
<mailto:<a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.<u></u>clusterlabs.org</a>><div class=""><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/<u></u>mailman/listinfo/pacemaker</a><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/<u></u>doc/Cluster_from_Scratch.pdf</a><br>
> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
><br>
><br>
> ______________________________<u></u>_________________<br>
> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br></div>
<mailto:<a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.<u></u>clusterlabs.org</a>><div class=""><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/<u></u>mailman/listinfo/pacemaker</a><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/<u></u>doc/Cluster_from_Scratch.pdf</a><br>
> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
<br>
______________________________<u></u>_________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br></div>
<mailto:<a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.<u></u>clusterlabs.org</a>><div class=""><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/<u></u>mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/<u></u>doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/<u></u>mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/<u></u>doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
______________________________<u></u>_________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/<u></u>mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/<u></u>doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
</div></div></blockquote></div><br></div>