On Wed, Jun 30, 2010 at 3:10 PM, Xeno1234 <[email protected]> wrote: > > Hi, > > I am currently trying to setup a cluster using heartbeat. Unfortunatly it > does not do what I want to do. I am using heartbeat 2.1.4-11 on a readhat > system.
You should really think about upgrading to 3.0 + Pacemaker 1.0 (that where the crm lives now). http://www.clusterlabs.org/rpm/ <--- EPEL =~ RHEL 2.1.4 is not supported. > I am using the the cib for configuration. > > What I want to do is the following: > I have two Nodes. I want to run a clone resource on both nodes. It's "named" > I want to run as a clone. This works fine. > Additionally I want to have two virtual IP adresses. One should be set on > Node 1 the other on Node 2. This works fine as well. > I want to set dependencies between the resources. And this is where I have > problems. > What I want to achive: > In case named is not able to run on a node, the vIP should switch to the > other node (which then will have both vIPs). In case both nodes are able to > run named, there should be one vIP on each node. Sounds simple, but does not > work. > Accourding to the heartbeat docu this an be achieved by using > '<rsc_colocation id=”stats-with-clone1” from=”vIP-1” to=”named-clone”/>' > '<rsc_colocation id=”stats-with-clone2” from=”vIP-2” to=”named-clone”/>' > But this does not work. It does not conform to the dtd and so is not > possible to set. Even if I set a score to make the syntax valid it does not > work as expected. > > Any ideas how to achive the result I am looking for? > > Cheers > Timo > -- > View this message in context: > http://old.nabble.com/Heartbeat-Clone-with-vIPs-constraints-tp29034376p29034376.html > Sent from the Linux-HA mailing list archive at Nabble.com. > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
