On 06/27/2011 08:12 AM, Whit Blauvelt wrote: > Hi, > > While the corosync.org site is sparse, some of the presentation slides > linked from there there promise that Corosync is designed to approach an > ideal of simplicity and clarity, to allow a variety of HA projects to be > developed against it. Since the Corosync site is sparse, is there anywhere > to find documentation on setting up Corosync as part of a project which is > not using Pacemaker, let alone one of the whole, pre-packaged cluster > stacks? Pacemaker and the pre-packaged stacks come at a cost of > one-size-fits-all complexity and opacity, and don't fit the existing > architecture we're wanting to improve the HA attributes of. What Corosync > or OpenAIS can do on their own in our context is what we hope to understand > and take advantage of. >
yup i hear you > Is documentation of this in development somewhere? Or has the goal of > Corosync being available to a wider universe of uses than simply being an > implicit component of Pacemaker-based cluster stacks been abandoned? > > Thanks, > Whit corosync (man corosync) is a standalone component designed for n-way state replication with simple restart in condition of failure. The four apis are: CPG - closed process group (man cpg_overview) SAM - simple availability manager (man sam_overview) CONFDB - configuration database (man confdb) QUORUM - quorum information (man votequorum_overview) Its configuration is stored in corosync.conf (man corosync.conf) There are man pages for every API. There are also several cli tools of which all are documented in man pages. man -k corosync. Regards, -steve > _______________________________________________ > Openais mailing list > Openais@lists.linux-foundation.org > https://lists.linux-foundation.org/mailman/listinfo/openais _______________________________________________ Openais mailing list Openais@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/openais
