<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>Hi Felix,</div>
<div> </div>
<div>basically you have three option to provide information to the resource agent.</div>
<div>- Resource parameters</div>
<div>- Resource meta attributes</div>
<div>- Node attributes</div>
<div>
<div> </div>
<div>Let me assume some information for an example.</div>
<div>Your nodes are named nodeA and nodeB.</div>
<div>The hardware address for nodeA shall be 0x30000 and for nodeB 0x60000.</div>
<div> </div>
<div>Resource parameter should be defined in the meta information part of the resource agent. As long as you have always a defined number of nodes, this can work as follows.</div>
<div>crm configure ... param node1name=nodeA node1addr=0x30000 node2name=nodeB node2addr=0x60000</div>
<div>The resource agent can go through all nodeXname parameter and pick the number out with its own hostname and read the address with the same number.</div>
<div>Be aware, that all those parameters have to be defined in the mta-data.</div>
<div> </div>
<div>Resource meta attributes are more relaxed, as you can assign every name and every value without defining them in the meta-data.</div>
<div>crm configure ... meta node1name=nodeA node1addr=0x30000 node2name=nodeB node2addr=0x60000</div>
<div>Read the meta data with crm_resource inside the resource agent.</div>
<div> </div>
<div>Node attributes are set and read with crm_attribute and can be persistent.</div>
<div>Set the attribute with</div>
<div>crm_attribute -n hwaddr -N nodeA -l forever -v 0x30000</div>
<div>
<div>crm_attribute -n hwaddr -N nodeB -l forever -v 0x60000</div>
<div>Inside the resource agent read the value with</div>
<div>crm_attribute -n hwaddr -N $HOSTNAME -l forever -G -q</div>
<div>and you get the value for the current host.</div>
<div> </div>
<div>I had a similar approach to do and used resource meta attributes mainly for two reasons.</div>
<div>- Resource configuration is bound to the resource and does not influence anybody else.</div>
<div>- Using "crm configure show" also shows the configuration of the resource, using crm_attribute would not.</div>
<div> </div>
<div>Rainer</div>
</div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Montag, 08. April 2013 um 09:34 Uhr<br/>
<b>Von:</b> "Felix Zachlod" <fz.lists@sis-gmbh.info><br/>
<b>An:</b> Pacemaker@oss.clusterlabs.org<br/>
<b>Betreff:</b> [Pacemaker] Clone Resources Individual Configuration per Node</div>
<div name="quoted-content">Hello List,<br/>
<br/>
I am up to writing a resource agent for Pacemaker which shall be used in a<br/>
Master/Slave manner. So the cluster shall always run two instances and one<br/>
of them shall be Master. My clone instances need a different configuration<br/>
depending on the node that they are running on. I know I could accomplish<br/>
this by having some kind of configuration file on each node but I want to<br/>
manage as much as possible through the cluster manager. So what I want is a<br/>
Master / Slave (or clone) resource running with instance attributes tied to<br/>
the cluster node which they are running on.<br/>
<br/>
Let me explain what the purpose is:<br/>
<br/>
The resource is dependent on specific hardware on the cluster node, which<br/>
has different hardware addresses on each node. So resource instance A DOES<br/>
deliver the same service as resource instance B at least when being in the<br/>
master state each but anyways has to be started with a different parameter.<br/>
<br/>
I understood that I can configure a location constraint for a resource so<br/>
that it can be run only on one node Lets say my RA expects a param<br/>
hwaddr={string}. I can set up a resource for Node a with hwaddr="a" and one<br/>
for node b with hwaddr="b" but how can I tell pacemaker that these two<br/>
resources now shall be treated as a Master Slave set? Or am I thinking about<br/>
this too complicated?<br/>
<br/>
Thank you for any hint in advance,<br/>
Felix<br/>
<br/>
<br/>
_______________________________________________<br/>
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br/>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/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/doc/Cluster_from_Scratch.pdf</a><br/>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a></div>
</div>
</div>
</div></div></body></html>