On 07/25/2012 09:08 AM, Antonis Christofides wrote: > On 2012-07-24 21:00, Andreas Kurz wrote: >> Though better you change "ver: 0" in your Corosync configuration to >> "ver: 1" ... in the Pacemaker plugin section, and use the init script to >> start Pacemaker after Corosync. > > Thanks, I suspected that, but I can't understand what is the "pacemaker > plugin section" of the corosync configuration. I don't see it in "man > corosync.conf", and I couldn't find any example on the web. http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/index.html#s-install-enable-ais .... Example D.3 ... its called "service" in corosync. > >> You can use either the crm shell bey executing "crm" ... or give LCMC a >> try: http://lcmc.sourceforge.net/ > > So I give it some commands and it stores its configuration in some kind > of internal database, which on Debian seems to be /var/lib/heartbeat. I > wonder whether this is a good idea; some deployment systems such as > Puppet can work better with installing configuration files than by > executing commands. (Yes, I know I'm rushing too much; since I am a > beginner I need to understand the philosophy of the whole thing first, > but I couldn't hold myself :-) http://clusterlabs.org/doc/crm.8.html ... crm can ex/import a "readable" version of the XML configuration. Regards, Andreas -- Need help with Corosync? http://www.hastexo.com/now
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
