On 03/19/2012 08:00 PM, sathya bettadapura wrote: > Let me try rephrasing the question. > > I thought a service such as DLCK was being provided in OpenAis as it's > not part of corosync. So if someone was planning on using distributed > locking for some applications, would they have to develop it themselves > now, as corosync doesn't provide it directly ? > > Not quite sure what you mean when you say "Or you can use corosync". Do > you mean corosync already provides DLCK in some way or that it's not > needed ? Would appreciate some clarification. > > Thanks, > > Sathya > implementing distributed locking is pretty easy on top of total ordering. Another option (in linux) is the DLM packages and kernel modules. Regards -steve > ------------------------------------------------------------------------ > *From:* Steven Dake <sdake@xxxxxxxxxx> > *To:* sathya bettadapura <s_bettadapura@xxxxxxxxx> > *Cc:* "discuss@xxxxxxxxxxxx" <discuss@xxxxxxxxxxxx> > *Sent:* Wednesday, March 7, 2012 1:02 PM > *Subject:* Re: Newbie question about Corosync-1.4.2 and > Openais-1.1.4 > > On 03/07/2012 12:53 PM, sathya bettadapura wrote: >> Thanks for the info. Are there plans to move Openais services like AMF >> and DLCK to the corosync project ? >> >> Thanks, >> >> Sathya >> > > I don't have any plans to do this. If you really want SAF might take a > look at opensaf.org <http://opensaf.org>. > > nother option is to just use corosync directly since it is well tested, > has tens of thousands of deployments, and available everywhere with a > dedicated upstream. > > Regards > -steve > >> ------------------------------------------------------------------------ >> *From:* Steven Dake <sdake@xxxxxxxxxx <mailto:sdake@xxxxxxxxxx>> >> *To:* sathya bettadapura <s_bettadapura@xxxxxxxxx > <mailto:s_bettadapura@xxxxxxxxx>> >> *Cc:* "discuss@xxxxxxxxxxxx <mailto:discuss@xxxxxxxxxxxx>" > <discuss@xxxxxxxxxxxx <mailto:discuss@xxxxxxxxxxxx>> >> *Sent:* Monday, February 27, 2012 4:28 PM >> *Subject:* Re: Newbie question about Corosync-1.4.2 and >> Openais-1.1.4 >> >> On 02/27/2012 05:02 PM, sathya bettadapura wrote: >>> Hi All, >>> >>> Let me start off with an apology if this is not the right group to post >>> a newbie question, as looking at the archives it appears to be meant for >>> more serious discussion. But as I couldn't find any FAQ or a user group >>> mailing list, I am posting it here. >>> >>> For starters, I was able to build corosync-1.4.2 and install it on two >>> nodes and execute a few test programs and all that works fine. >>> >>> But I have problems running openasi. Recent version of Openais such as >>> the branch "wilson" or 1.1.4 execute the binary "corosync" with >>> COROSYNC_DEFAULT_CONFIG_FILE set to >>> "openaisserviceenableexperimental:corosync_parser". I'm trying to follow >>> the instructions in README.amf and running into basic problems in >>> starting openais services, problems which are probably related to some >>> missing configuration settings or probably misconfiguration. >>> >>> 1) Looking at the log file where corosync logs its mesages, it looks >>> like corsync is up and ready to serve, but openais didn't even open >>> "amf.conf" (I have verified that the config file does exist where it's >>> expected to and in addition also in /etc/corosync/conf, the default >>> location for amf.conf). >>> >>> 2) In the openais source tree, README.amf which describes how to test >>> basic AMF functionlaity refers to a test program called "testamf1", >>> which is missing in the Makefile under the "test" directory. If you run >>> make from the top level, it makes a bunch of other test programs but not >>> "testamf1" (I modified the Makefile to produce "testamf1" too before >>> attempting to run openais). Does anyone know if the Makefile been >>> modified deliberately to omit making "testamf1" (version 0.80.6 appears >>> to have has "testamf1") ? >>> >>> Thanks, >>> >>> Sathya >>> >> >> openais is no longer maintained. See: http://www.openais.org/doku.php >> for the rationale >>> >>> _______________________________________________ >>> discuss mailing list >>> discuss@xxxxxxxxxxxx <mailto:discuss@xxxxxxxxxxxx> > <mailto:discuss@xxxxxxxxxxxx <mailto:discuss@xxxxxxxxxxxx>> >>> http://lists.corosync.org/mailman/listinfo/discuss >> >> >> > > > _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
