I will stick with the stable version. Upgrading corosync to 1.4.2, and see if that helps my error. Just a note, on the cluster site it say "requires corosync 1.4.1 (or higher) and openais 1.1.4 (or higher) "
Cheers, Nick. On Wed, Oct 26, 2011 at 2:36 PM, Fabio M. Di Nitto <fdini...@redhat.com> wrote: > On 10/26/2011 8:34 PM, Nick Khamis wrote: >> The question is, does the unstable standalone of dlm require cman? > > No it doesn´t, but as I wrote in the other email, it´s too "unstable". > It´s under heavy development and has received little to none testing. > >> There use to be >> a LibLogThread depedency. > > That´s probably a leftover in the Makefiles because as far as I remember > the new dlm doesn´t use liblogthread. If it does, you can just grab it > from cluster.git STABLE31 branch. > > Fabio > > >> >> Thanks in Advace, >> >> Nick. >> >> On Wed, Oct 26, 2011 at 2:29 PM, Nick Khamis <sym...@gmail.com> wrote: >>> Hello Fabio, >>> >>> Thank's again for your response. >>> >>>>> It means that pacemaker can use cman to obtain cluster view and quorum >>>>> info. So you basically configure cman and then run pacemaker instead of >>>>> rgmanage >>> >>> Sounds like something that we can use when the cluster is up and >>> running. As for dlm, >>> I checked out the latest version from >>> git://git.fedorahosted.org/dlm.git. Is it sufficient >>> just to run make && make install? Did not see and configure script. >>> >>> Thanks Again, >>> >>> Nick. >>> >>> >>> On Wed, Oct 26, 2011 at 2:19 PM, Fabio M. Di Nitto <fdini...@redhat.com> >>> wrote: >>>> On 10/26/2011 8:17 PM, Nick Khamis wrote: >>>>> I forgot to ask: >>>>> >>>>>>> Yes that is correct. dlm_controld.pcmk has been obsoleted in favour of >>>>>>> cman support for pacemaker. >>>>> >>>>> Does that mean that dlm + fence is provided by cman directly, and thus >>>>> deprecating libdlm? >>>> >>>> no. libdlm is still required. >>>> >>>>> >>>>> I just want to make sure I am on the right page. I would like to >>>>> provide dlm and fence >>>>> capabilities for our pcmk cluster. >>>>> >>>> >>>> It means that pacemaker can use cman to obtain cluster view and quorum >>>> info. So you basically configure cman and then run pacemaker instead of >>>> rgmanager. >>>> >>>>> Thanks Again, >>>>> >>>>> Nick >>>>> >>>>> On Wed, Oct 26, 2011 at 2:12 PM, Nick Khamis <sym...@gmail.com> wrote: >>>>>> Fabio, >>>>>> >>>>>> I appologize for that. It was unintentional. If you notice, I said >>>>>> "Hello Gents". I will upgrade to 1.4.2, and >>>>>> keep everyone posted. >>>>>> >>>>>> Thanks Again, >>>>>> >>>>>> Nick. >>>>>> >>>>>> On Wed, Oct 26, 2011 at 2:09 PM, Fabio M. Di Nitto <fdini...@redhat.com> >>>>>> wrote: >>>>>>> (please keep cluster-devel in the CC list, it might be helpful for other >>>>>>> people too) >>>>>>> >>>>>>> On 10/26/2011 3:00 PM, Nick Khamis wrote: >>>>>>>> Hello Gents, >>>>>>>> >>>>>>>> Thank you so much for your responses! There use to be >>>>>>>> "--enable-pacemaker" "--disable-cman" >>>>>>>> flags. These have since been dropped. So just build everything in >>>>>>>> Cluster 3 even for the pcmk stack? >>>>>>> >>>>>>> Yes that is correct. dlm_controld.pcmk has been obsoleted in favour of >>>>>>> cman support for pacemaker. >>>>>>> >>>>>>>> >>>>>>>> Any idea on the following fence error: >>>>>>>> >>>>>>>> /src/cluster-3.1.7/fence/fenced/config.c >>>>>>>> In file included from >>>>>>>> /usr/local/src/cluster-3.1.7/fence/fenced/config.c:1: >>>>>>>> /usr/local/src/cluster-3.1.7/fence/fenced/fd.h:182: error: field >>>>>>>> cpg_ringid has incomplete type >>>>>>>> make[2]: *** [config.o] Error 1 >>>>>>>> make[2]: Leaving directory `/usr/local/src/cluster-3.1.7/fence/fenced' >>>>>>>> make[1]: *** [all] Error 2 >>>>>>>> make[1]: Leaving directory `/usr/local/src/cluster-3.1.7/fence' >>>>>>>> make: *** [fence] Error 2 >>>>>>>> >>>>>>>> I am prototyping on a debian VM, and will be using fence_virt. For >>>>>>>> production, we will move to >>>>>>>> RH and obviously a STONITH device. >>>>>>>> >>>>>>>> Thanks in Advance, >>>>>>>> >>>>>>>> Nick from Toronto. >>>>>>> >>>>>>> You need a newer version of corosync. I don´t recall exactly what >>>>>>> version introduces the cpg_ringid, but you are better off taking 1.4.2. >>>>>>> >>>>>>> Fabio >>>>>>> >>>>>> >>>> >>>> >>> > >
