Hi Andrew you recall me in an old thread here that effectively cman was not involved
in option 4 : corosync + cpg + quorumd + mcp whereas it is involved in option 3 : corosync + cpg + cman + mcp but is seems that corosync is also used in both options . I tried to configure option 3 as you've seen in my other email two days ago, and we only have a mini cluster.conf file , and no more corosync.conf (and it works once I start Pacemaker after cman ;-) ) My question is now : when the option 4 will be available, we will come back to the corosync.conf file ? as same as with option 2 and no more cluster.conf ? And to be completely clear on why my question : the temporary option 3 forces us to use a mini cluster.conf, and therefore only one heartbeat network (or two but with bonding). But if in the future we configure option 4, and come back to corosync.conf, we will be able to have again two networks rings in the corosync.conf, and so ... that sounds be much better for me. Excpet if quorumd is working with a mini cluster.conf like cman ? Thanks for these precisions. Regards Alain _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
