http://www.corosync.org/ 2012-02-04T21:03:49+00:00 http://www.corosync.org/ http://www.corosync.org/lib/images/favicon.ico text/html 2012-01-31T09:59:02+00:00 Jan Friesse http://www.corosync.org/doku.php?id=releases&rev=1328003942&do=diff Releases The project includes various features depending on release version. The Corosync Cluster Engine project currently has one stable release branch called Flatiron. All releases are made according to the release policy. Experimental Development Releases (needle - version 1.99.z) The latest testing needle branch version is 1.99.1 (Beta) released on Jan-31-2012. text/html 2012-01-31T09:57:56+00:00 Jan Friesse http://www.corosync.org/doku.php?id=welcome&rev=1328003876&do=diff Quick Links View our 2011-2012 Community Derived Roadmap View our Corosync datasheet which briefly describes the advantages and features of Corosync. Weavers Needle 2.0 is coming in the first half of 2012! View our published Weaver's Needle 2.0 schedule which describes the milestones and dates we want to hit. text/html 2012-01-19T18:49:44+00:00 Steven Dake http://www.corosync.org/doku.php?id=faq:why&rev=1326998984&do=diff Why was Corosync created? Corosync was created from a derivative work of the openais project. For 6 years, the openais project operated to implement Service Availability Forum APIs. After 6 years of development of a few APIs, we found ourselves consumed by the challenging task of creating the infrastructure on which the APIs would run. The infrastructure, such as interprocess communication, network protocols, recovery synchronization, timers, logging and tracing, and other components turned… text/html 2012-01-19T18:46:13+00:00 Steven Dake http://www.corosync.org/doku.php?id=dev:submitting_patches&rev=1326998773&do=diff Submitting patches via git The corosync project uses git for version control and it is helpful for submitted patches to follow the git work flow to optimize the opportunity for review and merge. Setup git install git and git-email via your distribution tools. In RPM distributions, this can be done via text/html 2011-10-21T08:43:31+00:00 Steven Dake http://www.corosync.org/doku.php?id=developers&rev=1319186611&do=diff Developers The Corosync source code is developed in C in about 55000 lines of C code. For those developers interested in contributing, please see the plugin developer guide which describes the internal APIs and designs for adding third party corosync plugins. text/html 2011-10-13T19:51:27+00:00 Steven Dake http://www.corosync.org/doku.php?id=support&rev=1318535487&do=diff Support Information There are several presentations that have been made about the topic of openais to various organizations. Documentation The Quickstart Guide contains all the information for getting started quickly using Corosync. Clusters From Scratch generated by the Pacemaker project has useful information on setting up Pacemaker for use with Corosync. text/html 2011-08-15T06:57:12+00:00 Jan Friesse http://www.corosync.org/doku.php?id=faq:linux_distros&rev=1313391432&do=diff What Linux distributions include Corosync? The Corosync Cluster Engine is shipped by the following Linux distributions: * Debian * Fedora * Gentoo * openSUSE * Ubuntu A note to Linux distributors: If you include openais in your product or project, please feel free to email a request to be added to this list to openais@lists.osdl.org. text/html 2011-07-19T13:04:09+00:00 Jan Friesse http://www.corosync.org/doku.php?id=openais_presentations&rev=1311080649&do=diff Some older presentations relating to openais from which this project was created: * A 2010 presentation from Steven Dake providing a guide to developing HA applications using Corosync given at South East Linux Festival 2010: SELF 2010 Slides * A 2007 presentation from Steven Dake providing a technical overview the OpenAIS Closed Process Groups Service: Inside Closed Process Groups