On 17/04/2013, at 6:15 PM, Ivor Prebeg <[email protected]> wrote:
> Hi Andreas, thank you for your answer. > > Maybe my description was a little fuzzy, sorry for that. > > What I want is following: > > * if l3_ping fails on a particular node, all services should go to standby on > that node (which probably works fine with on-fail="standby") correct > > * if sip service (active/active) fails on particular node, only floating ip > assigned should be migrated to other node colocate ip with sip clone > > * if any of services (active/active), be it database or java container fails, > both database and java container should be stopped and floating ip migrated > to another node put all three in a group? > > * failure of sip service should not affect database or java container and > vice versa. > > Hope this makes it more clear, not sure that I understood how to achieve > dependency tree. > > Thanks, > Ivor Prebeg > > On Apr 16, 2013, at 2:50 PM, Andreas Mock <[email protected]> wrote: > >> Hi Ivor, >> >> I don't know whether I understand you completely right: >> If you want independence of resources don't put them into a group. >> >> Look at >> http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html/Pacemaker_Explained/ch10.html >> >> A group is made to tie together several resources without >> declaring all necessary colocations and orderings to get >> a desired behaviour. >> >> Otherwise. Name your resources ans how they should be spread across >> your cluster. (Show the technical dependency) >> >> Best regards >> Andreas >> >> >> Von: Ivor Prebeg [mailto:[email protected]] >> Gesendet: Dienstag, 16. April 2013 13:53 >> An: [email protected] >> Betreff: [Pacemaker] Pacemaker configuration with different dependencies >> >> Hi guys, >> >> I need some help with pacemaker configuration, it is all new to me and can't >> find solution... >> >> I have two-node HA environment with services that I want to be partially >> independent, in pacemaker/heartbeat configuration. >> >> There is active/active sip service with two floating IPs, it should all just >> migrate floating ip when one sip dies. >> >> There is also two active/active master/slave services with java container >> and rdbms with replication between them, should also fallback when one dies. >> >> What I can't figure out how to configure those two to be independent (put >> on-fail directive on group). What I want is to, e.g., in case my sip service >> fails, java container stays active on that node, but floating ip to be moved >> to other node. >> >> Another thing is, in case one of rdbms fails, I want to put whole service >> group on that node to standby, but leave sip service intact. >> >> Whole node should go to standby (all services down) only when L3_ping to >> gateway dies. >> >> All suggestions and configuration examples are welcome. >> >> Thanks in advance. >> >> >> Ivor Prebeg >> >> >> _______________________________________________ >> Pacemaker mailing list: [email protected] >> 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 > > _______________________________________________ > Pacemaker mailing list: [email protected] > 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 _______________________________________________ Pacemaker mailing list: [email protected] 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
