> iirc == if i recall correctly :-) sorry but I'm french, so ... I did not understand such achronymous ... but now I'll know ;-)
> 'rpm -ql pacemaker' will give you the file list. look for something > in the corosync directories. yes I know all those linux commands, but even on the Pacemaker release I currently use and which works with the corosync.conf , so with the plugin v1, I can't find anything related to corosync in pacemaker rpm : rpm -ql pacemaker | grep -i coro returns nothing at all > fyi though, even if it is present now, we're planning to remove it in > the next point release or so. > the policy is to not ship things we're not supporting. Yes I know, but if it is always delivered on 6.3, that will be sufficient for me until I switch from stack option 2 to stack option 4 Alain De : Andrew Beekhof <[email protected]> A : General Linux-HA mailing list <[email protected]> Date : 19/06/2012 11:34 Objet : Re: [Linux-HA] Pacemaker/corosync ==> Pacemaker/cman (on RH 6.2) Envoyé par : [email protected] > If so, how can I check for sure that the plugin is or is not in the > pacemaker package ? > (it is to check the pacemaker package delivered with the new RH 6.3) 'rpm -ql pacemaker' will give you the file list. look for something in the corosync directories. fyi though, even if it is present now, we're planning to remove it in the next point release or so. the policy is to not ship things we're not supporting. > > Thanks > Alain > > > > De : Andrew Beekhof <[email protected]> > A : General Linux-HA mailing list <[email protected]> > Date : 18/06/2012 23:38 > Objet : Re: [Linux-HA] Pacemaker/corosync ==> Pacemaker/cman (on RH 6.2) > Envoyé par : [email protected] > > > > On Mon, Jun 18, 2012 at 11:04 PM, <[email protected]> wrote: >> Hi again, >> >> could you tell me the package which install the "pacemaker plugin v1" > and >> which >> is the name of the binary or binaries or src ? > > its the pacemaker source rpm. it doesn't ship by default iirc > >> >> Thanks a lot >> Alain >> >> >> >> De : Andrew Beekhof <[email protected]> >> A : General Linux-HA mailing list <[email protected]> >> Date : 16/06/2012 12:25 >> Objet : Re: [Linux-HA] Pacemaker/corosync ==> Pacemaker/cman (on RH 6.2) >> Envoyé par : [email protected] >> >> >> >> On Fri, Jun 15, 2012 at 10:06 PM, <[email protected]> wrote: >>> 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 . >> >> cman is just a corosync plugin. think of "cman" being an alias for >> "corosync + cman plugin" >> >>> >>> 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 ? >> >> yes >> >>> as same as with option 2 and no more cluster.conf ? >> >> right >> >>> 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). >> >> I'm pretty sure you can have redundant rings with cluster.conf, I just >> don't know the details. >> >>> 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 ? >> >> No. Just corosync.conf >> You can get a preview of how option 4 works here: >> >> > https://www.dropbox.com/s/zd1mi6u1m7ac5t9/Pacemaker-1.1-Clusters_from_Scratch-en-US.pdf > >> >> >> I need to finish it off and push to clusterlabs... >> >>> >>> 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 >> _______________________________________________ >> 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 > _______________________________________________ > 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 _______________________________________________ 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
