On Tue, 21 May 2013, Lars Ellenberg wrote:
> On Tue, May 21, 2013 at 02:20:46PM +0000, Tony Stocker wrote:
>> On Tue, 21 May 2013, Ulrich Windl wrote:
>>
>>>>>> Tony Stocker <tony.stoc...@nasa.gov> schrieb am 21.05.2013 um 15:21 in
>>> Nachricht
>>> <alpine.lrh.2.03.1305211310530.10...@tf6102xuryqne.ccf.rbfqvf.anfn.tbi>:
>>>> On Tue, 21 May 2013, Ulrich Windl wrote:
>>>>
>>>>> Hi!
>>>>>
>>>>> I don't know what you are trying to do, but could "node coloring" do what
>>>> you want (run resources on nodes with a specific color (red/green/yellow))?
>>>
>>> Hi!
>>>
>>> Maybe that's my fault: "system health" is the term that you should look for
>>> ("info HealthSMART", "node-health-strategy").
>>> I don't think the crm can write corresponding rules without using XML.
>>>
>>> Regards,
>>> Ulrich
>>
>>
>> Okay, let me back up a bit. Maybe you can help me answer the following
>> questions which sort of underlie what I'm trying to do:
>>
>>
>> 1. Can a location constraint apply to a resource group? Or must
>> it apply only to resource primitives?
>>
>>
>> 2. Can a location constraint rule apply to a node parameter other
>> than #uname?
>>
>>
>>
>> I've tried creating one using crmsh but it doesn't seem to be working as I
>> anticipate:
>>
>> # crm configure show
>> node gpmhac01 \
>> attributes class="A" kernel="2.6.32-358.6.2.el6.x86_64"
>> node gpmhac06 \
>> attributes class="A" kernel="2.6.32-358.6.2.el6.x86_64"
>> node gpmhac09 \
>> attributes class="B" kernel="2.6.32-358.6.2.el6.x86_64"
>> node gpmhac10 \
>> attributes class="B" kernel="2.6.32-358.6.2.el6.x86_64"
>> node gpmhac11 \
>> attributes class="B" kernel="2.6.32-358.6.2.el6.x86_64"
>> node gpmhac12 \
>> attributes class="B" kernel="2.6.32-358.6.2.el6.x86_64"
>> primitive HACMASTER-BAK-IP ocf:heartbeat:IPaddr2 \
>> params ip="192.168.1.179" \
>> op monitor interval="30s"
>> primitive HACMASTER-COMM-IP ocf:heartbeat:IPaddr2 \
>> params ip="10.8.1.1" \
>> op monitor interval="30s"
>> primitive HACMASTER-EXT-IP ocf:heartbeat:IPaddr2 \
>> params ip="186.106.183.10" \
>> op monitor interval="30s"
>> primitive HACMASTER-JAVA ocf:PPS:hacJavaLinks
>> primitive HACMASTER-JOBFILE ocf:PPS:hacJobFile \
>> params role="hac" job="hacmaster"
>> primitive HACMASTER-PWFILE ocf:PPS:hacPWFile \
>> params role="hac"
>> primitive HACMASTER-SSHKEYS ocf:PPS:hacSSHKeys
>> primitive HACMASTER-STOR-IP ocf:heartbeat:IPaddr2 \
>> params ip="10.8.3.1" \
>> op monitor interval="30s"
>> group HACMASTER HACMASTER-JOBFILE HACMASTER-PWFILE HACMASTER-JAVA
>> HACMASTER-SSHKEYS HACMASTER-EXT-IP HACMASTER-BAK-IP HACMASTER-COMM-IP
>> HACMASTER-STOR-IP \
>> meta target-role="Started"
>> location hacmaster_prefer_b HACMASTER \
>> rule $id="hacmaster_prefer_b-rule" 1000: #class eq B
>
> You use "class" above.
> So lose the hash mark:
> rule $id="hacmaster_prefer_b-rule" 1000: class eq B
>
> The "#uname" attribute is a special, implicit one...
>
>
Lars,
Thanks so much! I was using the documentation as a guide so that's why I
had the hash mark since I didn't realize that is was reserved for special
attributes. Combined with upping the scores for the constraints
for the resource group, this seems to be working at the moment.
Thanks again very much.
Tony
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
