[Pacemaker] RHEL6 - clam + pacemaker + clvmd

Nikola Ciprich nikola.ciprich at linuxbox.cz
Mon Jul 1 12:46:18 UTC 2013


Hello again,

and thanks for your reply again.
> Sorry, no. That's up to you to decide. I go with corosync2 only because
> I'm pretty sure I can put that all into "Works for me" state now and in
> a future.
OK, I understand..

> 
> > slides, to me safe choice seems to be cman + pacemaker + (patched) clvmd,
> > better for futer could be corosync + pacemaker + clvmd (+ future patch).
> 
> Not exactly.
> now - cman + pacemaker + future patch for clvmd,
> future - corosync2 + pacemaker + dlm4 + clvmd with existing patch.
> 
> If you go with corosync2 you should realize that there are big issues
> running clustered filesystems with new corosync and old kernel.

well, this shouldn't be problem for me, I don't use any clustered filesystems
at all, I'm only interested in clustered LVM...

> 
> Actually, in future RHEL (and in fedora 17+) gfs and dlm communicate in
> kernel space rather than in userspace fro EL6. That's why gfs_controld
> (which is not needed in future releases) and ocfs_controld need to be
> ported to corosync2 for EL6. I did port former (thanks to David for not
> removing fs_control functionality from dlm), but I won't support that
> port except for myself. OCFS part is completely unclear for me.

that's what I forgot to mention, I'm not using distro kernel, but 3.x based
one.

I guess I'll just create a bunch of testing clusters with various combinations
and see which works best for me...

thanks a lot for Your valuable guidance, I appreciate it a lot!

have a nice day

with best regards

nik

> 
> 
> > 
> > While I'm not a cluster guru at all, I've got some experience with pacemaker
> > and don't have problem building and maintaining my own packages as well as
> > patching stuff...
> 
> You may try.
> I would say that it is possible to make everything work.
> 
> > 
> > thanks a lot in advance for this last advice :)
> > 
> > BR
> > 
> > nik
> > 
> > 
> > 
> > 
> > 
> >>
> >>
> >> _______________________________________________
> >> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> >> 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: Pacemaker at oss.clusterlabs.org
> > 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: Pacemaker at oss.clusterlabs.org
> 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
> 

-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28.rijna 168, 709 00 Ostrava

tel.:   +420 591 166 214
fax:    +420 596 621 273
mobil:  +420 777 093 799
www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis at linuxbox.cz
-------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130701/7fc4b257/attachment-0004.sig>


More information about the Pacemaker mailing list