[Pacemaker] Clone Resources Individual Configuration per Node

[Andrew Beekhof]

All the other replies will work, however the original intention was that people would use

   http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/_using_rules_to_control_resource_options.html

In practice it may be more or less usable than the alternatives. 

On 08/04/2013, at 5:34 PM, Felix Zachlod <fz.lists at sis-gmbh.info> wrote:

> Hello List,
> 
> I am up to writing a resource agent for Pacemaker which shall be used in a
> Master/Slave manner. So the cluster shall always run two instances and one
> of them shall be Master. My clone instances need a different configuration
> depending on the node that they are running on. I know I could accomplish
> this by having some kind of configuration file on each node but I want to
> manage as much as possible through the cluster manager. So what I want is a
> Master / Slave (or clone) resource running with instance attributes tied to
> the cluster node which they are running on.
> 
> Let me explain what the purpose is:
> 
> The resource is dependent on specific hardware on the cluster node, which
> has different hardware addresses on each node. So resource instance A DOES
> deliver the same service as resource instance B at least when being in the
> master state each but anyways has to be started with a different parameter.
> 
> I understood that I can configure a location constraint for a resource so
> that it can be run only on one node Lets say my RA expects a param
> hwaddr={string}. I can set up a resource for Node a with hwaddr="a" and one
> for node b with hwaddr="b" but how can I tell pacemaker that these two
> resources now shall be treated as a Master Slave set? Or am I thinking about
> this too complicated?
> 
> Thank you for any hint in advance,
> Felix
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org