On 2008-02-07T22:43:50, Thomas Glanzmann <[EMAIL PROTECTED]> wrote: > Hello again, > here comes by cib.xml for a clusterip. But the ressource stickiness is not > working for me. When I shoutdown ha-2, the two clone instances stay on ha-1. > Any ideas? Before sending this e-mail I used the following command to > set some location constraints: > > crm_resource -M -r ip0:0 -H ha-1
Uhm, what do you think should happen when you shutdown ha-2 - of course they stat on ha-1 in that case? > However it seems that location constraints or preferences are totally > fine with cloned ressources. So it doesn't seem that I do need the > ressource_stickiness. It doesn't work for me anyway. And that answers my > other question, I guess. I don't know what you're saying here ;-) > (ha-1) [~] crm_mon -1 -r > > ============ > Last updated: Thu Feb 7 22:25:12 2008 > Current DC: ha-1 (330da1b6-5f99-480a-b071-a144a98e1248) > 2 Nodes configured. > 1 Resources configured. > ============ > > Node: ha-2 (095256ab-361c-4b1e-9a8b-8bed74c4a7fb): online > Node: ha-1 (330da1b6-5f99-480a-b071-a144a98e1248): online > > Full list of resources: > > Clone Set: clusterip-clone > ip0:0 (heartbeat::ocf:IPaddr2): Started ha-1 > ip0:1 (heartbeat::ocf:IPaddr2): Started ha-1 > > <configuration> > <crm_config> > <cluster_property_set id="cib-bootstrap-options"> > <attributes> > <nvpair name="ressource_stickiness" value="0" > id="ressource-stickiness"/> > </attributes> With resource stickiness, this should be spread across two nodes? > </cluster_property_set> > </crm_config> > > <resources> > <clone id="clusterip-clone"> > <meta_attributes id="clusterip-clone-ma"> > <attributes> > <nvpair id="clusterip-clone-1" > name="globally_unique" value="false"/> This setting is wrong. globally_unique must be true for the cluster ip. Your configuration doesn't really work ;-) > <nvpair id="clusterip-clone-2" > name="clone_max" value="2"/> You can drop this line, it defaults to the number of nodes anyway - unless, of course, you want to make it larger so you can do more fine grained load control later. > <nvpair id="clusterip-clone-3" > name="clone_node_max" value="2"/> > </attributes> > </meta_attributes> > > <primitive class="ocf" provider="heartbeat" > type="IPaddr2" id="ip0"> > <instance_attributes id="ia-ip0"> > <attributes> > <nvpair id="ia-ip0-1" > name="ip" value="157.163.248.193"/> > <nvpair id="ia-ip0-2" > name="cidr_netmask" value="25"/> > <nvpair id="ia-ip0-3" > name="nic" value="eth0"/> > <nvpair id="ia-ip0-4" > name="mac" value="01:02:03:04:05:06"/> That's not a valid multicast MAC. Regards, Lars -- Teamlead Kernel, SuSE Labs, Research and Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde _______________________________________________ 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